Phoenix_124

Can you use Iexpress to make a installer for my VB 2005 Express applications



Re: Visual Basic Express Edition Iexpress (hidden setup tool in XP) use as setup installer for VB 2005 Express applications?


Re: Visual Basic Express Edition Iexpress (hidden setup tool in XP) use as setup installer for VB 2005 Express applications?

Phoenix_124

I'm also trying to add .Net Framework 2.0 on to the installer including with my program using iexpress. How to do so





Re: Visual Basic Express Edition Iexpress (hidden setup tool in XP) use as setup installer for VB 2005 Express applications?

Tall Dude

See post:

http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=227099&SiteID=1

Also I just posted the source code for my 'toy' installer at:

http://users.adelphia.net/~gcumbia/MakeMyExe.zip

A lot of the code in involved in making the form look and act interesting.

The meat of the code is where I build a 'SED' file for IExpress and a

batch file to handle renaming files and launching setup.exe.

My little program takes a simple 'publish to CD' VB express program,

configured to download the NET framework from the internet, and makes a

self extracting executable which copies the files and folders of the SIMPLE

program onto the target PC and starts the setup.exe ( which actually

handles most of the installation.)

For people who have an IPC server that causes the infamous 'XML' problem,

my installer is a poor man's workaround for this.

The main drawback to IExpress is that in some modes and places it will

not handle long file names. This is why my program had to programatically

save all the file names and re-name them by using a 'created on the fly' batch

script.

What I maen by a simple program is; If you made a program called testprg

and published it as 'CD-Rom installation' and pointed the location to say

'c:\t4'.

Then in folder c:\t4, you would have:

setup.exe

testprg.application

testprg_1_0_0_1.application

and one folder named

testprg_1_0_0_1

In folder testprg_1_0_0_1, you would have:

testprg.exe.deploy

testprg.exe.manifest

My program checks that the publish folder has only one subfolder

(as one of it's checks. It then makes sure that all the files in the publish

folder and the one subfolder get packed into the self extracting executable.

So for people with a different folder structure than I described, their program

could not be bundled correctly with my MakeMyExe 'toy' installer.