A quick question about best working practices when deploying, and maintaining an asp.net site.
If you compile all your code client side, using vs.net. Assuming a large site, I would imagine your 'site dll' (does anyone know the correct terminology for this?) is going to be a large file of the order of mb.
My question, regarding maintenance and improvement of such a site, is if any code changes need to be made/page code added, will this require a recompilation of the *entire* site?? I cannot see how such a system can work in most environments.
I am working on a remote development machine from my web server. Further to this, if I recompile the entire site, I will, I presume end up with MB's worth of dll, which I then have to upload to my server. Possibly taking minutes, where I presume the dll I am overwriting will be unavailable for access (the website goes down??) the other possibility in my eyes is that the dll is loaded into memory for use by the web server, will I then require a restart of the site/IIS/server??
An alternative is that we recompile all code on the server, I'm most hesitant to do this as it's *not* what that server's there for. This would also not get round the scenario outlined above whereby our site is unavailable for the duration of the action.
Hopefully someone can help me as this is the last step in getting the infrastructure of our site ready for the real meat of development. I'm hoping I've got some pretty large misconceptions that can be put right here.
TIA
If you compile all your code client side, using vs.net. Assuming a large site, I would imagine your 'site dll' (does anyone know the correct terminology for this?) is going to be a large file of the order of mb.
My question, regarding maintenance and improvement of such a site, is if any code changes need to be made/page code added, will this require a recompilation of the *entire* site?? I cannot see how such a system can work in most environments.
I am working on a remote development machine from my web server. Further to this, if I recompile the entire site, I will, I presume end up with MB's worth of dll, which I then have to upload to my server. Possibly taking minutes, where I presume the dll I am overwriting will be unavailable for access (the website goes down??) the other possibility in my eyes is that the dll is loaded into memory for use by the web server, will I then require a restart of the site/IIS/server??
An alternative is that we recompile all code on the server, I'm most hesitant to do this as it's *not* what that server's there for. This would also not get round the scenario outlined above whereby our site is unavailable for the duration of the action.
Hopefully someone can help me as this is the last step in getting the infrastructure of our site ready for the real meat of development. I'm hoping I've got some pretty large misconceptions that can be put right here.
TIA