|
.net
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
ASP.net using old version of DLLsWe have a web app that includes a number of dlls. These cover all sorts of things such as email handling, error handling, data access etc. The email handler dll has been modified a number of times but it seems that the old versions are still being referenced somewhere. So when we modify a method, then re-copy the dll up to the web server, the code in the old method is still running, not the new stuff. How would this be so? Is a machine reboot the same as am IIS reset and should I do this? Under the Framework\v1.1.4322\Temporary ASP.NET Files\applicationName folder, there are a couple of folders with assemblies, but all the assemblies are from way back, not this week when we put a new build up. Is that an error? Thanks all any pointers would be great. Jon Jon,
A machine reboot is not the same as an IIS Reset. If your components are strange "out of process" components then a reboot may be required (this would be very unusual... but possible). A reboot would at least eliminate possibilities. Are the old DLL's COM objects? Any chance the modification would have disturbed the COM class/interface information.... i.e. do you need to rebuild the interop layer as well? Did you have any problems replacing the actual files? Usually if a DLL is loaded the file remains open... which makes replacing the file "tricky". Regards, Rob Show quoteHide quote "Jon" <J**@discussions.microsoft.com> wrote in message news:3F767805-975C-481A-A827-09B130B5F3A9@microsoft.com... > Hello all. > > We have a web app that includes a number of dlls. These cover all sorts of > things such as email handling, error handling, data access etc. The email > handler dll has been modified a number of times but it seems that the old > versions are still being referenced somewhere. So when we modify a method, > then re-copy the dll up to the web server, the code in the old method is > still running, not the new stuff. > > How would this be so? > > Is a machine reboot the same as am IIS reset and should I do this? > > Under the Framework\v1.1.4322\Temporary ASP.NET Files\applicationName > folder, there are a couple of folders with assemblies, but all the > assemblies > are from way back, not this week when we put a new build up. Is that an > error? > > Thanks all any pointers would be great. > > Jon > Hi Rob,
No they're standard .net dlls. Typically when we upgrade, we stop IIS, delete the old dll and copy in the new one. If you look under the v1.1.4322\Temporary ASP.NET Files folder, all the assemblies have a date from the 30th May, but we did the upgrade on Tuesday, plus the app hasn't taken on any of the new functionality. Thanks, Jon Show quoteHide quote "Rob MacFadyen" wrote: > Jon, > > A machine reboot is not the same as an IIS Reset. If your components are > strange "out of process" components then a reboot may be required (this > would be very unusual... but possible). A reboot would at least eliminate > possibilities. > > Are the old DLL's COM objects? Any chance the modification would have > disturbed the COM class/interface information.... i.e. do you need to > rebuild the interop layer as well? > > Did you have any problems replacing the actual files? Usually if a DLL is > loaded the file remains open... which makes replacing the file "tricky". > > Regards, > > Rob > > "Jon" <J**@discussions.microsoft.com> wrote in message > news:3F767805-975C-481A-A827-09B130B5F3A9@microsoft.com... > > Hello all. > > > > We have a web app that includes a number of dlls. These cover all sorts of > > things such as email handling, error handling, data access etc. The email > > handler dll has been modified a number of times but it seems that the old > > versions are still being referenced somewhere. So when we modify a method, > > then re-copy the dll up to the web server, the code in the old method is > > still running, not the new stuff. > > > > How would this be so? > > > > Is a machine reboot the same as am IIS reset and should I do this? > > > > Under the Framework\v1.1.4322\Temporary ASP.NET Files\applicationName > > folder, there are a couple of folders with assemblies, but all the > > assemblies > > are from way back, not this week when we put a new build up. Is that an > > error? > > > > Thanks all any pointers would be great. > > > > Jon > > > > >
Other interesting topics
OleDbDataAdapter created in code behaves differently from one created by wizard.
Howto inherit from an exisiting webcontrol in VS 2005 CSS examples Intellisense with web.config registration of controls XML PROBLEM HELP NEEDED URGENTLY Page hang after updating web.config problem with GridView Error BC30451 Making New web site by using ASP.Net 2005 date in datagrid |
|||||||||||||||||||||||