What's the easiest way to deploy an ASP.NET MVC 3 project to Windows Server 2003? - visual-studio-2010

Is there some kind of deployment wizard I can run and have it install just the things it needs to run right onto the server end point? Do I have to build the project using VS2010 on the server? If I can't get this thing deployed today I am really going to be screwed.
IIS 6 is there and I think .NET 4 is installed (I tried installing it from Microsoft and they had me install a million things like VS2010 express and SQL Server and all this other crap, the install failed but .NET 4 does show up in IIS).

I achieved this by enabling an FTP site for the IIS server website and using this to deploy the web application within visual studio 2010 which will build and deploy just the changed files for each build. Works very well. You can even add a Publish toolbar to help deploy regularly more easily.

All you have to do is install the .NET Framework 4.0 (32 / 64 depending on build) and run aspnet_regiis.exe in the Framework folder.
For me this is located here:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe
Hope this helps!
You can also use the publish command from VS 2010 to save it to the filesystem and then copy the files into an IIS site on the target server. Just map a network drive to X: or something (for your sites root) and publish directly to the share.

You can take a look at Web Deployment projects or even the VS "Publish" feature

From the Build menu in VS2010, just click Publish [name of your web project] and enter the location on your web server where the site is going to be hosted.
VS2010 will publish the files required there.

It shouldn't be necessary to install VS2010 Express, just to deploy a site. But if .Net 4 and ASP.NET MVC 3 is installed, you should be able to deploy. Right click the web app in VS2010, and hit Publish.
Remember to set the configuration to Release!
But, with IIS 6 you could be in for a fight in regard to HTTP Modules, Handlers and other server configuration. Anything inside your Web.config's system.webServer section will always be ignored by IIS 6.

Related

How to publish Asp.Net core MVC web application on Godaddy's shared web hosting

I have developed an asp.net core 2.1 web application with entity framework core. Now I would like to host the application on my Godaddy's shared web hosting account. I am trying this with FTP but it is not working. Does anyone has solution for this?
Is there any error message that you see? The following is steps to publish your application:
Please open your project with Visual Studio tool
On the Solution Explorer windows (which is normally located on the top right hand corner of the VS tool), right click your project and select Publish
Please kindly publish it to a local folder, such as C:\Project
Please just upload whatever files/folders you see on C:\Project to the server via FTP and your site will work fine.
Important NOTE:
If you are using Visual Studio 2015 or later version, the publishing step may look a bit different.
Please open your website project with Visual Studio 2015. They may have been a pre-set .NET version on your project.
Then, please go to the Solution Explorer, Right Click the project and select "Publish Web App" website. Please select "FTP" as the deployment method
Please hit Publish
You can also read this documentation http://windows2008hosting.asphostportal.com/post/Cheap-ASPNET-MVC-3-Hosting-ASPHostPortal-How-to-Deploy-an-ASPNET-MVC-3-App-to-Web-Hosting-with-5cbin-Deployment.aspx. I use this tutorial to deploy my previous MVC. :)
From what I found on GoDaddy forums, do correct me if I'm wrong, GoDaddy doesn't support .NET Core on shared hosting yet. I believe Plesk Onyx will support this (mine is still on Odin) and after a conversation with GoDaddy customer service, they don't have a date for the upgrade yet.

Deployed application using InstallShield does not work

If you see below image, there are two applications deployed to IIS.
QManualDeployment - This is deployed using Visual studio Publish feature.
InstallShieldPOCWebApplication - This is deployed using InstallShield installation tool.
Option 1 is working without any issues, but as you see InstallShieldPOCWebApplication it looks like foder rather than web site. Also it does not work.
How can I deploy application as website using INSTALLSHIELD
Here is my IIS Settings from InstallShield Tool
Default Web Site is a website. QManualDeployment is a virtual directory / application off of Default Web Site.
In InstallShield, it isn't enough to just author all of your directories/files into components. You also have to define the IIS configuration.
I'm not sure if you are using InstallShield Express, Professional/Premier of Limited Edition so I can't give you more direction then that.
I faced same issue with Post owner, after run Install Shield setup file, it show a folder in IIS and I resolved by right click to folder name and convert to Application.
I share for whom concerned.
After that we can select suitable application pool as

Visual Studio 2010 published web site returns "Could not load assembly App_Web_xxxxxx.dll"

I am working on client's application in which we have two servers - development server and testing server. We first develop applications on development server and then publish it and host it on test server for client testing.
Testing server has Microsoft .NET framework 3.5 SP1. On development we have Visual Studio 2010.
We publish the website on development server using VS 2010 and then copy that folder to testing server and host it on its IIS.
Whenever we try access any aspx page of site hosted on testing server, we get error:
Could not load assembly App_Web_xxxxxx.dll". Make sure it is compiled before accessing the page
What can I do to resolve this?
This could be due to a lot of reasons.
I would start by trying one of the following things..
Make sure your IIS Site has the correct .net version specified - same as your application
Make sure you have all the required .net components installed in windows features (control panetl)
Look at event viewer for more errors and post it here
OK guys here is the solution.
Since my testing server is having Microsoft .NET framework 3.5 so on the development server while publishing from VS 2010, I have to choose target framework as 3.5.
Do this:
Right click web site -> Property Page -> Build -> Change the target framework.
After doing this setting, publish the web site again.

I want to keep my source protected on my development machine, how would I deploy ASP.NET MVC to the server?

I'm not exactly sure what to do, normally I do a commit to SVN and Cruise Control does all this stuff on the server to pull from the repo and deploy everything.
However I am just playing around for fun with my personal VPS and want to know how I can from Visual Studio 2010 (web express) on my local machine just make some kind of installer or DLL or whatever and how to deploy it to my VPS of Windows Server 2008.
Do I upload via FTP and run something or place some files in a certain location and configure through IIS? Or is there some way Visual Studio can just interface with my server and impregnate it with my beautiful code?
From the description given, I'd recommend 2 options:
check whether your server installation currently supports one-click publishing. It's likely an IIS configuration task(s) and/or ensuring your server supports MSDeploy/WebDeploy. See "One-Click Publishing - What's New". Publish Use Visual Studio 2010's Publish command to perform a Web Deploy of your solution.
setup an FTP server on your server. Use Visual Studio 2010's Publish command with the FTP option to push your built solution.
Would this MSDN article help?
The thing is there's capabilities in Visual studio that can publish a web application on a web server.
But you can always do an xcopy deployment as well. And since you've obviously never deployed a web application yet maybe it would be good to learn something and actually deploy it manually.

Deploying ASP.NET 2.0 to IIs7

How to deploy my ASP.NET website to IIS7? I'm using Visual Studio 2005. And I don't know where to start.
I tend to take more of a manual approach, but there is a web publish feature built into Visual Studio that should get you going.
Here is some reading you can do on it:
http://www.codeproject.com/KB/aspnet/VSDeploy.aspx
Here's some preliminary steps, a little more manual than some other options, but they are the ones I'm comfortable with:
Obtain access to the server where IIS7 is installed. If you don't have IIS7 installed on a server, install it. If you are not able to get access to this server, you will need to have the administrator of that server set up IIS7.
Create the website in IIS that you want to deploy to, or have the server administrator create an empty website for you to run your website on.
Use the 'publish' feature in Visual Studio to build a deployable version of your site. This is what you will install on IIS7.
Copy paste the website over to the server where IIS7 is installed. You will need to place it in a directory which you can set as the Home Directory for the site.
If you have access to the server, and rights to administer IIS7, set the Home Directory of the site to point at the directory where you copied over your files.
Enable the website, and you should be good to go!
NOTES:
These instructions assume the following:
a) You have some basic knowledge of how to configure IIS7 (or at least access to somebody who does)
b) You have some basic knowledge of how to install IIS7 if it is not installed (or access to somebody who does)
c) You have some basic knowledge on web site publishing from Visual Studio
If you need more instructions on these 3 notes, you may wish to consult the references for IIS7 and Visual Studio.

Resources