IIS 5 & IIS 6
DLL update in bin folder acting as if it didn't happen? Temp asp.net...
Last post Jul 23, 2019 08:27 PM by juanmanuelrojascavaliere
Jan 22, 2013 09:34 AM|BitShift|LINK
Iv'e been using IIS and asp.net for several years now, and this one stumped me. I built some simple changes in a website (vs 2010) and the single assembly for the website works fine when built to a folder that my local IIS (v 7) is mapped to. This works
fine, but when I copied the same dll to a folder on a test server (running IIS6 with .net 4.0), the app domain
SHOULD have refreshed since the dll SHOULD have been seen as different, correct?
After several iterations of build, recycle the app pool, cleaning the temp asp.net files, copying over the dll, test the site, rinse and repeat....the dll changes
FINALLY showed themselves. What gives?
I dont recally having this much trouble with deploying changes to IIS6 in the past.
This morning, after going through a few more iterations, I think I know what my problem was. I need to do a VIsual Studio REBUILD, not just BUILD. One clue all along that my app domain was infact restarting, was that I would have to re-login
to the app because the session had been terminated. So after all my headaches, it was something as simple as this. Everytime I do a make changes, do a rebuild (not just build), and then copy over the dll, the changes show up correctly on the IIS6 box. Ok,
so now Im still wondering why this wasnt a problem with my local instance of IIS7....hmmm
Jan 24, 2013 12:41 AM|Catherine Shan - MSFT|LINK
This morning, after going through a few more iterations, I think I know what my problem was. I need to do a VIsual Studio REBUILD, not just BUILD. One clue all along that my app domain was infact restarting, was that I would have to re-login to the app because
the session had been terminated. So after all my headaches, it was something as simple as this.
In order to help you, you need to know the difference between Build and Rebuild in Visual Studio.
Build means compile and link only the source files that have changed since the last build, while Rebuild means compile and link all source files regardless of whether they changed or not.
For details, please check the link below:
Ok, so now Im still wondering why this wasnt a problem with my local instance of IIS7....hmmm
I am a little confused. How do you do when add a dll to IIS7?
Jan 24, 2013 08:25 AM|BitShift|LINK
I had setup a local folder to publish to, mapped this folder to an .net wrb application within IIS7 running on my local Win7 workstation. When doing a build then publish or simply publish, to this local folder and testing the application locally, the changes
were as they should be.
However, when copying this same dll to an applicaiton folder on a test server (running IIS6), then testing the application, the changes did not seem to be there.
Only after making a few edits to the dll, doing a rebuild and then copyin gthe dll over, did my updates seem to take effect. I dont know where the problem really was however, either with IIS6, or the temporary asp files/ cache or somewhere else. Ive read
other reports of similar strange things happening when doing a web publish, as the copies of some files on the server are seen as newer and they dont get copied over. However, in my case I was first publishing to a local folder, then copying them over locally.
Jul 23, 2019 08:27 PM|juanmanuelrojascavaliere|LINK
Im Juan from Argentina.
Have you experienced this again? with newer Microsoft Products? I will be testing the RE BUILD approach tomorrow.