Printable View
Hie guys.
I just developed an application in visual basic 6.0 and would like to package the application using inno setup.
What I want exactly is to create a setup that would give two options.One option should allow for the installation of server components such as the database and some reports designed using CR11.The other option should allow for the installation of client components which should be the vb application interface(forms) to manipulate the server components.
Many thanks in advance
Moved :)
I havent had the experience with Inno but I know other members have. I'm sure they will be replying to you shortly. ;)
well, inno has a wizard that can help you with although i'm not really sure how... sori.
anyways, if i have to make an installer like that, i'd settle in developing my own installer... why? i can do whatever i want to do with it... for free...
Thanks for the quick response.Hope I will be getting something from other members.
How can I develop my own setup instruction set.I would love that so much.Shade more light lerroux.
first of all INNO is free.. and 99% customizable
writing your own installer is a silly idea unless you plan on writing it in a native windows language like C, and even then it is a HUGE painstaking process to actually write your own installer from scratch.
look into the INNO help file for the [Components] and [Types] sections... that is where you define different types of installs to be allowed, and in the files section you set a components attribute, and specify to install that file when the certain component was selected to be installed..
here is a sample, but i wrote it right here in IE, and not in INNO, so the syntax could be off a bit.. like I said read the help file and it will give you a lot of info.. that is how I figured it out when I first started using INNO.
Code:[Files]
Source "C:\myfile.exe"; destDir: {app}; Components: cAlways cOptional
Source "C:\readme.txt"; destDir: {app}; Components: cAlways cOptional
Source "C:\database.mdb"; destDir: {app}; Components: cOptional
[Types]
Name: "mininstall"; Description: "Minimum Installation"; Flags: iscustom
Name: "fullinstall"; Description: "Full Installation"; Flags: iscustom
[Components]
Name: "cAlways"; Description: "Main Program Files"; Types: mininstall; flags: fixed
Name: "cOptional"; Description: "Additional Program Files"; Types: fullinstall; flags: fixed
Thanks so much for the contribution.I just got back to my work and will be trying this out now.Will notify you guys on my progress and will be looking forward to your continued support.
Many thanks
Quote:
Originally Posted by kleinma
Thank you so much for your support guys.Your contributions really helped me.
Kleinma;what I can say is left for me now is to grasp the concepts as I already have the two installation components differentiated.
Many thanks
glad that I can help. I pimp inno whenever I can, because it really is one of the best installers that rivals even the expensive ones. Sure some of them that you pay for make it a little easier with their interfaces, but the fact that INNO introduced built in PASCAL scripting, basically makes you able to do ANYTHING you want from INNO. You can even make windows API calls...
Mayormdau,
If you look into the Inno Setup Third Party Tools you will also get more help in your efforts with Inno setup.
kleinma,
Why not put together a collection of Pascal scripts that users can use in their efforts?
I have posted links in the past in this forum to a site where a guy has posted like 80+ real world usable pascal scripts for use in INNO. I will dig up the link
here are some pascal scripts for almost anything you may want to do with INNO
http://www.vincenzo.net/isxkb/module...ve&sa=show_all
Yeah, I know that one. I was maybe seeking a Kleinma special...
i am actually putting together an INNO VB6 and .NET installer template, but I have been busy at the moment.