iisreset? why does this work?

[Reader]

Here is the story. I have my ASP.Net web appliacation that when I uninstall
an old version and install a new version the old version's assemblies are
still in the system somewhere and cause the new install to crash or have old
application operations.

Here are some notes on the assemblies. They are put in the GAC. The old
and the new have the same version information. During the new version
install the ASP.Net web folder is deleted from inetpub. My install also
deletes the app's folder from the "Temporary ASP.NET Files" to prevent the
known cached file to exist in the new install. This all worked perfectly
before what I think the new service pack. I will have to verify.

So, when i install the new version and run the web application it will
either crash because it cannot find the properties, methods, or classes in
the cached assembly or it will execute the old logic. Now, if I do nothing
but run iisreset and rerun my new install it all works perfectly. EVERY
time I test an install I get the same results. I am about to test this with
a Windows 2003 machine and it too has the latest service packs. If it
continues to happen I will be forced to either put a forced iisreset in my
install or determine if the problem is with the service packs. Has anyone
else seen this issue if so how might i avoid this issue?

Thank you for your time.

 

[Kevin Spencer]

The GAC works a heck of a lot like the COM registry. If you install a new
version having the same version number, you will have to do what you're
doing to use it. Why not use the \bin folder instead? Lot less trouble.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living

 

[Reader]

The assembly it references does exist in the GAC.... other applications use
the assembly too. But the same assembly is also in the bin. Because the
asp.net app does not find it unless it too exists in the bin..... anyway..
between the instlls this bin and the parent web folder are removed but the
old one still seems to exist. I have tested on a machine that predates the
latest services packs and it happened to me again.. maybe my firs ttime
fix did not solve it to begin with.. but no matter it would be nice to
figure out a solution to this..

 

[Reader]

To give you another thing about the assemblies... the assemblies are used in
many applications.. it just happens this web site is one of those
appliations that use them. It should not matter if they are in the GAC or
bin. What matters is that when the web site is completely removed and even
the asp.net cache folder is removed IIS still has them somewhere.. memory...
on disk? If i could know where and how to solve this and not have to debate
why i have my assemblies in the GAC.......

Why do i have to restart IIS to have it work?!? IIS is the only application
that needs a restart. All Windows applications that reference the
assemblies do not have problems with the install. This can't be a complete
fluke when i can reproduce this error 100% on many different server
installations...

 

[Reader]

The solution.

The solution was to set a property in my VS.Net setup project. I set the
restartwwwservices to true and this will magically under the mask of
whatever.. restart the iis services...


It had nothing todo with how i was implementing my GAC or assemblies.. peace
out kids.. have fun with that info mauahah

 

[Reader]

The solution is to set the property in my VS.Net setup project to restart
www services...