Assembly backups + versioning

  • Thread starter Thread starter Stephen Brown
  • Start date Start date
S

Stephen Brown

Here's another mystery I hope someone can shed some light on. I made a
backup last month of my web application assemblies to another local drive on
the web server and renamed the files to a different extension to reflect the
version number on the backup. Last week, we updated the live web
application with the current version and all hades broke loose. The
application would no longer load and was giving assembly errors (I cannot
recall the errors). We spent hours trying to track it down until somebody
noticed the different extension in the audit of one of the errors. It
turned out that dotNet had magically decided to use the assemblies that had
been copied to another local drive with different extensions. We moved
these backup files to a network drive and the application began working
again.

Similarily, we had a client a couple of months ago with a problem where they
had been backing up the web.config file to the same directory as the live
web.config file, but giving it a different name. When we updated the
assembly files, we suddenly got machine.config errors about Access denied to
some of the assemblies. We noticed that this was the same error we get if
we delete the web.config file, so we knew where to look. When we deleted
all the backup web.config files, the application started working again even
though the web.config file never moved or was changed in any way.

I have started instructing clients to never backup dotNet files to a local
drive. Has anybody else had this experience? Anybody know what's going on
with this or how to prevent this from happening?
 
Sounds like an explorer thing like it tracks a COM DLL when you move it to the recycle bin. See if you can reproduce if you move, and rename, via the command shell

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog

nntp://news.microsoft.com/microsoft.public.dotnet.framework/<[email protected]>

Here's another mystery I hope someone can shed some light on. I made a
backup last month of my web application assemblies to another local drive on
the web server and renamed the files to a different extension to reflect the
version number on the backup. Last week, we updated the live web
application with the current version and all hades broke loose. The
application would no longer load and was giving assembly errors (I cannot
recall the errors). We spent hours trying to track it down until somebody
noticed the different extension in the audit of one of the errors. It
turned out that dotNet had magically decided to use the assemblies that had
been copied to another local drive with different extensions. We moved
these backup files to a network drive and the application began working
again.

Similarily, we had a client a couple of months ago with a problem where they
had been backing up the web.config file to the same directory as the live
web.config file, but giving it a different name. When we updated the
assembly files, we suddenly got machine.config errors about Access denied to
some of the assemblies. We noticed that this was the same error we get if
we delete the web.config file, so we knew where to look. When we deleted
all the backup web.config files, the application started working again even
though the web.config file never moved or was changed in any way.

I have started instructing clients to never backup dotNet files to a local
drive. Has anybody else had this experience? Anybody know what's going on
with this or how to prevent this from happening?



---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.770 / Virus Database: 517 - Release Date: 27/09/2004



[microsoft.public.dotnet.framework]
 
Back
Top