Distribution as an executable installer

[Nak]

Hi there,

Suprise suprise, Tucows don't want my application because it's not in a
ZIP or EXE file. Hmmm, do they actually know anything about computers I ask
myself?

My installer is as an MSI file. So now I will have to somehow change it
to an EXE installer. But my understanding is that if I make an EXE
installer within a setup project I also have to distribute a cab file with
it (as well as some other files?).

Would I be correct in saying this? Or is there a way to distribute as
an executable installer without having to resort to a 3rd party product?

As usual, thanks loads in advance!

Nick.

 

[Scott Swigart]

You can use WinRar (http://www.rarsoft.com/download.htm) to make a
self-extracting .EXE that automatically launches your MSI.

 

[Nak]

Hi Scott,

Aaah, I hadn't actually thought of that concept. I'll have to have a
look at that. Thanks for your input! I'm was pulling my hair out!

Nick.

 

[Nak]

BTW, good blog.

 

[C-Services Holland b.v.]

Hi there,

Suprise suprise, Tucows don't want my application because it's not in a
ZIP or EXE file. Hmmm, do they actually know anything about computers I ask
myself?

My installer is as an MSI file. So now I will have to somehow change it
to an EXE installer. But my understanding is that if I make an EXE
installer within a setup project I also have to distribute a cab file with
it (as well as some other files?).

Would I be correct in saying this? Or is there a way to distribute as
an executable installer without having to resort to a 3rd party product?

As usual, thanks loads in advance!

Nick.

You could always try InnoSetup. It produces a single setup. I know it's
a 3rd party product, but it's free.
http://www.jrsoftware.org/
We use it extensivily.

 

[Nak]

Hi there,

Thanks for the suggestion, after Scotts suggestion I had actually tried
that. What I have done though is abanded both solutions and I'm actually
creating one myself. What I am making is an application that will convert
an MSI file into an EXE file (so to speak). What will happen is when the
EXE is run it will check to see if the required version of the .NET
Framework is installed and give notifications/links where necessary before
processing the MSI file.

The programs being written in C++ and it's pretty much finished, I just
need to smooth off the edges. I'm going to release it for free and what it
is going to mean is that when people want to distributor their .NET apps
they can still use an MSI installer, but wrap it with my new program and it
will add the benefit of Framework detection without needing the Framework.

Anyway, thanks for the suggestions, I'm glad I'm working on this now.
Ill post in here when it's finished.

Nick.