PDA

View Full Version : EXE files



NewsArchive
03-12-2007, 08:27 AM
I created an install script
compiled and it created an exe

the folder where the .sb6 and exe are located in c:\bmabc\newbmsetup

my sb6 file is called bmsetup.sb6

i then opened my sb6 file and did a SAVE AS
and saved bmsetup.sb6 as BM.sb6 and also bmupd.sb6

so I have 3 installation scripts

all 3 sb6 files are visable in the folder c:\bmwin\newbmsetup
I edited each script to change the name to exe that gets created

bmsetup.exe
bm.exe
bmupd.exe

Here is my problem

When I do a compile of the each script, the other exe files are gone from my
folder

so if I compile bmsetup.exe I see it, but dont see the other exe files
If I them compile bm.exe I will not see bmsetup.exe but will see bm.exe in
my folder

i am using vista home premium if that makes any difference

--
Eric Jacobowitz
www.castlecomputer.com
www.cctsoftware.com

NewsArchive
03-12-2007, 08:28 AM
> When I do a compile of the each script, the other exe files are gone from my
> folder

That is **normal** behaviour Eric.

SB6 models after industry standards here (such as Visual Studio) and it
"cleans" out the output folder.

Just set the output path to a different location for each of your separate
projects.

After a build you will have the new distributable file there as well as the
HTML report of the compile.


A technique I use is that I have a DISTRIBUTE folder on my root of the
drive.

I create a folder under that for each product by name.

Then below that I build a directory structure to match the one that I
expect to create on the target computer.

The completed files get placed in those folders.

I then build my SB6 project FROM those folders (so it is easy to tell that
I have the files needed in each folder)

I also have a DOCS and a ONLINE HELP folder there where I publish my H&M
files to as well (for the website).

Last but not least is a PUBLISH folder under the product name.

Then SB6 is set to generate the output there.


This simple yet effective organization keeps everything easy to find.

Then when I do a release - I ZIP the folder structure by product name and
rename the zip file with the release version appended.

This gives me a "snapshot" of that entire release - the source files, web
help and the distributable's.

;-)

Charles





--
-------------------------------------------------------------------------------------------------------
Charles Edmonds

www.clarionproseries.com - "Serious imaging tools for Clarion Developers"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

NewsArchive
03-12-2007, 08:28 AM
Eric,

What Charles said.

Another option is to remove the *.exe item from your "Extensions to Delete
on Clean" list (General Properties -> Project Properties).

Friedrich

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

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

-- Official Comodo Code Signing and SSL Certificate Partner