Building Exe and Deployment

Question

1.00/5 (1 vote)

See more:

I'm using VB 2008

I created an Executable of the program i created by following the instructions..
Right-click on the Project, Selected Properties and After filling the necessary entries, I selected Publish Tab and clicked on Publish Wizard.

After creating an Exe. How will I deploy my new program?

do i need to copy the whole Project's folder to another PC or only the .Exe file?

Posted 17-Jan-12 21:38pm

Alan Tuscano

Add a Solution

Comments

Sergey Alexandrovich Kryukov 18-Jan-12 4:13am

If you don't know, it means you need to learn the very basics of programming and even of basic computing on the level of the regular user -- you did not get the whole idea of it yet.
--SA

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2012-01-17T22:12:00

Normally, you need to deploy only what you got in your output directory. Usually, this is not just one executable file (it could be several executable files, EXE and DLL, configuration file, sometimes some other read-only data, etc.). This is the most simple and most welcome way of deployment — for those who understand. :-)

Your project "folder" has source code, which is not what the customers use. You can provide source code of course, but this is alternative to deployment of compiled code. If you provide source code, it usually should be uncompiled — the users what to compile it by themselves.

—SA

RDBurmon · Accepted Answer · 2012-01-17T21:44:00

Solution 1

exe and its dependant file (not code file but report file , dlls eTC..)

Posted 17-Jan-12 21:44pm

RDBurmon

Comments

Alan Tuscano 18-Jan-12 3:48am

After doing that,
then will i just copy the folder to another Computer?

Sergey Alexandrovich Kryukov 18-Jan-12 4:18am

Yes, if your project is done correctly. You should not create dependencies on hard-coded path names and other stupidities. You should check up that your code work in any directory where you put your output.

Make sure you install all prerequisites on the other computer.
--SA

RDBurmon 18-Jan-12 4:05am

No , I suspect you should add this all in package . Please googled how to create package for VB.net application, Run that on another computer

Sergey Alexandrovich Kryukov 18-Jan-12 4:19am

No, OP should not make a package, if the project is done well. It's the best of the project can be kept as simple and reliable as that (copy the output directory in any location and it should work), but there are many cases when many other installation steps are needed. It is not related to packaging in fact. One example: add file type for a new data file type in the system registry.

If a developer can avoid any extra steps, this is the best, but not always possible or acceptable.
--SA

Alan Tuscano 18-Jan-12 4:37am

This explains.

Tnx SaKryukov

Sergey Alexandrovich Kryukov 18-Jan-12 4:20am

You were not quite accurate. Developer should deploy the output directory, but it's not just the main file and its dependencies. Some files are not dependencies. You should see the difference between build-time and run-time dependencies.
--SA

RDBurmon 18-Jan-12 4:25am

Hey SAKryukov, Please do not misguide OP . Every project after completion it should go through deployment phase by creating package or set up programme to avoid all hassel to gather dependancies manually.

Sergey Alexandrovich Kryukov 18-Jan-12 14:04pm

It depends what do you call a package. MSI? No, not all projects.
Finally, Microsoft started to support the "xcopy deployment". There are recommendations here and there how to make the product working in any location right away. Project integrity and versioning in .NET is different; it stimulated return to a healthy way. The trend really works to support my opinion, but this is not something which affect my opinion itself. Direct copy deployment is much better in many cases.
--SA

RDBurmon 19-Jan-12 3:03am

SO what about the dependancies then ? In "Direct Deployment" the project owner has to identify all the dependancies . Is it so painful process of project deployment ?And one thing here you can't version your project .