Please build your project before running without debugging
-
- Posts: 32
- Joined: Mon Oct 29, 2012 2:27 pm
Please build your project before running without debugging
X3 Studio Admin Edition, Update 20.11, Win8.1
I build the installer project (Single EXE) successfully, and now, after I have begun dual signing the components using the IA Build Events according to InstallAware's published instructions, I get this message every time I click the Green Arrow on the IDE to run the setup without debugging, (or after making a Debug Build) I click on the debugger. In short, I can no longer run a setup, with or without debugging, from within the IDE.
(NOTE: Before dual signing via the IA build events, I could build an setup and them immediately run it without debugging as described above without this dialog box popping up).
What has changed? Did I miss something in the Release Notes?
erich.einfalt@ntrepidcorp.com
I build the installer project (Single EXE) successfully, and now, after I have begun dual signing the components using the IA Build Events according to InstallAware's published instructions, I get this message every time I click the Green Arrow on the IDE to run the setup without debugging, (or after making a Debug Build) I click on the debugger. In short, I can no longer run a setup, with or without debugging, from within the IDE.
(NOTE: Before dual signing via the IA build events, I could build an setup and them immediately run it without debugging as described above without this dialog box popping up).
What has changed? Did I miss something in the Release Notes?
erich.einfalt@ntrepidcorp.com
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Please build your project before running without debugging
Dear Erich,
probably I missed some of the steps you used, but I am not able to reproduce the same.
By the way, are you sure that the compressed EXE has been effectively generated?
Please also note that with our "Microsoft’s new code signing policy - via IA Build Events" tutorial, are described the different "command lines" that have to be defined based on the build mode used. Are you sure that those you entered effectively match with the build mode you used?
Regards
probably I missed some of the steps you used, but I am not able to reproduce the same.
By the way, are you sure that the compressed EXE has been effectively generated?
Please also note that with our "Microsoft’s new code signing policy - via IA Build Events" tutorial, are described the different "command lines" that have to be defined based on the build mode used. Are you sure that those you entered effectively match with the build mode you used?
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
-
- Posts: 32
- Joined: Mon Oct 29, 2012 2:27 pm
Re: Please build your project before running without debugging
Q: "are you sure that the compressed EXE has been effectively generated?"
A: Yes, because I can run the finished compressed single .exe from the #PROJDIR#\Release\Single folder and it runs correctly.
Q: "Are you sure that those you entered effectively match with the build mode you used?"
A: Here is the PostCompress Event script used for a Single Compressed .EXE setup output:
NOTES:
(1) The compiler variable #ROLE# referenced below contains either "Setup" or "Updater". In production builds, this variable is set on the miabuild.exe command line. In the IDE, the value is "Setup". It is used in creating the final output filename.
(2) The compiler variable #DISPVERSION# referenced below contains the full 4 digit version number of the primary executable to be installed named #TITLE#.exe. It is also used in creating the final output filename.
(3) The compiler variable #AUTOBUILDNUM# referenced below contains the Bamboo Build number. It is also used in creating the final output filename.
#CERT_FOLDER#\SignTool.exe sign /n "{REDACTED_STORED_SIGNING_CERT_IDENTIFIER}" /t http://timestamp.comodoca.com/rfc3161 "#PROJDIR#\Release\Single\#TITLE#_#ROLE#_v#DISPVERSION#-#AUTOBUILDNUM#.exe"
#CERT_FOLDER#\SignTool.exe sign /n "{REDACTED_STORED_SIGNING_CERT_COMPANY}" /as /fd SHA256 /tr http://timestamp.comodoca.com/rfc3161/?signature=sha2 /td SHA256 "#PROJDIR#\Release\Single\#TITLE#_#ROLE#_v#DISPVERSION#-#AUTOBUILDNUM#.exe"
The final output #TITLE#_#ROLE#_v#DISPVERSION#-#AUTOBUILDNUM#.exe correctly contains two digital signatures, one SHA1 and one SHA256.
No errors are generated when building this within the IDE, but when the Run Without Debugging (Green Arrow) is clicked after a successful build, the reported dialog always pops up.
A: Yes, because I can run the finished compressed single .exe from the #PROJDIR#\Release\Single folder and it runs correctly.
Q: "Are you sure that those you entered effectively match with the build mode you used?"
A: Here is the PostCompress Event script used for a Single Compressed .EXE setup output:
NOTES:
(1) The compiler variable #ROLE# referenced below contains either "Setup" or "Updater". In production builds, this variable is set on the miabuild.exe command line. In the IDE, the value is "Setup". It is used in creating the final output filename.
(2) The compiler variable #DISPVERSION# referenced below contains the full 4 digit version number of the primary executable to be installed named #TITLE#.exe. It is also used in creating the final output filename.
(3) The compiler variable #AUTOBUILDNUM# referenced below contains the Bamboo Build number. It is also used in creating the final output filename.
#CERT_FOLDER#\SignTool.exe sign /n "{REDACTED_STORED_SIGNING_CERT_IDENTIFIER}" /t http://timestamp.comodoca.com/rfc3161 "#PROJDIR#\Release\Single\#TITLE#_#ROLE#_v#DISPVERSION#-#AUTOBUILDNUM#.exe"
#CERT_FOLDER#\SignTool.exe sign /n "{REDACTED_STORED_SIGNING_CERT_COMPANY}" /as /fd SHA256 /tr http://timestamp.comodoca.com/rfc3161/?signature=sha2 /td SHA256 "#PROJDIR#\Release\Single\#TITLE#_#ROLE#_v#DISPVERSION#-#AUTOBUILDNUM#.exe"
The final output #TITLE#_#ROLE#_v#DISPVERSION#-#AUTOBUILDNUM#.exe correctly contains two digital signatures, one SHA1 and one SHA256.
No errors are generated when building this within the IDE, but when the Run Without Debugging (Green Arrow) is clicked after a successful build, the reported dialog always pops up.
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Please build your project before running without debugging
Dear Erich,
I don't believe your problem is caused by the defined build events.
I suspect instead that the build mode defined with your project doesn't match the effective build produced.
For example;
- with the project the build mode is defined as Uncompressed:
- but the build gets started using one of the following menu:
- finally if you try to run the generated package using the Green Arrow, of course you will receive the following warning:
Regards
I don't believe your problem is caused by the defined build events.
I suspect instead that the build mode defined with your project doesn't match the effective build produced.
For example;
- with the project the build mode is defined as Uncompressed:
- but the build gets started using one of the following menu:
- finally if you try to run the generated package using the Green Arrow, of course you will receive the following warning:
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
-
- Posts: 32
- Joined: Mon Oct 29, 2012 2:27 pm
Re: Please build your project before running without debugging
Sorry for the late followup. The Build Settings for this project is set to Compressed Single Self Installing EXE. The rest of the settings are as previously shown.
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Please build your project before running without debugging
Dear Erich,
you may try to send me your project .... because I am able to replicate this behavior as you reported.
Regards
you may try to send me your project .... because I am able to replicate this behavior as you reported.
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
-
- Posts: 32
- Joined: Mon Oct 29, 2012 2:27 pm
Re: Please build your project before running without debugging
Did you mean the .mpr file or the entire project folder and its contents?
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Please build your project before running without debugging
Dear Erich,
of course I mean you project or a very minimal (which is better) version of it.
To the test the project, I need to build it and due of this, this must include any single file it uses.
Regards
of course I mean you project or a very minimal (which is better) version of it.
To the test the project, I need to build it and due of this, this must include any single file it uses.
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
-
- Posts: 32
- Joined: Mon Oct 29, 2012 2:27 pm
Re: Please build your project before running without debugging
Sorry for the delayed reply. Management requires that all sensitive information in our source files and scripts be 'sanitized' if they are sent out of house and since my last post I have had other priorities assigned of late.
I now have a management approved, sanitized version of the installer project that the IDE won't run in either debug or not-debug mode. The project builds correctly from the build drop down menu and from the command line. The built installer runs from both Windows Explorer and the command line correctly.
Since I don't know what might be causing this, I can only provide the full project and the support files. Zipped up it's still 351MB. How can I deliver this to you for your examination?
I now have a management approved, sanitized version of the installer project that the IDE won't run in either debug or not-debug mode. The project builds correctly from the build drop down menu and from the command line. The built installer runs from both Windows Explorer and the command line correctly.
Since I don't know what might be causing this, I can only provide the full project and the support files. Zipped up it's still 351MB. How can I deliver this to you for your examination?
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Please build your project before running without debugging
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Please build your project before running without debugging
Dear Erich,
I had a look at the project you sent me and the problem you reported, it's caused by the compiler variables (#TITLE#_#OUTPUT_FILENAME_SUBTYPE##ROLE#_v#DISPVERSION#-#AUTOBUILDNUM#) used to specify in the "Output filename" field (project "Build Settings").
Compiler variables can be only resolved at build time. So to solve your problem, just replace them with a literal file name or leave the field blank.
Hope this helps you.
Regards
I had a look at the project you sent me and the problem you reported, it's caused by the compiler variables (#TITLE#_#OUTPUT_FILENAME_SUBTYPE##ROLE#_v#DISPVERSION#-#AUTOBUILDNUM#) used to specify in the "Output filename" field (project "Build Settings").
Compiler variables can be only resolved at build time. So to solve your problem, just replace them with a literal file name or leave the field blank.
Hope this helps you.
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
-
- Posts: 32
- Joined: Mon Oct 29, 2012 2:27 pm
Re: Please build your project before running without debugging
Thanks for looking at it but the compiler variables you listed as being the problem (#TITLE#_#OUTPUT_FILENAME_SUBTYPE##ROLE#_v#DISPVERSION#-#AUTOBUILDNUM#) all have default definitions (see screen caps attached)
NOTE: According to IA documentation, #TITLE# is an IA Pre-Defined compiler variable set to the value of the Product in the Project settings and so I assume that is why it doesn't show up in the list of Compiler Variables. Is that correct? Or do I need to explicitly define a compiler variable named TITLE and set a default value for it?
Why would these default values not be used when running from the IDE after building it in the IDE?
NOTE: According to IA documentation, #TITLE# is an IA Pre-Defined compiler variable set to the value of the Product in the Project settings and so I assume that is why it doesn't show up in the list of Compiler Variables. Is that correct? Or do I need to explicitly define a compiler variable named TITLE and set a default value for it?
Why would these default values not be used when running from the IDE after building it in the IDE?
- Attachments
-
- IAFailedBuildDemoCompVarsDefValsCapture1.PNG (14.57 KiB) Viewed 8790 times
-
- IAFailedBuildDemoCompVarsDefValsCapture2.PNG (29.33 KiB) Viewed 8790 times
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Please build your project before running without debugging
Dear Erich,
I suppose there was a misunderstanding.
All your compiler variables are defined correctly and used properly. So how these are used to generate the output filename it's absolutely correct.
However all these variables, because are compiler variables, can be only resolved during build time. In other words, once the build process is completed, the IA IDE will be not able to resolve such variables and consequently, it'll be not able to run the generated package. It tries to run a file which is "literally" called "#TITLE#_#OUTPUT_FILENAME_SUBTYPE##ROLE#_v#DISPVERSION#-#AUTOBUILDNUM#.exe" ... and of course such file doesn't exist.
Finally and if you want to run the package from IA IDE, you may "temporarily" replace them with a literal file name or to leave the field blank.
Unfortunately in this case, it doesn't exist a different workaround that can be used.
I'll check with our dev team the possibility to have this feature with future product release.
Hope this helps you.
Regards
I suppose there was a misunderstanding.
All your compiler variables are defined correctly and used properly. So how these are used to generate the output filename it's absolutely correct.
However all these variables, because are compiler variables, can be only resolved during build time. In other words, once the build process is completed, the IA IDE will be not able to resolve such variables and consequently, it'll be not able to run the generated package. It tries to run a file which is "literally" called "#TITLE#_#OUTPUT_FILENAME_SUBTYPE##ROLE#_v#DISPVERSION#-#AUTOBUILDNUM#.exe" ... and of course such file doesn't exist.
Finally and if you want to run the package from IA IDE, you may "temporarily" replace them with a literal file name or to leave the field blank.
Unfortunately in this case, it doesn't exist a different workaround that can be used.
I'll check with our dev team the possibility to have this feature with future product release.
Hope this helps you.
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
-
- Posts: 32
- Joined: Mon Oct 29, 2012 2:27 pm
Re: Please build your project before running without debugging
Ohhhhh! The "build" used by the Run From IDE actions don't resolve the compiler variables, it uses the value in the project output name box as a string literal for the IDE "build", right? I'll try using some string literal as the project output name temporarily while debugging and running from the IDE and then change it back to the compiler variable concatenation when we push it to the repo for building it from the command line miabuild.exe, where we define values for those compiler variables for each specific build configuration.
-
- Posts: 32
- Joined: Mon Oct 29, 2012 2:27 pm
Re: Please build your project before running without debugging
Using some string literal as the project output name successfully allows debugging and running from the IDE.
Thanks.
Thanks.
Who is online
Users browsing this forum: No registered users and 37 guests