Deployment Question
From: Dave M. (nospam_at_ihatesmap.com)
Date: 01/31/05
- Next message: Steve Easton: "Re: Where are version/author properties?"
- Previous message: TH3_CUR3: "Update Disk"
- Next in thread: Phill. W: "Re: Deployment Question"
- Reply: Phill. W: "Re: Deployment Question"
- Reply: Kevin Spencer: "Re: Deployment Question"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 31 Jan 2005 15:31:52 -0700
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: Steve Easton: "Re: Where are version/author properties?"
- Previous message: TH3_CUR3: "Update Disk"
- Next in thread: Phill. W: "Re: Deployment Question"
- Reply: Phill. W: "Re: Deployment Question"
- Reply: Kevin Spencer: "Re: Deployment Question"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|