Deploying

[NewsArchive]

Hi Friedrich,

In SB 6 we have the option to deploy the install to an FTP server. How
about just deploying it to another drive<g> I'm working with one VM to
compile and develop and another one to test. So after I compile the SB
install I need to copy it to another drive (I'm not changing the output
folder for this). It would be very handy to be able to tell SB to copy the
file after it's compiled. Of course I could do it with BA, but this would
be very handy to have in SB for a quick copy once compiled:)

Sorry haven't got around to check if 7 can do it:(

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

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

[NewsArchive]

Arnor,

I faced the same problem till I realised it was just a question of changing
the path to the executable output dir ..... simple!

--

Thank you - Merci

Cordialement - Best Regards
Jean-Pierre GUTSATZ

DMC - Data Management Center - A tool to let you Migrate Import Export
Transfer all your Data very easily
www.dmc-fr.com
Certified by Microsoft : "Works with Vista" & "Works with Windows Server
2008"

[NewsArchive]

Hi Jean-Pierre

> I faced the same problem till I realised it was just a question of changing
> the path to the executable output dir ..... simple!

I do in other projects, but in this case I need it in another folder also.
You only have one output dir, I need two. An option to deploy locally would
be really handy:)

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

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

[NewsArchive]

Hi Arnór,

>> I faced the same problem till I realised it was just a question of
>> changing the path to the executable output dir ..... simple!
>
> I do in other projects, but in this case I need it in another folder also.
> You only have one output dir, I need two. An option to deploy locally
> would be really handy:)

Absolutely no problem ;-) You can use "#copy file..." to copy it to 1,000
different folders <g>

In our scripts, we automatically copy the setup.exe to a backup drive
H:\Backup\SetupBuilder\[VERSION], then to c:\releases\setupbuilder and to
\\VISTA64\Linder\test

Friedrich

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

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

> Hi Friedrich,
>
> In SB 6 we have the option to deploy the install to an FTP server. How
> about just deploying it to another drive<g> I'm working with one VM to
> compile and develop and another one to test. So after I compile the SB
> install I need to copy it to another drive (I'm not changing the output
> folder for this). It would be very handy to be able to tell SB to copy the
> file after it's compiled. Of course I could do it with BA, but this would
> be very handy to have in SB for a quick copy once compiled:)

Another useful copy feature would be to copy JUST the program EXE that has
been processed by SB (Vista Manifest, Armadillo protected, CodeSigned) and
send it to a specific folder WITHOUT having to Install it. THAT would be
very helpful and useful!

David

--
From David Troxell - Product Scope 7 - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
Profile Exchanges - www.encouragersoftware.com/profile/
http://www.profileexchanges.com/blog/

[NewsArchive]

Hi David,

> Another useful copy feature would be to copy JUST the program EXE that has
> been processed by SB (Vista Manifest, Armadillo protected, CodeSigned) and
> send it to a specific folder WITHOUT having to Install it. THAT would be
> very helpful and useful!

You should be able to accomplish that with the #copy compiler directive
after you manifest and codesign. The problem is that even if you put the
#copy as the last statement in the script it is performed early in the
compile process - or that's what it looked like to me - too early to make it
work with the install that is being compiled. However, I think if you had a
script with:

#embed vista manifest
#code sign
#copy file

it should work for what you are talking about.

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

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

[NewsArchive]

Arnor,

While after reading your message and Friedrich's - and using

#copy file - with - "Process after script compilation" option", it worked
EXACTLY as I need!

Thanks to you both for pointing to the solution!

David

--
From David Troxell - Product Scope 7 - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
Profile Exchanges - www.encouragersoftware.com/profile/
http://www.profileexchanges.com/blog/

[NewsArchive]

Hi David,

> Another useful copy feature would be to copy JUST the program EXE that has
> been processed by SB (Vista Manifest, Armadillo protected, CodeSigned) and
> send it to a specific folder WITHOUT having to Install it. THAT would be
> very helpful and useful!

What Arnór said. SetupBuilder can already handle this ;-)

Friedrich

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

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Friedrich,

THANK YOU Very Much!

After reading your post and Arnór's (AND THEN the help file!) - I realized
I had just overlooked it - works Exactly as I need!

Someone needs to write a "SetupBuilder Tips & Techniques" - however, it
might take about 10 "volumes" to cover it adequately! :-D

David

--
From David Troxell - Product Scope 7 - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
Profile Exchanges - www.encouragersoftware.com/profile/
http://www.profileexchanges.com/blog/

[NewsArchive]

Hi Arnór,

> In SB 6 we have the option to deploy the install to an FTP server. How
> about just deploying it to another drive<g> I'm working with one VM to
> compile and develop and another one to test. So after I compile the SB
> install I need to copy it to another drive (I'm not changing the output
> folder for this). It would be very handy to be able to tell SB to copy
> the file after it's compiled. Of course I could do it with BA, but this
> would be very handy to have in SB for a quick copy once compiled:)
>
> Sorry haven't got around to check if 7 can do it:(

The "#copy file..." compiler directive in the latest SetupBuilder 6.9 and
SetupBuilder 7.0 support the "Process after script compilation" option.
So you can copy the resulting setup executable to whatever location(s) you
want ;-)

Does this help?

Friedrich

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

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi David,

> THANK YOU Very Much!
>
> After reading your post and Arnór's (AND THEN the help file!) - I realized
> I had just overlooked it - works Exactly as I need!
>
> Someone needs to write a "SetupBuilder Tips & Techniques" - however, it
> might take about 10 "volumes" to cover it adequately! :-D

;-) I am sure we'll see such a "SetupBuilder Tips & Techniques & Everything
you ever wanted to know about SetupBuilder but were afraid to ask" in the
near future <g>

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

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

> The "#copy file..." compiler directive in the latest SetupBuilder 6.9 and
> SetupBuilder 7.0 support the "Process after script compilation" option.
> So you can copy the resulting setup executable to whatever location(s) you
> want ;-)
>
> Does this help?

YES - didn't notice that "after compilation" option!

Source: [OUTPUTDIR]\[EXENAME]
Dest: T:\install\client\new\[EXENAME]

The destination has to be full path AND filename. I.e. if I just use
"T:\install\client\new\" or "T:\install\client\new" it fails.

Best regards,


--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

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

[NewsArchive]

>> Does this help?
>
> YES - didn't notice that "after compilation" option!
>
> Source: [OUTPUTDIR]\[EXENAME]
> Dest: T:\install\client\new\[EXENAME]
>
> The destination has to be full path AND filename. I.e. if I just
> use "T:\install\client\new\" or "T:\install\client\new" it fails.

Yes, if you copy a single file then the "Destination" has to be
pathname\filename. I'll add a note to the documentation.

Thanks,
Friedrich

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

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

> Yes, if you copy a single file then the "Destination" has to be
> pathname\filename. I'll add a note to the documentation.

Or perhaps just strip the filename from the source if no wildcards are used
and use that? Same as "Copy c:\test.txt C:\Temp" will then create it in
C:\Temp\test.txt.

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

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