Groups | Blog | Home
all groups > dotnet distributed apps > october 2007 >

dotnet distributed apps : Deploy using a Third-Party Installer


AGP
10/29/2007 12:58:25 PM
I resisted for many years but I've just written my first app in .NET2005
and am looking to deploy my app with a third-party installer. ClickOnce
and the VS Installer do not meed my needs and I am already well versed
in another installer.

My question is mainly dealing with deploying the app dependecies. I think
I know where im headed but could use the advice of others who have had
more experience. Should i just take all the files in the \Release\ folder
and
deploy those. There are two DLLs which are listed as local and another one
which is non-local in the References. I can change if its local or not but I
dont
understand what makes a DLL local by default.

Anyway thats the point where im at after looking at countless artciles which
all seem to focus on the bult-in VS installer and installshield.

AGP

DIOS
10/29/2007 1:35:48 PM
Thank you for the info but I am not looking for an installer. Like I
said i already am well versed with another installer and all I'm
looking for is a methodology to deploy my app. My idea was to simply
deploy all files in the /Release folder. Is there a way to configure
my app such that it looks for the info in a /bin/ or /Support/ folder
rather than directly from the EXE path. I think I can just copy the
DLLs into the same path as the app and it should work on the target
system correct?

AGP
Rad [Visual C# MVP]
10/29/2007 10:05:05 PM
On Mon, 29 Oct 2007 12:58:25 GMT, "AGP" <sindizzy.pak@softhome.net>
[quoted text, click to view]

Take a look at the Wix installer --- it's much more flexibe than the
built in Visual Studio setup tool, and allow syou to do much more.

http://www.wix.sourceforge.net

--
AddThis Social Bookmark Button