Re: Deployment Question

From: Kevin Spencer (kevin_at_DIESPAMMERSDIEtakempis.com)
Date: 02/01/05


Date: Tue, 1 Feb 2005 08:36:15 -0500


> Basically, I have one solution that has a number of .DLLs, and 2
> applications that use those core DLLs. When I try to build a deployment
> package for my applications, I figured it was a good idea to put the .DLLs
> in the system folder and just share them between the two applications.

That's not how .Net works. You're thinking about it as if it were COM, which
it ain't.

You basically have 2 choices:

1. Put the assemblies in the bin folders of their respective apps.
2. Register the assemblies inthe Global Assembly Cache (GAC).

Unless you have a really good reason to register the assemblies in the GAC,
I would go ahead with the simple XCopy deployment. The GAC is really there
for things like the CLR, which is used by all .Net applications. If you only
have 2 that use the same assemblies, I wouldn't bother.

-- 
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
Neither a follower nor a lender be.
"Dave M." <nospam@ihatesmap.com> wrote in message 
news:uzvjaS%23BFHA.3596@TK2MSFTNGP12.phx.gbl...
>I looked for a different group to post this but didn't see it.
>
> I am having an issue with a deployment project using. I am using Visual 
> Studio 2003 and have a deployment project for my application.
>
> Basically, I have one solution that has a number of .DLLs, and 2 
> applications that use those core DLLs.  When I try to build a deployment 
> package for my applications, I figured it was a good idea to put the .DLLs 
> in the system folder and just share them between the two applications.
>
> The problem I am having is that when I move the .DLLs in my deployment 
> project to the System Folder, my application can no longer see the .dll. 
> When I start the applicaiton, I get an error saying that it cannot find 
> the assembly.  If I keep the .dll in the Application Folder, the 
> application works.
>
> I tried different ways of registering (None, COM, Relative), but nothing 
> seems to work.  It seems silly to have the .dlls in 2 places, especially 
> for updating purposes.
>
> Is there a different way to do this?  Any info is appreciated.
>
> 


Relevant Pages

  • Re: Deployment Question
    ... > use those core DLLs. ... > in the system folder and just share them between the two applications. ... deployment method. ... locating assemblies is concerned. ...
    (microsoft.public.vstudio.general)
  • Re: Deployment Question
    ... >> applications that use those core DLLs. ... >> .DLLs in the system folder and just share them between the two ... I would go ahead with the simple XCopy deployment. ...
    (microsoft.public.vstudio.general)
  • Avoiding DLL hell with unmanaged applications
    ... Can I leverage assemblies to avoid DLL hell with unmanaged code? ... static libraries that I would like to convert to DLLs. ... existing applications. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: D2007 - mind-numbing obstacles after upgrading
    ... We avoid stuff like packages and DLLs since it makes deployment of ... applications so much more complex - our apps roll out to thousands of ... deployment takes on a new face entirely. ...
    (borland.public.delphi.non-technical)
  • Re: Same assembly in different deployments
    ... I have created a class library, when builded it produces a dll called test.dll. ... When I create a deployment project, this dll is added to the output and is shipped with the application. ... How can I change the setup/code/properties so the application will look in a different directory for this particular assembly at runtime, while it look for other assemblies in the application path? ... that it is not an option to install ALL applications in the same directory. ...
    (microsoft.public.dotnet.languages.csharp)