Why the dll is not updated in vs-2008?

[Prasadsm]

Hi Friends,

I am using a web application which is recently Converted from vs-2003 to vs-2008.Here whenever i build this application, the related dll in bin folder is not updated. what may be the reason? how can i overcome this? I need this recently modified dll to be used in main project.Can you please guide?

Thanks in Advance
Prasad.

[ThatThatGuy]

make sure that the project which is building the dll and the project which is using the dll are in same solution

[sashi]

Check the .dll path & reference, good luck :)

[Prasadsm]

Thanks for ur replies..

I tried ur suggestions but still the dll is not updated.

[tlhintoq]

Before you Build, right-click on the solution and choose "Clean solution"
That should delete all compiled code.

Now check the output directory again. Is the compiled DLL gone? If it's not, that's because its not really part of that solution. Someone just dropped it in there for use by some of the code they've written.

Now that everything has been cleaned, Visual Studio has no choice but to compile a new one for you.

You *are* increasing the version numbers in the assembly properties for these - right? If you aren't, it would see no reason to make a new one.

[Frinavale]

The DLL that isn't updated...is it an unmanaged/COM code?
These DLLs are not automatically updated (ever) and you will have to update them manually....usu ally this involves re-registering the new version of the DLL and then re-referencing it in your application so that a new Interop class is generated to use the new DLL.

-Frinny

[Prasadsm]

thanks friends for ur replies.

But here in vs-2008... once the web application which was created in vs-2003 is converted to vs-2008 becomes website.[Initially its a Project , After Conversion if you commit this project and checkout it becomes website] . Bcoz of this, the newly updated dll is created in App_code folder (in some other Location) instead of bin folder and also the dll name will be different.

[JamieHowarth0]

That's a nasty little snag I wasn't aware of. Thanks for bringing it to my attention, I'll bear it in mind for future upgrades from legacy projects :-)

codegecko

[Frinavale]

Hmm I never experienced that problem when upgrading my projects...stra nge