Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / IDE / November 2005

Tip: Looking for answers? Try searching our database.

Does VS.NET IDE add correponding versions of assemblies?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Sek - 07 Nov 2005 11:29 GMT
Hi Folks,

Sorry about the very abstract subject.

I am using VS.NET 2003.

I have a couple of DLLs written using C# and i have an App using these
assemblies.
I want to reference them in my App project by selecting the assemblies
under the References section. (Don't want to include the DLL project(s)
in the App solution).

Lets say my App's currently active configuration is "Release" and i
select the reference assembly of "Release" version from the
"obj\Release" folder of the corresponding assemblies.
Now, when i switch to "Debug" configuration of my App, will the project
automatically refer to the corresponding Debug versions of the
assemblies (I mean assemblies from "obj\Debug")?

TIA.
Sek
Carlos J. Quintero [VB MVP] - 07 Nov 2005 13:54 GMT
I don´t think so.

Any reason for not using Project References?

Signature

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

> Hi Folks,
>
[quoted text clipped - 17 lines]
> TIA.
> Sek
Sek - 07 Nov 2005 14:40 GMT
Hi Carlos,

There are no specific reason, except that it is the current setup and i
can't change that.

If i want to add the assemblies by locating using the add reference, is
it possible to add the corresponding configuration of assembly as per
the App project configuration. I mean, i want to refer debug version of
DLL for debug configuration of App and vice versa.

TIA.
Sek
Carlos J. Quintero [VB MVP] - 07 Nov 2005 15:07 GMT
References are "project properties" independent of the configuration
(Release/Debug) so they won´t change automatically. But you can add/remove
references programatically using the extensibility model, so you could build
a macro or add-in that switches references when executing it or clicking a
button. I think that even could be done automatically with some event that
notifies a change of configuration or a build. Let me know if you want to
follow that route, but it would be much better to use project references to
debug the library dlls. Also notice that in Release configuration you are
not debugging, so you can skip the IDE and run the app directly and at this
point the app will use as referenced dlls whatever the probing mechanism
finds first (dlls in the same folder, in subfolder, in GAC, etc.). In other
words, the Release configuration is used mostly to build the release version
and little else...

Signature

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

> Hi Carlos,
>
[quoted text clipped - 8 lines]
> TIA.
> Sek
Sek - 08 Nov 2005 02:00 GMT
Carlos,

Thanks for ur detailed reply.
One thing i am interested from your explanation is the purpose of
references.

I understand that, the references are basically for the compilation
phase to resolve the declarations. In this case, all that matters is
the type of assembly available during the execution/runtime phase,
rather than the compilation phase.

Presently, i am thinking of using Release config of assemblies in the
references and also set the "Copy Local" to false.

Thanks for all the help.
Sek

> References are "project properties" independent of the configuration
> (Release/Debug) so they won´t change automatically. But you can add/remove
[quoted text clipped - 33 lines]
> > TIA.
> > Sek
Carlos J. Quintero [VB MVP] - 08 Nov 2005 12:08 GMT
> In this case, all that matters is the type of assembly available
> during the execution/runtime phase rather than the compilation phase.
> Presently, i am thinking of using Release config of assemblies in the
> references and also set the "Copy Local" to false.

If you use "Release" versions as references during the debugging, you will
be unable to debug inside them if a problem arise...considering the some
people, including me, would love to debug inside the .NET Framework Dlls
provided by Microsoft to solve some problems, it would be a pity to impose
yourself the limitation of being unable to debug your own DLLs while
debugging their client application...

Signature

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.