SB7.1.2860 issue

[NewsArchive]

Hi Friedrich,

Build 7.1.2860 STILL saves .SB6 files that are converted and saved to .SB6
files instead of .SB7. We went over this in September or October last year
but I still don't get why SB7 doesn't save SB7 files.

If you compile a SB7 project in SB6 then some features are or can be
missing. For example if I compile an install that has the "Clarion 7.1"
detection (as well as 7.0) enabled in SB6 it will show up as "Clarion 7.0"
instead of "Clarion 7.1". So compiling SB7 projects in SB6 can IMO produce
unpredictable results.

So my question is: Why can't SB7 correctly convert the filename to use its
associated ".SB7" extension when it converts the project from SB6 to SB7 and
saves it?

Best regards,

--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> So my question is: Why can't SB7 correctly convert the filename to use
> its associated ".SB7" extension when it converts the project from SB6 to
> SB7 and saves it?

---
SetupBuilder 7.0 Build 2734 (September 29, 2009)

CHANGE : IDE: File "Save as..." saves projects with .sb7 extension.
---

Just checked this and I opened test.sb6 and then selected "Save As...". It
saved it to test.sb7.

BTW, SB7 does not really "convert" .sb6 to .sb7. It just adds some new
properties. You can still open "SB7 converted" .sb6 file in your SB6
IDE and compile it.

Thanks,
Friedrich

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

SetupBuilder is Windows installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

BTW, quite a few customers are using batch compilers to automate the
deployment process. SB7 does not automatically change .sb6 to .sb7 so
developers do not have to modify all their batch process files. For
example, we have large companies with 1000+ different .sb6 batch processes.
They are using SB7 now but it would be a nightmare to change all the
references from .sb6 to .sb7.

Friedrich

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

SetupBuilder is Windows 7 installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

> BTW, quite a few customers are using batch compilers to automate the
> deployment process. SB7 does not automatically change .sb6 to .sb7 so
> developers do not have to modify all their batch process files. For
> example, we have large companies with 1000+ different .sb6 batch processes.
> They are using SB7 now but it would be a nightmare to change all the
> references from .sb6 to .sb7.

Understood, but could there be a switch that defaulted to OFF that let the
IDE save the converted script to SB7 extension? I sure as heck would rather
make sure that the script was compiled using the right compiler!!!<g>

Best regards,

--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Friedrich,

> BTW, SB7 does not really "convert" .sb6 to .sb7. It just adds some new
> properties. You can still open "SB7 converted" .sb6 file in your SB6
> IDE and compile it.

Yes, but the results are NOT the same. See my example about the Clarion 7.0
and Clarion 7.1. When compiled in SB6 the Clarion 7.0+Clarion 7.1 option
becomes Clarion 7.0 only. Obviously there are some changes or we wouldn't
need SB7 at all, we could just use SB6<bg>

Best regards,

--
Arnór Baldvinsson - Icetips Alta LLC
Port Angeles, Washington
www.icetips.com - www.buildautomator.com - www.altawebworks.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

> Yes, but the results are NOT the same. See my example about the Clarion
> 7.0 and Clarion 7.1. When compiled in SB6 the Clarion 7.0+Clarion 7.1
> option becomes Clarion 7.0 only. Obviously there are some changes or we
> wouldn't need SB7 at all, we could just use SB6<bg>

Yes, but the same would happen with a .sb7 compiled with SB7.0 <g>. No
Clarion 7.1 support at all <g>. We introduced support for C71 in SB71.

Friedrich