PDA

Click to See Complete Forum and Search --> : How to make a Visual basic project a standard exe?


kaushiks
Dec 9th, 2005, 07:29 AM
hi,
i have prepared a visual basic project which is completely ready. I need to deliver it to the client in the form of an exe. , since this is my first project i do not have any idea how to prepare a standard exe., so guys i require your help in knowing the steps of preparing an exe.



regards,
kaushik

sishe
Dec 9th, 2005, 07:41 AM
Use menu : "File/Make XXXXX.exe"

But if you want to distribute the application you'll need to prepare an installation script after making the exe file. For this pupose, you can use "Package and Deployment Wizard" which can be found in Visual Studio 6.0 Tools.

cssriraman
Dec 9th, 2005, 07:43 AM
Hi,

You need to create a package using "Package & Deployment Wizard" which is available in Visual studio 6.0 Tools.

mfurqan
Dec 9th, 2005, 07:45 AM
hmmm... simply u can go to File Menu and then you wll find an option says Make abc.exe where 'abc' is your primary form name or MDI form if u r using it.......

Hack
Dec 9th, 2005, 07:56 AM
What edition of VB are you using?

If it is the Learning edition, I don't believe you can make an .Exe

Dave Sell
Dec 9th, 2005, 10:43 AM
You need to buy a 3rd-party software. Here are some:

http://www.winappslist.com/developer/installation_tools.htm

There is one that is the most popular but I can't remember the name - go figure...

Anyway VB6 can make a setup.exe plus a CAB file, but that's 2 files.

Rattled_Cage
Dec 9th, 2005, 11:37 AM
http://support.microsoft.com/?kbid=237803 for free but neat

or

http://www.indigorose.com/site/index.php
set up factory allows you to scan any exe and find all the files dependancys so you can include them too

kinjalgp
Dec 9th, 2005, 12:34 PM
I use Inno Setup. Its really good and easy to use and top of all its FREE
http://www.jrsoftware.org/isinfo.php

randem
Dec 9th, 2005, 01:29 PM
kaushiks,

After you create your exe please read Installation Problems in my signature to help avoid serious problems.

ZachFSW
Dec 10th, 2005, 12:33 AM
Holy Mother of God.

You people that responded to this thread need to read this thread from start to finish.

I am going to guess that you probably didnt help him much - as I know a thing or two, and my head is spinning after reading this - you each gave, albiet more or less each correct in their own unique way, a completely different answer than each other - and thats hard with the amount of responses - damn

Though, I will give that the reason that you all probably gave so many different answers, is cause you got asked a very a generic question with no details.

Info like -

1) What version of VB are you using?
2) Did you use an non-standard components that would need to be accounted for?


Actually, a better question might be.

3) How the hell did you get a client, when you dont know how to make an executable?

Jacob Roman
Dec 10th, 2005, 12:38 AM
What edition of VB are you using?

If it is the Learning edition, I don't believe you can make an .Exe

On the contrary, I have learning edition and can make exes. I just can't control how it's compiled, so it ends up always being P-Code rather than giving me the choice of either P-Code or Native code. :(

dglienna
Dec 10th, 2005, 12:40 AM
If you have a better response, make sure that you post it. I'm sure that he will read them all, and probably ask a few more questions. I think you should read a few more threads in this forum. We come in all shapes, sizes, and flavors, so we have to adjust to everyone's questions as best we can. Often each person interprets a question differently. It narrows down the problem.

Dave Sell
Dec 10th, 2005, 02:37 AM
Holy Mother of God.

You people that responded to this thread need to read this thread from start to finish.

I am going to guess that you probably didnt help him much - as I know a thing or two, and my head is spinning after reading this - you each gave, albiet more or less each correct in their own unique way, a completely different answer than each other - and thats hard with the amount of responses - damn

Though, I will give that the reason that you all probably gave so many different answers, is cause you got asked a very a generic question with no details.

Info like -

1) What version of VB are you using?
2) Did you use an non-standard components that would need to be accounted for?


Actually, a better question might be.

3) How the hell did you get a client, when you dont know how to make an executable?

I read original poster's question thouroughly - his boss asked for the project to be available in a single executable installation format. VB6 does not offer this by default. There is a popular 3rd party toll to do this but I can't remember it's name....

I also mentioned that VB6 offers a setup.exe plus a single .CAB file built into VB6. If this would suffice then he should use it.

dglienna
Dec 10th, 2005, 03:13 AM
Inno Script and Inno Setup can be used to create a setup.exe
Look at www.*********** for information on deployment.

Hack
Dec 10th, 2005, 06:38 AM
On the contrary, I have learning edition and can make exes. I just can't control how it's compiled, so it ends up always being P-Code rather than giving me the choice of either P-Code or Native code. :(Really??!! I didn't know you could do that. I've never used the Learning Edition before, but I know I've seen posts on this forum that have stated you can't make .Exes with it. This is good to know and will be filed away for future reference. :D

esposito
Dec 12th, 2005, 01:17 PM
Really??!! I didn't know you could do that. I've never used the Learning Edition before, but I know I've seen posts on this forum that have stated you can't make .Exes with it. This is good to know and will be filed away for future reference. :D

This means there are different VB6 Learning Editions because, in the one I have, the Make exe option is not active.

User6254
Aug 4th, 2010, 09:03 PM
If you usin' vb6 i don't know ... Try to publish it,go in folder "aplication data" (you publish this folder)and rename your ["program name.exe.deploy"] to ["program name .exe"] just clear ".DEPLOY"