From some moment in the past, in one project I can't start installer from IDE (Run->Run without debugging). IA gives me a message: "Please build your project before running without debugging". The same is for r"un with debugging" (slightly different message). Setup started directly works fine.
For the other project this functionality works ok. I'm trying to find the project setting responsible for it, but I failed. Do someone know what is going on?
Running setup from IDE - problem
-
- Posts: 904
- Joined: Thu Dec 22, 2005 7:03 pm
- Contact:
Hi,
Check if your build type is the same as the default project type, as the IDE will try to run the default project build type (even if you have built another type and that is available).
Check if your build type is the same as the default project type, as the IDE will try to run the default project build type (even if you have built another type and that is available).
Candice Jones
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/
-
- Posts: 904
- Joined: Thu Dec 22, 2005 7:03 pm
- Contact:
The default build type is the value stored in Deployment -> Build Settings.
Are you using a compiler variable to change the output file name? That might also confuse the IDE, causing it to fail to find the built file.
Are you using a compiler variable to change the output file name? That might also confuse the IDE, causing it to fail to find the built file.
Candice Jones
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/
>Are you using a compiler variable to change the output file name?
yes
>That might also confuse the IDE, causing it to fail to find the built file.
yes, this was the reason. But it should be considered as a bug, because I can't use default and simply rename files after build, because the name is hardcoded in other files.
Is there workaround for this?
yes
>That might also confuse the IDE, causing it to fail to find the built file.
yes, this was the reason. But it should be considered as a bug, because I can't use default and simply rename files after build, because the name is hardcoded in other files.
Is there workaround for this?
-
- Posts: 904
- Joined: Thu Dec 22, 2005 7:03 pm
- Contact:
Actually, there is no way for the IDE to know which compiler variable you may have last compiled your setup with, so the IDE plays it safe.
Your solution is to not use compiler variables in the custom output file field until you have debugged your setup.
Your solution is to not use compiler variables in the custom output file field until you have debugged your setup.
Candice Jones
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/
Who is online
Users browsing this forum: No registered users and 61 guests