Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Referencing another project
Message
From
05/10/2012 08:06:05
 
 
To
05/10/2012 06:36:02
General information
Forum:
ASP.NET
Category:
Other
Environment versions
Environment:
C# 3.0
Miscellaneous
Thread ID:
01554354
Message ID:
01554361
Views:
50
>Here's a basic question:
>I have a solution that contains 5 projects.
>All 5 projects reference a dll - wsgutilitieslib.dll that contains many utilities used by this solution but is not a project in the solution.
>wsgutilitieslib.dll rarely changes, but it does occasionally.
>What should I do in the calling solution when I make changes to wsgutilitieslib.dll?
>I've been removing and re-adding the reference to it in each project of the solution.
>Is that necessary? Is so, it's getting to be quite a pain.
>What's the most efficient way to handle something like this?

AFAIK, if you add a reference to an external DLL in a project it will always use the current (i.e. latest) version. No special action neccessary. Do you have a situation where this is not the case ?
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform