SetupBuilder 6 vs 4

[NewsArchive]

Hi Friedrich

In version 4, you do a static scan, and it detects all the dependant
files, and if you accept all, it would only add the ones that you
didn't have in the project. But in version 6, this duplicates the list
and i have to delete the duplicates....

I also have some sugestions.
- when you are in the files and folders visualizer in the window where
you have your included files, and you select one, you should be able to
right click it and have an option to position the directory on the
upper side, so you can include some more files from the same dir.

- also it would be nice to have an auto scan feature, when you are
compiling. The thing is that i add a new 3rd party but didn't include
it's dll because i forget to do the scan again.

Thanks

Andres Sanchez R.

[NewsArchive]

Hi Andres,

> In version 4, you do a static scan, and it detects all the dependant
> files, and if you accept all, it would only add the ones that you didn't
> have in the project. But in version 6, this duplicates the list and i have
> to delete the duplicates....

Ben Riebens reported a similar problem. Unfortunately, we cannot reproduce
this here. Perhaps it has something to do with "case sensitiveness". Item
is still in review.

> I also have some sugestions.
> - when you are in the files and folders visualizer in the window where you
> have your included files, and you select one, you should be able to right
> click it and have an option to position the directory on the upper side,
> so you can include some more files from the same dir.

Sorry, I don't know exactly what you mean.

> - also it would be nice to have an auto scan feature, when you are
> compiling. The thing is that i add a new 3rd party but didn't include it's
> dll because i forget to do the scan again.

IMO, it is not a good idea to have such an "auto-scan" at compile time.
What happens if the Scan detects OS specific files or files that you should
not redistribute?

For example:
You do an auto-scan on a machine with IE7. The compiler would include
C:\WINDOWS\system32\Normaliz.dll and C:\WINDOWS\system32\iertutil.dll. But
you are not allowed (and you should not) redistribute these files. Or on
Vista, it may detect a NSI.dll file. This should also not be distributed.
The next SetupBuilder 6.5 build lists the NSI.dll, Normaliz.dll and
iertutil.dll in the sbscan.ini "exclude" file. But the list is growing and
growing, and with an auto-scan you would lose control (IMO).

Friedrich

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

"point. click. ship" - that's SetupBuilder 6.5
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

What would be an idea, is to optionally include the ship (shp) file as a
source for files, and on each build, check the files against the ship file.

This is then of cause the programmer;s responsibility to make sure that his
templates and 3'rd party register correctly in the ship file during compile
time...

ben

[NewsArchive]

Ben,

> What would be an idea, is to optionally include the ship (shp) file as a
> source for files, and on each build, check the files against the ship
> file.
>
> This is then of cause the programmer;s responsibility to make sure that
> his templates and 3'rd party register correctly in the ship file during
> compile time...

We played with .shp files (this goes back to SB4 and SB5) but most ship
files do not include the full qualified path name. Two or three years ago
we asked Clarion developers to send us their .shp files (we have about 300
now). It turned out that it does not make sense to use .shp files.

Thank you for your suggestion!

Friedrich

[NewsArchive]

Hi friedrich:

> IMO, it is not a good idea to have such an "auto-scan" at compile time.
> What happens if the Scan detects OS specific files or files that you should
> not redistribute?
>
> For example:
> You do an auto-scan on a machine with IE7. The compiler would include
> C:\WINDOWS\system32\Normaliz.dll and C:\WINDOWS\system32\iertutil.dll. But
> you are not allowed (and you should not) redistribute these files. Or on
> Vista, it may detect a NSI.dll file. This should also not be distributed.
> The next SetupBuilder 6.5 build lists the NSI.dll, Normaliz.dll and
> iertutil.dll in the sbscan.ini "exclude" file. But the list is growing and
> growing, and with an auto-scan you would lose control (IMO).

It was not talking about an auto scan (silent) option, it could be the
same static scan, just called in automatically when compiling, the
window will pop up, and you have to select the ones you want, after
hitting ok, compiling continues.

Or even more simple, one of the properties of the added files could be
a check to mark it for static scan, and you can have a button before
the compile button in the toolbar, so I can press and not have to look
for the file or files to scan, and just add them before compile.

Does this sound better ?


Thanks
Andres Sanchez

[NewsArchive]

Hi Friedrich,
>
>> In version 4, you do a static scan, and it detects all the dependant
>> files, and if you accept all, it would only add the ones that you didn't
>> have in the project. But in version 6, this duplicates the list and i have
>> to delete the duplicates....
>
> Ben Riebens reported a similar problem. Unfortunately, we cannot reproduce
> this here. Perhaps it has something to do with "case sensitiveness". Item
> is still in review.
>
Yes you are right the problem is because you are comparing with case
sensitivity, in all the path i might add. I don't know why do you
compare the Link Path to, you should compare only the file name, and
both UPPER()'ed.

I am attaching an image so you can look at it.

Thanks
Andres Sanchez

[NewsArchive]

Andres,

> It was not talking about an auto scan (silent) option, it could be the
> same static scan, just called in automatically when compiling, the window
> will pop up, and you have to select the ones you want, after hitting ok,
> compiling continues.

IMO, this would open the door for trouble. What if you have to
self-register, register as shared file, etc. specific dependency files?
This process should not be part of the compilation process (IMO).

> Or even more simple, one of the properties of the added files could be a
> check to mark it for static scan, and you can have a button before the
> compile button in the toolbar, so I can press and not have to look for the
> file or files to scan, and just add them before compile.
>
> Does this sound better ?

I have to give this some thoughts. You can already do a static scan from
the lower right files list, so from the technical point of view it would be
possible.

Thank you for your suggestions.

Friedrich

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

"point. click. ship" - that's SetupBuilder 6.5
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner