Publishing

[PiotrKolodziej]

Hi
Is the a way to prepare install packet in such a way that user dont have to
care about installing .NET Framework 2.0? I know that FM 2.0 is required for
all c# applications, but i would like client not to care about any other
install packets but mines.
Thanks
PK

 

[Champika Nirosh]

check this
http://msdn.microsoft.com/msdnmag/issues/04/10/Bootstrapper/

else you may have to write a setup script using some thing like "Installed
Shield"

or else you may write your own setup program that invoke frame work
installtion first and then your app setup ..

finally the easier would be to have framework setup and app setup with the
destribution pack and write a simple bat file to invoke the two setup files
sequencially..

Nirosh.

 

[PiotrKolodziej]

BootStrapper seems to be cool.
Thank you.
PK

 

[Chris Mullins]

Is the a way to prepare install packet in such a way that user dont have
to care about installing .NET Framework 2.0? I know that FM 2.0 is
required for all c# applications, but i would like client not to care
about any other install packets but mines.

What you're looking for is the Setup Bootstrapper. There's a ton of custom
stuff you can do in there to make sure your pre-requisites are met.

A collegue of mine wrote a number of custom packages for this, and wrote it
up in his blog at:
http://www.coversant.net/dotnetnuke/Default.aspx?tabid=88&EntryID=16

He goes into all sorts of detail in his samples, including building
bootstrappers for x64, IA64, and other related items.