Re: deployment of a .NET DLL
From: Bob Powell [MVP] (bob_at__spamkiller_bobpowell.net)
Date: 05/13/04
- Next message: Thomas: "MouseMove outside windows"
- Previous message: jamie: "Re: Serial Communication (Com1)"
- In reply to: songie D: "Re: deployment of a .NET DLL"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 13 May 2004 23:06:33 +0200
Installing the DLL in the same directory as the executable is by far the
simplest scenario.
Installation in the GAC is useful when a single DLL serves for many
applications and requires strict version management.
DLL's whether in the application directory or in the GAC are all "early
bound". That is to say that the compilation process must have access to the
reference of the DLL and the specific version does matter even though you
might be able to configure the application to use a different version later.
-- Bob Powell [MVP] Visual C#, System.Drawing Image transition effects, automatic persistent configuration and design time mouse operations all in April's issue of Well Formed http://www.bobpowell.net/wellformed.htm Answer those GDI+ questions with the GDI+ FAQ http://www.bobpowell.net/gdiplus_faq.htm The GDI+ FAQ RSS feed: http://www.bobpowell.net/faqfeed.xml Windows Forms Tips and Tricks RSS: http://www.bobpowell.net/tipstricks.xml Bob's Blog: http://royo.is-a-geek.com/siteFeeder/GetFeed.aspx?FeedId=41 "songie D" <songie@d.com> wrote in message news:OaWGJnROEHA.3596@tk2msftngp13.phx.gbl... > Is this like the difference between late binding and early binding in VB6? > Except it's set at the building-of-the-DLL level? > I think it just sounds simpler to have it in the same directory as the app - > after all I don't want to get into a strange bootstrapping process when > installing it on the user's pc... > > "Bob Powell [MVP]" <bob@_spamkiller_bobpowell.net> wrote in message > news:OhdomLOOEHA.2920@tk2msftngp13.phx.gbl... > > > Does it require you to change the reference to the release version when > > building a release version of the program? > > > > No. > > > > If you're building with Visual Studio you can have the IDE build a > strongly > > named DLL for you by setting the appropriate values in the > AssemblyInfo.cs. > > Look at the comments in that file for a greater understanding. > > > > -- > > Bob Powell [MVP] > > Visual C#, System.Drawing > > > > Image transition effects, automatic persistent configuration and > > design time mouse operations all in April's issue of Well Formed > > http://www.bobpowell.net/wellformed.htm > > > > Answer those GDI+ questions with the GDI+ FAQ > > http://www.bobpowell.net/gdiplus_faq.htm > > > > The GDI+ FAQ RSS feed: http://www.bobpowell.net/faqfeed.xml > > Windows Forms Tips and Tricks RSS: http://www.bobpowell.net/tipstricks.xml > > Bob's Blog: http://royo.is-a-geek.com/siteFeeder/GetFeed.aspx?FeedId=41 > > > > > > > > > > > > "songie D" <anonymous@discussions.microsoft.com> wrote in message > > news:6444A54F-A443-471C-A3D5-2981987C7452@microsoft.com... > > > Does it require you to change the reference to the release version when > > building a release version of the program? > > > > > >
- Next message: Thomas: "MouseMove outside windows"
- Previous message: jamie: "Re: Serial Communication (Com1)"
- In reply to: songie D: "Re: deployment of a .NET DLL"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
