CODEWITHSUNDEEP
.net
Nipun
Nipun

Reputation: 1485

Deployment of Application

I want to deploy my application to some other machine. I had build this application with Release version using .NET 3.5. What else is required to deploy this application, which will work on other machine which does not has .NET framework?

Upvotes: 2

Views: 321

Answers (4)

Marc Gravell
Marc Gravell

Reputation: 1064004

As an aside; if you don't want to have to deploy the full framework; with 3.5 SP1 there is the Client Profile - this is quite a bit smaller than the "full" 3.5 SP1, but omits a range of (usually-server-side) things like web and DAL classes.

IMO, it is easier to support the full framework, simply because it removes an extra variable...

Another option would be to develop the app as Silverlight; it may be too late for this, but Silverlight provides a very small client footprint (and easy install).

There are some programs that bootstrap the runtime into your code, but I don't recommend them.

Upvotes: 0

BikeMrown
BikeMrown

Reputation: 1150

In Visual Studio, add a "Setup Project" (under "Setup and Deployment" or "Other Projects Types") to your current solution. About the bare minimum would involve going to "File System" in the setup project and under the "Application Folder" you want to right-click and "Add Project Output." Just select your application's release build. It would be worth your time to read through the MSDN articles to familiarize yourself with the various options and settings. The setup project should detect your applications dependencies automatically (.NET, DLL's, etc)

Just to note, when you build your setup project you will get two installation options (Setup.exe and MySetupProject.msi). If you use setup.exe it will run a dependencies check and notify the user if they need a newer .NET framework or other library. Using the .msi will simply install without the check.

Upvotes: 2

Shoban
Shoban

Reputation: 23016

Here is a nice article for you to learn about deploying windows applications.

Upvotes: 1

Jesse Smith
Jesse Smith

Reputation: 380

The other machine will need the .NET Framework one way or the other. You can bundle it with your installer, you can have your installer detect it and download and install it if necessary, or you can just ask your users to install the framework through Windows Update if they don't have it already.

Once the framework is on the machine, in the simplest case it's simply a matter of copying the contents of the bin\Release folder.

Upvotes: 2

Related Questions