Deploy using a Third-Party Installer

[AGP]

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

[Rad [Visual C# MVP]]

On Mon, 29 Oct 2007 12:58:25 GMT, "AGP" <si**********@softhome.net>
wrote:

>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

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

--
http://bytes.thinkersroom.com

[DIOS]

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]]

On Mon, 29 Oct 2007 13:35:48 -0700, DIOS <si******@gmail.comwrote:

>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

Perhaps I'm not understanding your problem -- from what I understand
you want to be able to deploy some DLLs with your application that are
not in the standard bin folder, correct?

It this is so I don't understand your reluctance to use an installer
of some sort. How will you deal with issues like

1) Allowing the user choice of where to install the files
2) Control the versioning of the application for support issues
3) Where applicable, register assemblies in the Global Assembly Cache?
4) Allow the user to cleanly uninstall the application?

--
http://bytes.thinkersroom.com

[AGP]

"Rad [Visual C# MVP]" <ra*@nospam.comwrote in message
news:m4********************************@4ax.com...

On Mon, 29 Oct 2007 13:35:48 -0700, DIOS <si******@gmail.comwrote:

>>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

Perhaps I'm not understanding your problem -- from what I understand
you want to be able to deploy some DLLs with your application that are
not in the standard bin folder, correct?

It this is so I don't understand your reluctance to use an installer
of some sort. How will you deal with issues like

1) Allowing the user choice of where to install the files
2) Control the versioning of the application for support issues
3) Where applicable, register assemblies in the Global Assembly Cache?
4) Allow the user to cleanly uninstall the application?

--
http://bytes.thinkersroom.com

yes it seems like I haven not made myself clear. I am not asking for advice
on installers.
I have one already and am well versed in building installations with this
specific system.
My inquiries have to deal with how to deploy my app and its dependencies.
bascially
like pseudo code so that i can replicate it with my installer. I think I
understand that i can deploy
my exe along with its DLLs and place them in the same direcory and it should
work. Now
if i wan to deploy the dependencies to another folder say a /Support/ folder
then I have to
regsiter in the GAC. Is that correct? My second inquiry is what files do i
deploy. As I understood
it I just deploy all files in my projects /bin/Release/ folder. is that
correct?

AGP

[aDelfino]

I agree
"AGP" <si**********@softhome.netwrote in message
news:Eu*******************@newssvr29.news.prodigy. net...

>
"Rad [Visual C# MVP]" <ra*@nospam.comwrote in message
news:m4********************************@4ax.com...

>On Mon, 29 Oct 2007 13:35:48 -0700, DIOS <si******@gmail.comwrote:

>>>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

Perhaps I'm not understanding your problem -- from what I understand
you want to be able to deploy some DLLs with your application that are
not in the standard bin folder, correct?

It this is so I don't understand your reluctance to use an installer
of some sort. How will you deal with issues like

1) Allowing the user choice of where to install the files
2) Control the versioning of the application for support issues
3) Where applicable, register assemblies in the Global Assembly Cache?
4) Allow the user to cleanly uninstall the application?

--
http://bytes.thinkersroom.com

yes it seems like I haven not made myself clear. I am not asking for
advice on installers.
I have one already and am well versed in building installations with this
specific system.
My inquiries have to deal with how to deploy my app and its dependencies.
bascially
like pseudo code so that i can replicate it with my installer. I think I
understand that i can deploy
my exe along with its DLLs and place them in the same direcory and it
should work. Now
if i wan to deploy the dependencies to another folder say a /Support/
folder then I have to
regsiter in the GAC. Is that correct? My second inquiry is what files do i
deploy. As I understood
it I just deploy all files in my projects /bin/Release/ folder. is that
correct?

AGP

[AGP]

Hmm, you agree on what? Anyway, still researching this. Again I have
an installer system and Im looking for advice on what files in the /
Release/ folder of my project i need to deploy.

Rgds
AGP

On Nov 13, 7:57 am, "aDelfino" <[e-mail]:

I agree"AGP" <[e-mail] in message

news:Eu*******************@newssvr29.news.prodigy. net...

"Rad [Visual C# MVP]" <[e-mail] in message
news:m4********************************@4ax.com...

On Mon, 29 Oct 2007 13:35:48 -0700, DIOS <[e-mail]:

>>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

Perhaps I'm not understanding your problem -- from what I understand
you want to be able to deploy some DLLs with your application that are
not in the standard bin folder, correct?

It this is so I don't understand your reluctance to use an installer
of some sort. How will you deal with issues like

1) Allowing the user choice of where to install the files
2) Control the versioning of the application for support issues
3) Where applicable, register assemblies in the Global Assembly Cache?
4) Allow the user to cleanly uninstall the application?

--
http://bytes.thinkersroom.com

yes it seems like I haven not made myself clear. I am not asking for
advice on installers.
I have one already and am well versed in building installations with this
specific system.
My inquiries have to deal with how to deploy my app and its dependencies.
bascially
like pseudo code so that i can replicate it with my installer. I think I
understand that i can deploy
my exe along with its DLLs and place them in the same direcory and it
should work. Now
if i wan to deploy the dependencies to another folder say a /Support/
folder then I have to
regsiter in the GAC. Is that correct? My second inquiry is what files do i
deploy. As I understood
it I just deploy all files in my projects /bin/Release/ folder. is that
correct?

AGP