cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
installdotnet
Level 3

Licensing Problem With Windows VISTA

Hi All,

I have created an application in .NET. I am using InstallShield 2009 Premier edition for creating Setup. I have created a trialware build of my application. Its running fine in Windows XP but the application does not run in Windows VISTA. Its not even giving any error message.:confused:
Labels (1)
0 Kudos
(3) Replies
jw1207
Level 2

Hi,
The help does say it doesn't work with .net applications and gives a workaround.
So I followed this and Ive done a try and die with a simple c++ native console application. The app runs in XP, throws an exception in Vista.

Anybody have any ideas?

(Using IS2009, premier, latest, VS2008 latest)

Thanks, john
0 Kudos
KathyMorey
Level 10

My first two suggestions would be:
1. If you haven't already, validate you install project to see if that gives you any errors.

2. If you haven't already, log the install and see if the log file provides any clues.

Last, a little more detail about the exact error may help.
0 Kudos
jw1207
Level 2

Hi,

Some more details to add to my previous post. Ive been playing with the validations, which seem to have their own problems, and finally managed to make some sense out of them.

Im using VS2008 and created an unmanaged c++ console app which just writes hello to a console window, 3 lines of code.

Using IS2009 premier, stand alone.
I use the project wizards to check for dependencies and add the trialware file for try and die.
It produces no errors in building and passes all the validations (Win 2000, Full MSI, WinXP, Best Practice), except for the Vista one:


Loading File table
Wrapping trialware file TrialTest8.exe
Wrapping trialware file SCResetLicense.exe
Building File table



Validating against ISVista.cub...
ISDEV : error ISICE02: File TrialTest8.exe in Component TrialTest8.exe is not digitally signed. All .exe files distributed to Windows(R) Vista must be signed. File File trialtest8.exe
ISDEV : error ISICE02: File IsSvcInstTrialTest8.dll in Component TrialTest8.exe is not digitally signed. All .dll files distributed to Windows(R) Vista must be signed. File File IsSvcInsttrialtest8.dll
ISDEV : error ISICE02: File msvcm90.dll in Component nosxs.30729.01.Microsoft_VC90_CRT_x86.SP.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC is not digitally signed. All .dll files distributed to Windows(R) Vista must be signed. File File nosxs_msvcm90.dll.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC
ISDEV : error ISICE02: File msvcm90.dll in Component uplevel.30729.01.Microsoft_VC90_CRT_x86.SP.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC is not digitally signed. All .dll files distributed to Windows(R) Vista must be signed. File File ul_msvcm90.dll.30729.01.Microsoft_VC90_CRT_x86.SP.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC
ISDEV : error ISICE02: File msvcm90.dll in Component downlevel_payload.30729.01.Microsoft_VC90_CRT_x86.SP.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC is not digitally signed. All .dll files distributed to Windows(R) Vista must be signed. File File msvcm90.dll.30729.01.Microsoft_VC90_CRT_x86.SP.D8D85FD0_537C_3A3A_9BEC_7A1B426637EC
ISDEV : error ISICE09: An MsiPatchCertificate table entry is required for User Account Control (UAC) patching MsiPatchCertificate
ISDEV : error ISICE10: Custom action SxsInstallCA of type 1 is not documented in table ISCustomActionReference CustomAction Action SxsInstallCA
ISDEV : error ISICE10: Custom action SxsUninstallCA of type 1 is not documented in table ISCustomActionReference CustomAction Action SxsUninstallCA
ISDEV : error ISBP19: File IsSvcInstTrialTest8.dll in Component TrialTest8.exe imports deprecated API KERNEL32.dll!IsBadWritePtr File File IsSvcInsttrialtest8.dll
ISDEV : error ISBP19: File IsSvcInstTrialTest8.dll in Component TrialTest8.exe imports deprecated API KERNEL32.dll!IsBadReadPtr
ISDEV : error ISBP19: File IsSvcInstTrialTest8.dll in Component TrialTest8.exe imports deprecated API KERNEL32.dll!IsBadCodePtr
Completed validation against ISVista.cub


The try and die setup.exe works on XP but not on Vista machines.

Looking at the errors, apart from the 'digital signed' errors the only errors come from the file installshield itself produces.

What have I missed?


Thanks for any help here, john


John Watkinson, Developer
0 Kudos