I purchased Express a couple days ago...and all seems okay on my install...except the Finished Dialog Box has a "check box "Run $TITLE$ now. When run it, it does not start my exe that I just installed...and I am not sure where to set the property to let it know what EXE to run.
Please let me know, Ed,
Finsished Dialog Box
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
Use the Run Programs view, and add a new run command set to use the "Finish Dialog" timing.
Michael Nesmith
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
Wrong startup dir - \"Finish Dialog\" timing.
Well I did that and it "almost worked"....I say almost because when it tries to start my application my program does not start seem to run from the $TARGET$ directory, I think it is actually running from the install directory because it launches and gives me errors trying to open my files like local mdb's etc that are in my target directory, it cant find them.
So the next question is how do I get the Run Programs to use the $TARGET$ as the "Start InFolder" just like the Shortcuts do.
BTW: The shortcuts work fine, just the TRun Programs does not.
Thanks again, Ed,
So the next question is how do I get the Run Programs to use the $TARGET$ as the "Start InFolder" just like the Shortcuts do.
BTW: The shortcuts work fine, just the TRun Programs does not.
Thanks again, Ed,
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
In that case, you need to use the Run Program As command, and specify the startup folder explicitly in the command. You do need access to the MSIcode view for this.
Michael Nesmith
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
Do you mean
Do you mean
make the Command Line Paramaters line say
$TARGETDIR$\\myapp.exe
and make the Run Program empty
I dont think you are saying put in Command Line Paramaters
c:\\program files\\company\\myapp.exe
because there program files could be in the d:
Ed,
make the Command Line Paramaters line say
$TARGETDIR$\\myapp.exe
and make the Run Program empty
I dont think you are saying put in Command Line Paramaters
c:\\program files\\company\\myapp.exe
because there program files could be in the d:
Ed,
It did not work :(
Well I tried it, I put $TARGETDIR$\\myapp.exe
as a Command Line Paramater
and it did not work....all it did is open the temp folder with the MSI
Is there no way to get this thing to run from the target directory...if not then that makes the last check box "Run Program" kinda usless
as a Command Line Paramater
and it did not work....all it did is open the temp folder with the MSI
Is there no way to get this thing to run from the target directory...if not then that makes the last check box "Run Program" kinda usless
You do need access to the MSIcode view for this
> You do need access to the MSIcode view for this
How do I do this?
I dont see it anywhere on my menu items.
How do I do this?
I dont see it anywhere on my menu items.
MSI Code requires upgrade?
You said that I need to access the MSI Code, but when I click on the tab I get a message to upgrade...is there no way to get this last box to run my program from teh working folder? If not then then that check box to run the program should not be there, most apps use some resource from their working directory.
Please let me know if there is a way to fix this bug without upgrading.
Thanks, Ed,
Please let me know if there is a way to fix this bug without upgrading.
Thanks, Ed,
-
- Posts: 3452
- Joined: Thu Dec 22, 2005 7:17 pm
- Contact:
This isn't a bug with InstallAware, but your program. If your program requires access to files in its own folder, it should be smart enough to read those files from its own folder, and not assume that an "empty path" always points to its own folder - it may not, especially when the program is run from another startup location. Any user could create a shortcut to your program from another startup location, or start it from the command line from another path, so this will come back and bite you later if you don't fix it now anyways.
And no, I'm afraid you can only edit dialogs with InstallAware Studio, and you can only access scripting with InstallAware Developer. I do apologize for the inconvenience...I will put in a feature request that the Run Programs view emit Run Program As instead of Run Program commands, but please be aware this isn't a bug in InstallAware, its a bug in your own program.
And no, I'm afraid you can only edit dialogs with InstallAware Studio, and you can only access scripting with InstallAware Developer. I do apologize for the inconvenience...I will put in a feature request that the Run Programs view emit Run Program As instead of Run Program commands, but please be aware this isn't a bug in InstallAware, its a bug in your own program.
Michael Nesmith
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
InstallAware
Home of The Next Generation MSI Installer
Get your free copy today - http://www.installaware.com/
all is good now...thanks again!
Thanks Michael...
Well I actually did set my app to read the app dir in my code...so at least I thought...but there was a bug in "my code"
At the place in question I was using the
Directory.GetCurrentDirectory();
Not the
Assembly.GetExecutingAssembly().Location
So that was the issue...I know you said that I need to use the MSIcode scripting but really I did not know where that was since like I said I had it only a couple days...please bear with me I am new using this product...thanks again for the quick response...and I have learned a little more...maybe I just need to upgrade since I think I will want to be editing these boxes at one time...all is good now...thanks again!
Well I actually did set my app to read the app dir in my code...so at least I thought...but there was a bug in "my code"
At the place in question I was using the
Directory.GetCurrentDirectory();
Not the
Assembly.GetExecutingAssembly().Location
So that was the issue...I know you said that I need to use the MSIcode scripting but really I did not know where that was since like I said I had it only a couple days...please bear with me I am new using this product...thanks again for the quick response...and I have learned a little more...maybe I just need to upgrade since I think I will want to be editing these boxes at one time...all is good now...thanks again!
Who is online
Users browsing this forum: No registered users and 72 guests