B
Bazza Formez
Greetings...
I have an odd problem to do with replacing a DLL.
My ASP.NET application makes use of a 3rd party charting component.
This component is supplied as a DLL file.
The component has worked well for us, but now I am having real problems
trying to replace the DLL with a new version.
To implement on my development machine, I am simply attempting to copy
the new version into the bin directory after deleting the old version.
However, everytime I run the application (or when I restart Visual
Studio I think)... magically the old version of the DLL is copied into
the bin directory over my new version.
Even if I completely delete all versions of the DLL from the bin
directory... somehow the old DLL reappears !
I saw somewhere that you have to be careful to rename old backups such
that they don't have a DLL extension .. but I don't even have a backup
in the directory.
Am I missing some basic knowledge here to do with .NET DLL
implementation ?
Can anyone please help ?
Thank you ,
Bazza
I have an odd problem to do with replacing a DLL.
My ASP.NET application makes use of a 3rd party charting component.
This component is supplied as a DLL file.
The component has worked well for us, but now I am having real problems
trying to replace the DLL with a new version.
To implement on my development machine, I am simply attempting to copy
the new version into the bin directory after deleting the old version.
However, everytime I run the application (or when I restart Visual
Studio I think)... magically the old version of the DLL is copied into
the bin directory over my new version.
Even if I completely delete all versions of the DLL from the bin
directory... somehow the old DLL reappears !
I saw somewhere that you have to be careful to rename old backups such
that they don't have a DLL extension .. but I don't even have a backup
in the directory.
Am I missing some basic knowledge here to do with .NET DLL
implementation ?
Can anyone please help ?
Thank you ,
Bazza