I am having an issue with a new version of a .dll taking affect on my site. Locally, I had to manually add the new .dll version to GAC by removing the old version of the .dll and then re-adding the new one via Visual Web Developer. Is there a way to refresh the .dll on the server? I tried stopping the site, recycling the application pool, waiting two minutes, and then starting the site, but this did not affect things. This was suggested on the forum. The .dll in question is stored in the /bin/ folder and requires me to change my web.config file. If this is not done, the .dll generates a version mismatch error, so I know that I have done this properly. The new version of the .dll fixes a bug that I reported to the 3rd party vendor. The new version of the .dll is working locally (after the GAC trick), but I cannot get it to work on the server. Thank you for your help and suggestions. Below is the response from a ticket that I submitted on this topic: Hello, Thank you for contacting discountASP.NET. Basically, you need to do two things: 1. Upload your DLLs to the 'bin' folder of your web application 2. Properly reference that assemblies in your code We do not allow registering third party asseblies in GAC on our shared hosting environment. If your asseblies are bin-deployable, but you are still running into errors, please contact the developers of your web application for further assistance. You can also post your questions in our community forum for peer support: http://community.discountasp.net Please let us know if you have any further questions. Thank you, Dmitri DiscountASP.NET - Microsoft Gold Certified Partner - asp.netPRO Magazine Readers Choice Award for Best Hosting Service five years in a row! 2005 - 2009 - DiscountASP.NET forum: http://community.discountasp.net - DiscountASP.NET blog: http://daspblog.com
I am not sure I understand your question. Did you mean you uploaded the dll to the site bin directory but it is not seeing it?
No, it is being seen. If I remove the .dll, I get errors. What I am thinking is that the old .dll is somehow cached in memory or something, preventing the new version from being used. This was apparently the case when running locally.
