Randem Systems Support Board

got it, thx, I'll notify you when more work is accomplished.  Thank you for your support.

OK, when you do get time; please make sure you download the latest version from the website to test with.

Thanks, But not doing Any Deployment tests on any Developemnt machines....& we do use Virtual Machines on the other test hardware.  
 
It's the IDE, among some others, that breaks immediately after first run of InnoScript with SxS employed.  Appears to me that these Breaks  occur because InnoScript 'moves' some of the registrations when SxS is used.  
 
Thanks again but my schedule precludes me from performing more testing at this time. thx!

It occurred to me that if you are using your development machine to test with all sorts of malady's can happen such as the ones you mentioned. I would suggest that if you want to test on your machine that you use Microsoft's Virtual PC 2007 SP1. You can start with a clean system each time and not have to worry about corrupting your development environment.

The offer was to create your script for you. All our applications on the web have WinSxS versions and something that bad would have surfaced by now on our development systems. This is why we offered to create your script for you at no cost for we want to see this issue that we have not seen before and we have a few applications out there with WinSxS versions created in InnoScript. We want to resolve this issue.

Yes, I did comment out some lines because InnoScript had a problem with safe mode, or input file location, or some other etc.... I suggest not an issue for the subject analysis.  
Also, some of the file names were changed prior to my post to you so as to protect some sensitive info.... again not critical to this analysis.  
 
As far as duplicate manifest entry, perhaps a result of my input edit but, as u say, one will not recall  
Anyway, duplicate manifest of same name is not functional... I'd call that an error, and thanks for pointing it out.  
 
As far as breaking existing apps, it happens and is repeatable and takes me a few hours to recover via an image restore... I've already delineated with you one of the problems relative to DAO350.DLL as pertains to InnoScript re-registering at a different location and thus breaking VB6... you offered fix but it's manual & time consuming for all the dll's and offers  error..... there are others... sorry but I've just been told I do not have time to go further, thus:  
 
I thank you for your offer to do further analysis.... that must be sometime in future as time on this for me at present has again run out.  
 
Bests & thank you for your support!

InnoScript will not check for duplicates or add duplicate unless you have instructed it to do so in a template. InnoScript nor any compiler should check for duplicates for they are meaningless. Editing of the script should be done via a template not manually for results may vary and you may not remember where changes came from. I see the script and immediately know what changes were done manually.
 
I can see that the script was edited, there are lines commented out and added of which InnoScript would not ever do unless instructed to do so in a template; and since you state that you are not using the template function, these lines had to be added and commented out manually. Here is an example:
 
;must be XP or above OS:
;OnlyBelowVersion=,5.1.2600sp3
MinVersion=0,5.1.2600sp3
 
There is no way InnoScript would have done this. This should have been done on the main screen on the Versioning tab with the selection buttons. There was no reason to edit the script to get the proper results. Other such edits exist in the script. Once you start to do this you may not be able to tell who changed what or when it was changed.
 
InnoScript does add manifest files but not duplicate ones... We use InnoScript here everyday to create scripts for others as well as for our products we deploy including WinSxS deployments. We do not have any broken IDE or other such issues with WinSxS deployments. Perhaps if you could zip the deployment files along with the vbp and exe, I will run InnoScript with them to generate the appropriate script that should be generated and I guarantee the script would not look the same as the one you have and would not break ANY of our applications here.

Can't send any manifests as all have been lost.  
This because InnoScript run using SxS caused app issues which were broken/severe (a number of apps including IDE would not launch, etc) and thus a system backup image was employeed.

Please refer to ** insert replies below:  
 
In your script you are duplicating lines such as Source: C:TT-VB6TrilDistrib_INNOManifestTT-.exe.manifest; DestDir: {app}; Flags: ignoreversion;
 
**
Nope.. no intention to do that... One would think that a script generator (or the compiler) would check for dups.... not intentionally from me, but I'll ~try to go thru the script and check for dups.  
I've not purposely added any lines to the script other than that which would occur from the individual [AddFiles].  
I do not recall EVER adding any Manifest files; I suggest that Any Manifest entries have been performed by InnoScript.  
**
 
 
You may not be using the templates as you should (recommended) or modifying lines manually (not recommended). When you modify lines manually without using the templates to do the modification; you may forget or not type the lines the same each time leading to incorrect results and/or duplications.  
 
**
We've not intentionally used any templates, and never intended to use any templates.  The process was that we directed InnoScript to produce per the VBP, then we added the various app reference files (pdf's, txt, etc), then we selected [ADD] from the SxS so as to provide most secure use of the registered libraries, etc.  
**
 
 
I don't see a database in your script but you have database modules in the script. If you are deploying a database in the {app} folder and it is deployed in the {pf}, {pf32}, {pf64} folders (not recommended) you will experience issues related to maintenance with the database.
 
**  
There is no specific database in the script.  
DB's are manufactured realtime via app generation &/or import.  
This is a dynamic process and needs are constantly changed.  
The primary DB driver is SQL however Jet and other via ADO are also offered in the app.  
Note that the script Dependencies are generated per InnoScript.  
**

In your script you are duplicating lines such as Source: C:\TT-VB6\TrilDistrib_INNO\Manifest\TT-.exe.manifest; DestDir: {app}; Flags: ignoreversion;
 
You may not be using the templates as you should (recommended) or modifying lines manually (not recommended). When you modify lines manually without using the templates to do the modification; you may forget or not type the lines the same each time leading to incorrect results and/or duplications.
 
I don't see a database in your script but you have database modules in the script. If you are deploying a database in the {app} folder and it is deployed in the {pf}, {pf32}, {pf64} folders (not recommended) you will experience issues related to maintenance with the database.
 
InnoScript is designed to help keep you from manually modifying lines so that each time you can generate the same exact script if you need to or modify just the lines you need to automatically.

Sorry, I forgot to ask for the manifest file also... Could you zip and post that too.
 
Have you tried the trial and error approach yet?

Yes, you probably will have that error on some applications. It is noted in the manual you will need to figure out which ocx.dll/exe that you are adding to the WinSxS deployment cannot be there then you can add them to the [WinSxS] section of the UnSafe.Fil file. There are some files that will not work in a Side-by-Side environment. You will need to add one file at a time to the WinSxS deployment till you find the file(s) that cannot work in that environment and not add them. It is a trial and error approach but that is the only one that will work consistently.
 
When using WinSxs if you have files that are to be registered they will be registered as normal. If you have files the are to be deployed as WinSxS, a Manifest will be created for these files and they are NOT registered in the normal fashion.
 
Please post your script so that I may take a look.

SxS problems continue:  
I apparently have your most recent update, per app checking at launch {ver 10.5 build 4}, and I'm receiving there is a problem with the application on launch attempt after deployment to 3rd party computers when employing InnoScript SxS for the InnoScript recommended files.  
All appears ok when not using SxS.  
Additionally, when using SxS, InnoScript reregister DAO350.dll and others so that VB6 IDE does not launch, etc.

Ok, re-uploaded. Download again it should solve the issue.