On this one, I'd have to say "Sort of, sometimes". If there haven't been any
changes in the ASPX pages or ASCX controls or references or anything else
that would change the Main project assembly, then yes, you should be able to
copy back the backup and have it work. But if you've made any changes in the
aspx pages etc. as described that would cause the new project to be looking
for something new in that assembly, and it doesn't find it, you may be a very
unhappy "webmaster".
Best solution:
1) test your code well locally before deploying to production.
2) Keep an entire website zipped up as a backup, "just in case".
3) Sleep well at night.
Cheers,
Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
"rh******@gmail.com" wrote:
Hey all. I'm the new webmaster of a popular website which is built in
..net using c#
I have successfully set up a dev environment on my local box here (with
some tweaking) but it works nonetheless.
As I create new asp.net pages I will need to recompile and update the
project dll in the bin folder. My question is, if for any reason the
newly compiled DLL causes some sort of error for the site, can I simply
recopy the old DLL's (which I will backup) back into the BIN folder?
My hesitation to simply test this is because the project has references
to various components and other projects.
thanks.
