PDA

View Full Version : Warning GEN1116: Corrupt File Properties detected



NewsArchive
04-14-2015, 09:24 AM
All,

In the new SetupBuilder 2015 Version 8.5 Build 4753 there is a more strict
compiler check to detect "corrupt file properties".

There are still quite a few older project files out there with missing file
properties for Windows 8.0, 8.1 and 10. Even our own (very) old
SetupBuilder projects did not have the new properties. Because we create
Windows version independent installations, this does not cause problems.
But if you have selected the operating systems on which the file should be
installed (File Properties -> Conditions tab) then you need the new
properties.

To fix the problems, you can double-click the file to open the File
Properties dialog. If necessary, please update the target operating system,
then click the "OK" button. SetupBuilder will update/fix the properties.

Or you can use the "File | Script Structure Validation" function. Please
note that this function will reset "damaged" properties to the SetupBuilder
default values. Please check each line for changes and manually adjust back
to your previous settings if any had settings that differed from the
default!

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

--Helping You Build Better Installations
--SetupBuilder "point. click. ship"
--Create Windows 10 ready installations in minutes
--Official COMODO Code Signing and SSL Certificate Partner

NewsArchive
04-14-2015, 09:25 AM
We'll make the new SetupBuilder update available tomorrow. Just wanted to
make sure you are prepared for the "GEN1116" compiler warning...

Friedrich

NewsArchive
04-15-2015, 01:36 AM
Just to be clear, if I don't set an installer for a given version of
Windows, I've nothing to worry about?

--

Russ Eggen
RADFusion International, LLC

NewsArchive
04-15-2015, 01:36 AM
Hi Russ,

Yes, that is correct. If you have set the Target OS Conditions in the File
Properties to "OS Independent" then you have nothing to worry about.

Friedrich

NewsArchive
04-16-2015, 04:29 AM
Quick update: I have enhanced the "File > Script Structure Validation"
function in Build 4754. You can use this function to fix the problems after
the compiler detected corrupt or missing file properties.

It will "add" (and NOT reset) the required properties if missing file
properties have been detected and "re-create" the properties if corrupt file
properties have been detected (this will reset "damaged" properties to the
SetupBuilder default values).

Friedrich

NewsArchive
05-25-2015, 02:44 AM
Friedrich,

> Yes, that is correct. If you have set the Target OS Conditions in the File
> Properties to "OS Independent" then you have nothing to worry about.

Suggestion for future release; If this option is set then correct the
change in the background and leave my blood pressure where it is! <g>

--
Lee White

RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
RPM Review........: http://www.clarionmag.com/cmag/v11/v11n06rpm.html
Report Faxing.....: http://www.cwaddons.com/products/afe/
---Enroll Today---: http://CWaddons.com

Creative Reporting: http://www.CreativeReporting.com

Product Release & Update Notices
http://twitter.com/DeveloperPLUS

Windows 8 brings us "The Oval, Bumper Car, Roller Coaster of Wait!"
And, now, Windows 10 brings us "The Inch Worm, Bumper Car of Wait!"

NewsArchive
05-25-2015, 02:45 AM
Lee,

> Suggestion for future release; If this option is set then correct the
> change in the background and leave my blood pressure where it is! <g>

Quite a few developers hate automatic changes to their projects <g>.

To disable the check:

Tools > Options... > Skip 'Script Structure Validation' and you are done <g>

Friedrich

NewsArchive
05-26-2015, 01:10 AM
Friedrich,

> Tools > Options... > Skip 'Script Structure Validation' and you are done <g>

But then it's on ME, not YOU, if it breaks!<g>

In local, hillbilly, vernacular; "I'm too afeared!!"

Lee White