Deploying a VB.NET Windows Application

  • Thread starter Thread starter Phil Galey
  • Start date Start date
P

Phil Galey

In VB.NET you have two configurations: Debug and Release. It sure would be
nice if you could point the Debug version locally like it already is and the
Release version to, say, a network location for deployment purposes. I wind
up just using the Debug configuration, and after building the solution and
setup project, copying the setup files to the deployment location the old
fashion way. VB6 allows you to create the setup project in a network
location. I must be missing something. I'm sure the Release configuration
isn't intended to just sit there unused.

QUESTION:

Once you've created a Windows Application and associated Setup Application,
is there an intended way of deploying the application, other than manually
copying the files to the network deployment location?
 
Phil,

A very nice one, create a create a setup and deployment project.

Set the resulting MSI on your installation location on the network

And let the users upgrade there programs on there computers.

I hope this helps?

Cor
 
Back
Top