Re: Deployment Question
From: Dave M. (nospam_at_ihatesmap.com)
Date: 02/01/05
- Next message: Dave: "Re: Help - not showing up"
- Previous message: Henrique Bucher: "Help - not showing up"
- In reply to: Kevin Spencer: "Re: Deployment Question"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 1 Feb 2005 08:21:58 -0700
Thank you both for your answers. I stumbled upon the GAC thing yesterday
but the whole "strong-named" deal seems a bit overkill. I think I'll stick
with the apps version for now. It will probably be easier to manage the
deployments (keeping versions of the .dlls consistent between the two apps)
than doing the extra work.
Thanks again.
"Kevin Spencer" <kevin@DIESPAMMERSDIEtakempis.com> wrote in message
news:Op55BMGCFHA.2984@TK2MSFTNGP11.phx.gbl...
>> 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.
>>
>>
>
>
- Next message: Dave: "Re: Help - not showing up"
- Previous message: Henrique Bucher: "Help - not showing up"
- In reply to: Kevin Spencer: "Re: Deployment Question"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
