Hi Everyone:

    I developed a .Net 2.0 asp.net application and add some references
to VB DLL and every thing work fine. Once the development is complete
and i deploy the app on Integration server references t Vb dll does not
work.To fix the problem i have to open the solution on Integration
Server and Delete the Reference to VB Dll and agian add the reference
again and build the solution.

Can someone please help me to avoid this manually reference every time
i update the solution on Integration Server.

Thanks in advance.

Pargat

Are you having the same version of the VB dll on both of your servers?
pargat.si***@gmail.com wrote:
Show quoteHide quote

GUID may change every week.
Mani wrote:
Show quoteHide quote

Hello pargat,

What if to set "Copy Local" to true in the VB dll references and deploy your
solution with local VB dll?

ps> Hi Everyone:
ps>
ps> I developed a .Net 2.0 asp.net application and add some
ps> references to VB DLL and every thing work fine. Once the development
ps> is complete and i deploy the app on Integration server references t
ps> Vb dll does not work.To fix the problem i have to open the solution
ps> on Integration Server and Delete the Reference to VB Dll and agian
ps> add the reference again and build the solution.
ps>
ps> Can someone please help me to avoid this manually reference every
ps> time i update the solution on Integration Server.
ps>
ps> Thanks in advance.
ps>
ps> Pargat
ps>
---
WBR,
Michael  Nemtsev [C# MVP] :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

VSNET: Problems adding VS 2005 extensions for .Net 3.0
VB vs. C# language challenge question
Split .NET exe file into many smaller ones
Block WM_MOUSEACTIVATE messages
Question on AppDomain and Thread