Randem Systems Support Board

InnoScript => InnoScript - General Questions, Report Bugs, Problems etc... => Topic started by: philippe on May 20, 2011, 01:50:49 AM

Title: Issue with .NET script generation?
Post by: philippe on May 20, 2011, 01:50:49 AM
Aloha again,
 
Using the latest Innoscript (prior to 10.5.07 I just saw right now and which I did not download yet).
 
I am revisiting the .NET script creation and I seem to experience some issues:  
 
My prog is called CC2Xcal.
 
- When the script is generated, there is no mention of the exe name in the [Files] section
- [Icons] and [Run} sections: see below:
 
[Icons]
Name: {group}\CC2Xcal ; Filename : {app}\; WorkingDir: {app};                                  EXE name missing
Name: {group}{cm:UninstallProgram, CC2Xcal }; Filename: {uninstallexe};                 OK
Name: {commondesktop}\CC2Xcal ; Filename: {app}\cc2xcal.exe; Tasks: Desktopicon ; WorkingDir: {app};
 
[Run]
Filename: {app}\; Description: {cm:LaunchProgram, CC2Xcal }; Flags: nowait postinstall skipifsilent runascurrentuser; WorkingDir: {app}
 
Here again the name of the exe is missing
 
Am I doing anything wrong?
 
Also, how do I include a checkbox to add the DotNet install? (Tasks section of the Innosetup script)...DotNETInstall.tpl is defined in my templates but I can't seem to make this box display..
 
Has it tested that it's installed on my machine?
 
Thanks and mahalo
 
Uploading a zip with my exe, pjt and .vbproj files
 
Cheers
 
Philippe
Title: Issue with .NET script generation?
Post by: Randem on May 20, 2011, 11:03:25 AM
Ok, There was an issue with the exe file entry being generated. try this version. Also you should be checking for unsafe files, using relative paths etc...
 
Title: Issue with .NET script generation?
Post by: Randem on May 20, 2011, 11:09:28 AM
BTW: I did not see your script. The selections for the .NET installs are there in the script I generated. What version of InnoScript are you using?
Title: Issue with .NET script generation?
Post by: Randem on May 20, 2011, 06:08:07 PM
Also if you are attempting to see the check box for the .NET installations, they will not occur if the .NET installation is already present. If you want to make the check box appear anyway then remove the check for the .NET installation in the [Tasks] section and it will always appear. Otherwise it will only appear when the .NET installation is not already installed on the target machine.
 
[Tasks]
Name: DotNetFramework35sp1; Description: Install .Net Framework; GroupDescription: .Net Framework:; Check: InstallDotNET35(1)
Name: DotNetFramework40; Description: Install .Net Framework; GroupDescription: .Net Framework:; Check: InstallDotNET40(0)
 
will be changed to:
 
[Tasks]
Name: DotNetFramework35sp1; Description: Install .Net Framework; GroupDescription: .Net Framework:;  
Name: DotNetFramework40; Description: Install .Net Framework; GroupDescription: .Net Framework:;
Title: Issue with .NET script generation?
Post by: Randem on May 20, 2011, 06:54:24 PM
An update to InnoScript:
 
 
 
Note: Should only be used after installing Innoscript 10.5 Build 8
Title: Issue with .NET script generation?
Post by: philippe on May 20, 2011, 09:14:15 PM
Replying to your second post: was using 10.5 build 3 at the time of the issue. Will update to build 8 then 9 and recheck Monday...
 
Thx
 
Philippe
Title: Issue with .NET script generation?
Post by: Randem on May 20, 2011, 10:10:01 PM
Also the new Unsafe file should be used.
 
Title: Issue with .NET script generation?
Post by: philippe on May 24, 2011, 09:10:57 PM
Hmmm...Almost there but not yet...
Looks like everything is there, except the EXE file in the Files section.
 
Tested all. Uninstall works too.
 
See attached .iss file
 
Thx
 
Philippe
 
(Message edited by philippe on May 24, 2011)
Title: Issue with .NET script generation?
Post by: Randem on May 24, 2011, 09:20:54 PM
Ok, still making changes... Try this one.
 
Title: Issue with .NET script generation?
Post by: philippe on May 24, 2011, 09:33:57 PM
Better...Except that this one installs the EXE from bindebug whereas I specified Release in the Install Release Type section.
Title: Issue with .NET script generation?
Post by: Randem on May 24, 2011, 09:42:13 PM
You need to tell InnoScript that it should not use that folder for searches by placing the folder in the Exclude Tab.
Title: Issue with .NET script generation?
Post by: philippe on May 24, 2011, 09:43:13 PM
OK...Trying...
Title: Issue with .NET script generation?
Post by: philippe on May 24, 2011, 09:50:43 PM
Cool...This works...
However, from a usability standpoint, I would assume that pressing the Release button defaults to search the release version in \bin\release, without having to exclude the debug dir since it's a toggle on/off type thing..
 
French way of thinking  
 
Thanks again
 
Philippe
Title: Issue with .NET script generation?
Post by: Randem on May 24, 2011, 09:56:18 PM
No, The release button is an InnoScript option only. It is not related to VB.NET... and there is no Release/Beta Option for VB6 or the other situations InnoScript handles.
Title: Issue with .NET script generation?
Post by: philippe on May 24, 2011, 10:02:00 PM
True but something like this should work, shouldn't it?
 
if VB.NET then
    If Release Then
       Look for binrelease
    Else
       Look for bindebug
    Endif
Endif  
 
No sweat...Just food for thoughts...
 
Thanks again for your great support.
 
Phil
Title: Issue with .NET script generation?
Post by: Randem on May 24, 2011, 10:04:05 PM
No, because that is not what the Release button is for...