ASP.NET Web Deployment using Visual Studio: Deploying to Test

First Last 1

I want to test publishing my ASP.Net web app from my development environment (it uses the default IIS Express that comes with VS 2017) to a QA environment that has IIS (like a Hoster will have). My goal is 2-fold - to test deploying my web app to IIS as well as QA test the web app in IIS. The web app will eventually be deployed to a 3rd party vendor(Hoster). I do not want to use AZURE.

I’m trying to do this tutorial.
https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/visual-studio-web-deployment/deploying-to-iis

It states: "an app could run and test correctly in Visual Studio but fail when it's deployed to IIS".

So, I want to test deploying the web app to IIS as well as QA test the web app in IIS.

However, the example that is out there is obsolete now. It no longer allows for the download of the Contoso University starter project. So I cannot do the tutorial to deploy to IIS.

I can't find something similar.

Any suggestions?

Joy Phillips 6 Reputation points

2022-03-09T09:29:59.69+00:00

We are also facing the same issue for our business app. As we have complete website of golf grips. But the app is facing the same issue due to which still our users is suffering while using mobile phone. Although our web user is fully satisfied.
Dean Everhart 1,536 Reputation points

2022-11-29T19:58:33.41+00:00

.....
Nathan Isaiah 0 Reputation points

2023-06-04T15:45:58.39+00:00

I also want to make an app for your site Apky Mody. but I'm not getting the right direction from where to learn visual studio as a pro. I searched a lot but didn't get it. Need Suggestion
harshbargersonphilips 0 Reputation points

2024-12-07T17:14:10.7066667+00:00
To test deploying your ASP.NET web app to IIS and QA it, follow these steps:

Set Up IIS: Install IIS on the QA machine, ensuring components like ASP.NET and Web Management Tools are configured.

Publish from Visual Studio: Use the File System publish method to create deployment files and copy them to C:\inetpub\wwwroot\YourApp on the QA machine.

Configure IIS: Create a site in IIS, point it to your app folder, and configure an appropriate application pool and permissions.

Test the Deployment: Access the app in a browser and perform QA testing to identify issues.

Like a bottleneck calculator identifies mismatches in PC performance, testing in IIS helps detect deployment bottlenecks, such as misconfigurations or missing dependencies. This ensures smoother deployment to 3rd-party hosting environments.
harshbargersonphilips 0 Reputation points

2024-12-07T17:15:26.06+00:00

i hope it will help

3 answers

Yijing Sun-MSFT 7,091 Reputation points

2021-10-05T01:45:55.257+00:00

Hi @First Last ,
The Contoso University starter project is a project for testing. So I suggest you could create a new simple project by yourself.The content of the project could only includes of "Hello World".It's ok.

Best regards,
Yijing Sun

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our  documentation  to enable e-mail notifications if you want to receive the related email notification for this thread.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Sam of Simple Samples 5,546 Reputation points

2021-10-05T04:43:49.663+00:00

Do you want to deploy to test or do you want to test publishing? Those are different.

If you want to create a web app then test it then you do not need to deploy it. You can use the server provided by Visual Studio to test it. Or in IIS you can make the app a website and test using IIS. Then that web app can be deployed wherever it needs to be deployed to.

Do you want to try deploying a website just to understand how it works or something like that? As you indicate, you can use Azure for that. If you do not want to pay for Azure then there are a few other possibilities, but I am not aware of any host that offers free hosting. You can get a free trial for Azure.

I created Simple Samples Network when GearHost was allowing free websites but they have discontinued the free option. They will someday remove that website.

Do you want to try using web deploy locally just to learn about it without paying for a host? I assume that is possible and if that is what you are trying to do then you need to clarify it.

Web Deploy is older technology. Many organizations and developers are using Git and they use hosts that can deploy from GitHub without using Web Deploy.
Please sign in to rate this answer.
First Last 1 Reputation point

2021-10-05T13:04:03.83+00:00

My goal is to eventually deploy (publish) an ASP.NET web application to a third-party hosting provider using Visual Studio 2017. This web site will be a publicly accessed blog that also collects user information and requires signing in. It uses SQl Server to store the user's information for subsequent retrieval.

Currently I run and test it in Visual Studio 2017 using IIS Express as the development web server.

From what I read, an app could run and test correctly in Visual Studio but fail when it's deployed to IIS.

So, I want to test deploying the web app to IIS as well as QA test it there.

I believe I should deploy the application to IIS on the development computer which then will be the same process that I will use later to deploy it to a production environment (third party hosting).

The tutorial - ASP.NET Web Deployment using Visual Studio: Deploying to Test - was to instruct and show me how it is done.

I was trying to follow the steps but it no longer allows me to download the Contoso University project.

I'm new to GIT - is there a tutorial for Developers that explains the host and the deploy from GitHub without using Web Deploy?

How is IIS used or is it?

AgaveJoe 28,961 Reputation points

2021-10-05T14:27:01.373+00:00

Just deploy the project to a folder on your machine like C:\inetpub\wwwroot\NameOfYourAppFolder. Assuming you have IIS installed on your dev machine, open IIS Manager. Find the application folder in the "Default Web Site" node, right click the folder, and select "Convert to Application".

You should be able to run the project on local IIS. Then it is just a matter of coping the application folder to your host.

Sam of Simple Samples 5,546 Reputation points

2021-10-05T15:11:42.227+00:00

There are very many tutorials about Git and GitHub. I think that Git is difficult to learn and I am still a beginner but it is what most developers are using now. Git and GitHub are used by both Windows and Linux developers. Git (the software) was developed by the same guy that initially developed Linux. One possible tutorial is Add ASP.NET Core projects to GitHub using Visual Studio 2019 | BinaryIntellect Knowledge Base

The procedure for deploying to a host from GitHub depends on the host. So it is best to know what host the site will eventually be deployed to. Also, you have not said whether you are using ASP.Net Framework or ASP.Net Core. You certainly can deploy from GitHub to a host that is not the same as the host(s) that the application will eventually be deployed to and that will at least allow you to become familiar with the procedure. Supporting multiple versions is exactly what Git is designed to do.

You have not said why you do not want to use Azure. I will tell you why I do not. Mainly it is because more than once I have been unable to determine what I am being charged for. I certainly understand that problem.

Sam of Simple Samples 5,546 Reputation points

2021-10-05T16:08:56.577+00:00

As best as I can see, most developers do not use C:\inetpub\wwwroot for development purposes.

Albert Kallal 5,331 Reputation points

2021-10-05T18:04:39.097+00:00

Well, you can create a sample web project, crete a page, and a button that shoves Hello World into a text box. I thus see no reason for a smaple web site.

However, there ARE some large considerations here. I mean, first up, I would as noted create a new web application project. Try a few things. Visual Studio lets you develop + test your site automatic (it provides a copy of the web server IIS express for you).

About the ONLY considering you need here? Do you create a asp.net web application site, or do you create a asp.net web site?

The two above SOUND the same, but they are VERY different. A asp.net web site application tends to mean that you have your OWN FULL server.

But, often low cost budget hosting will not support that option. So, you would create a asp.net web site. They tend to function the same, but publishing is easier the web site vs the web site application.

I would thus create a simple test project - run it play with it. If you have hosting now then you could test publish to that web site (say by using FTP).

So did you try create a test site in VS and play with it? And git has zero to do with this process - so don't worry about that for now.

First Last 1 Reputation point

2021-10-06T00:57:31.047+00:00

AgaveJoe - I have not installed IIS yet. I see that the instructions to do so were in that tutorial I was attempting to do. I just have never done it before and am cautious about it as I did not want to mess anything up on my PC but I stopped as I could not download the Contoso University starter project.

https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/visual-studio-web-deployment/deploying-to-iis

So at a glance - if you are familiar with doing an ISS install, if it is not a bother, can you tell if the instructions in the tutorial to do the IIS install are valid still? If so, I guess I can then proceed with them and then do the remainder as you suggest.

First Last 1 Reputation point

2021-10-06T00:59:24.41+00:00

SimpleSamples - on my PC I am using Visual Studio 2017. I have created an ASP.NET MVC application project - selected the ASP.NET Web Application (.NET framework). It is full coded BLOG web application and I run it and test it in Visual Studio. Now I want to publish it to IIS and test it.

No real reason for not using Azure. I just thought I would go with GoDaddy.com or some other. This is new to me and trying to determine the best approach.

The

https://learn.microsoft.com/en-us/aspnet/web-forms/overview/deployment/visual-studio-web-deployment/deploying-to-iis

was to instruct me how to do Web Deployment using Visual Studio so I can test it on IIS. Part of that instruction is to install IIS. I wanted to do the full the tutorial as I just felt more comfortable first doing this tutorial 'Deploying to Test' process before attempting to do this with my application. I did not want to mess up anything installing IIS as I have never done that. But got hung up on the fact that I can no longer download the Contoso University starter project.

So, I suppose I can just do the part of the instruction that is to install IIS.

First Last 1 Reputation point

2021-10-06T00:59:51.203+00:00

AlbertKallal-4360

So when you state "But, often low cost budget hosting will not support that option. So, you would create a asp.net web site." Do you mean create an asp.net web application?

That is what I have done. On my PC I am using Visual Studio 2017. I have created an ASP.NET MVC application project - selected the ASP.NET Web Application (.NET framework). It is full coded BLOG web application and I run it and test it in Visual Studio. Now I want to publish it to IIS and test it.

First Last 1 Reputation point

2021-10-06T01:01:38.093+00:00

What would they use?

Albert Kallal 5,331 Reputation points

2021-10-06T01:13:08.607+00:00

yes, the main distinguish here is the word "application". I believe that these days most web hosting plans support "applications". Both choices are available for MVC. I mean, if you looking to post up say some test pages, or a sub-site to a EXISTING hosted site, then web site is better.

So the two choices are: asp.net web site
and
Asp.net web site application.

web site "application" quite much assumes that the whole site and whole application is going to be the web site.

And another notable difference is that a web site allows you to copy "one" page, and update code for one page and not have to re-deploy the whole site.

With a web site application, while the web pages are published, the code is not, and all dependences and code is pre-compiled.

The difference is explained here:
dd547590(v=vs.110)

I probably should not even noted or mentioned this difference, but you are MUCH better to use a web site application, and everything suggests that's what you done now anyway.

So, my comments about using a web site vs web site application probably don't apply. It can be more difficult to publish a web site application as a "sub folder" or site to a existing site, but that does not look to be a issue for you. Most plans that support asp.net should work and be just fine for your use.

Albert Kallal 5,331 Reputation points

2021-10-06T05:06:28.747+00:00

Just as a follow up, you don't have to install or setup IIS on your computer. Installing Visual Studio does this for you.

And I see you ALREADY have that setup working. So, if you want to test deploy to IIS?

Then you need to install IIS. I don't believe that IIS is free. The local IIS "express" you are now using of course works, but it not really appropriate for a test deploy to a real working server with IIS on it. So, unless you have the full edition of IIS, then you can't really do this with much easy. (maybe you do have a server available to you running IIS).

As for web publishing? Not really sure why git-hub was brought up? But you can use folder publishing (and then copy that folder to the web server). Or you can use simple FTP publishing. I in fact use folder publish. I publish the site to a local folder (c:\TestWeb). Then I take that folder and copy it over to the computer with IIS on it. So config and setup of real server running IIS is a "big job".

And I don't think it would be at all appropriate to install IIS and a server based of windows on your development computer. In fact, for such testing I have a server 2016 VM running on my dev computer for this purpose. So, if you use VM's for development (don't we all???), then this could be another road.

AgaveJoe 28,961 Reputation points

2021-10-07T15:31:44.043+00:00

As best as I can see, most developers do not use C:\inetpub\wwwroot for development purposes.

This is a deployment question. The main point is deploying to the file system on the local machine. This works every time and the results the file only needed to host the application.

The files are deployed to C:\inetpub\wwwroot and IIS is installed, which come Windows, then you can quickly create an application using only the deployed files.

AgaveJoe 28,961 Reputation points

2021-10-07T15:39:37.497+00:00

IIS is a Windows feature which can be added from the "Turn Windows features on or off".

Bruce (SqlWork.com) 68,486 Reputation points

2021-10-07T20:08:39.207+00:00

the main issue with your question, is it can not be answered without knowing the hosting provider and framework version. depending on the hosting provider, VS may or may not be able to deploy to the provider.

deploy from GitHub again depends on the hosting provider. But GitHub has more deployment options than visual studio.

while a local deploy to IIS will be a good training, it probably will not match the deploy to the hosting provider. also the security on you local deploy will be different.

A common approach is to use VS to deploy to a file folder, than upload this folder to the hosting provider per their instructions.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Sam of Simple Samples 5,546 Reputation points

2021-10-06T04:49:00.183+00:00

This is another discussion that starts simple then frustratingly goes in many directions. I give up.
Please sign in to rate this answer.
First Last 1 Reputation point

2021-10-06T13:13:43.74+00:00

The tutorial (link posted above) states; "an app could run and test correctly in Visual Studio but fail when it's deployed to IIS".

So, I just want to deploy my ASP.NET web application to IIS on my development computer and then to QA test it on IIS (currently I am using the default IIS Express that comes with VS 2017) so that I can use the same process later to deploy it to a production environment - a 3rd party vendor.

I was trying to follow that tutorial but got stopped by not being able to download the Contoso University starter project.

So looking at that tutorial, the section 'INSTALL IIS', is that still a valid approach (it was written 1/2019) that I can follow to do the install of IIS on my development computer? I've never done that before and I don't want to mess up my dev environment that I have been using for coding and testing.

I would then want to follow the section 'Publish to IIS' (deploys to IIS using Visual Studio and Web Deploy).

Albert Kallal 5,331 Reputation points

2021-10-06T15:05:23.367+00:00

Well, the install IIS part is still valid, but it in general assumes that you have a server based edition of windows, and that server is setup and running. It also not clear what copy and where you obtained IIS. but I fail to see why doing a simple test publish requires some particular web sample - why not publish the test site or what you playing with now then?

So, as general rule, IIS is to be installed on a server based edition of windows. I don't know what tutorial you speak of (edit - ok, just looked), but generally the setup menus on the server edition of windows are quite helpful, but then again, that assumes you have a server edition of windows.

So as noted, IIS express is what you have now on your dev box with Visual Studio. And I 100% agree is a a great idea to setup the full edition of IIS (but, it quite a big system, and there is a lot of learn).

I suppose you could install IIS on your dev box. They seem to suggest that JUST selecting the web deploy will also give you the option (or force you) to install IIS - that was never my knowledge. Web deploy is to be installed on the web server - that allows seamless debugging and deployment from your dev box and VS.

If that step actually offers to install IIS, then so be it. Did IIS install for you? (I'm not all that comfortable turning my dev computer into running a full pop web server - I would use a VM for that, and a server based version of windows - since that's what a production server will be running).

First Last 1 Reputation point

2021-10-07T14:12:43.193+00:00

I was following the tutorial and figured I would use the example that they are using so I could follow along per the tutorial. And as I have never done it before, I am being cautious to not mess up my dev code (maybe that would not happen but as I said new to this).

My windows:
Edition Windows 10 Pro
Version 21H1
Installed on ‎8/‎8/‎2020
OS build 19043.1237
Experience Windows Feature Experience Pack 120.2212.3530.0

I have not tried the install of IIS per the tutorial yet as I wanted to know if it was safe to do so and not mess up my dev environment that uses IIS express.

So It sounds like - to be safe and simulate a production server - I need to buy a PC with a a server based version of windows that will act as my test machine.

AgaveJoe 28,961 Reputation points

2021-10-07T15:52:47.397+00:00

I have not tried the install of IIS per the tutorial yet as I wanted to know if it was safe to do so and not mess up my dev environment that uses IIS express.

IIS is a service that comes with Windows.

It is highly likely you'll deploy this application to IIS running on a remote host. Unless you have a dev and/or test environment at your convenience, local IIS works well for testing deployments.

So It sounds like - to be safe and simulate a production server - I need to buy a PC with a a server based version of windows that will act as my test machine.

You're making up problems that do not exist. I use Kestrel, IIS Express, and IIS everyday on my development machine. Each host has a purpose depending on the type of application.

Albert Kallal 5,331 Reputation points

2021-10-07T16:39:54.56+00:00

Well, these days? What a personal assistant is to word processing?

VM technology is that to developers. I mean, I have to test my software "installers" all the time. My dev computer is out of the question (since it has 3+ years of library installs - EVERY thing will always work on my dev box -- right!!! - it has everything including the kitchen sink!!!).

So, I have on my laptop at least 15 computers (VM's). So, I can spool up and launch a test copy of windows 10 in less then one minute. This is a fresh win 10 VM. I can test my installer software. and then ROLL BACK that VM to a fresh win 10 copy. That way the install of my software is a fair and legitimate test (even one test install on a box means that additional test installs are not valid - who knows what my last install left behind (so further tests are not valid). So, today, most developers use VM technology. So I have a test SharePoint server, a test server 2016 (with web server setup). I have a test version of DOS 5.0 to run a old legacy program in FoxPro I have. I have a test vm of win7 (that I was using to test for some clients that had older PC's running win 7). So all of these VM's are on my laptop. So, these days, you don't buy a whole computer for just testing - you use VM technology. One of my favorite features of windows 10? It includes Hyper-v for free!! (any version beyond home edition).

So, I have as many spare computers as I have disk space so to speak. You can even spool up 2 desktop computers and a server - network them - all virtual, and thus no need for phycsical boxes.

Albert Kallal 5,331 Reputation points

2021-10-07T16:54:43.14+00:00

Having said all the above? You can intstall IIS on your dev box - its not the end of the world. However having a septerate machine (even a VM) is much better. That what you can test/play over and over. And with that VM then you can say have others in the company try out the web site - say these changes need to be made. It can be VERY hard to push out changes to a LIVE server if customers are using that server. So, it really depends at what stage you are here. It would be less work to simply get some hosting and use that for testing. But, once it goes live, then using that live system for testing can be a really pain (challenge).

So, some developers do install IIS on their dev box - it not all that bad of a idea, but I have a HUGE hesitance to install any old software on my dev box, and I already have too much software on my dev box for personal tastes (so I make great efforts to avoid installing more test software and systems on my dev box unless absolute necessary).

I had surmised that you need a "true" server edition of window for really good testing. But that's not really 100% true. So installing IIS is not all that bad. But I just think your final server will STILL be a different environment anyway, and thus if you just testing deploying software, then fine. But for a good true test and testing system, then yes a separate box (or better yet a vm) is a "better" choice. So, not the end of the world if you want to and do install IIS on your dev box. Such tests would test installing, but not be valid if it will actually run correctly on final server.

Albert Kallal 5,331 Reputation points

2021-10-07T16:59:43.047+00:00

Also, sorry - meant to respond to one thread up - to original poster, but no big deal. I suspect that the user is new to these things - so all I can do is post a narrative that helps the poster move forward.

First Last 1 Reputation point

2021-10-07T20:03:43.697+00:00

So if I choose to use my development box (that has my web app and is using IIS Express) - then how do I create the VM on the development box to act as a QA test area?

The idea being to install IIS on the VM and deploy my web app to the VM it so as to QA test the web app on the VM using the IIS there (if I am not mistaken, then that will simulate a production environment that will be on the hosting company I eventually choose).
Then:
1.) Deploy (publish) the ASP.NET web application to the VM.
2.) QA test it on the VM. (repeat step 2 and 3 as many times as necessary)
3.) At some point, deploy from the VM to the hosting company I eventually choose.

If I choose to get a NEW box to act as a QA test area, then it would need to have a server based edition of windows. Correct?
Then:
1.) Install IIS here.
2.) Copy in my development web app (hence VS 2017 and MS SQL Server is needed here as well).
3.) Deploy (publish) my development web app here.
4.) QA test it. (Repeat step 2 and 3 as many times as necessary)
5.) At some point, deploy from here to the hosting company I eventually choose.

AgaveJoe 28,961 Reputation points

2021-10-07T21:17:27.087+00:00

So if I choose to use my development box (that has my web app and is using IIS Express) - then how do I create the VM on the development box to act as a QA test area?

You are making up problems that do not exist and over complicating a very simple deployment test. The time you've spent posting responses is far longer than it takes to install IIS and deploy a web app to c:\inetpub\wwwroot.

Clearly you do not have a test environment or VM setup currently. So why not just fire up IIS and deploy your application? You get to learn how to setup an application in IIS without having to worry about networking, firewalls, domains, etc. It's not like you can't build a test server or VM later...

First Last 1 Reputation point

2021-10-07T21:55:14.36+00:00

AgaveJoe - OK - no VM machine.

I did not see your screenshot above for setting IIS on. I missed it.

Anyway. Here is what mine looks like now.

Here are my proposed changes per your screen shot recomendation.

I selected the 3 under web Management Tools
I selected ASP.NET 4.8 under Application Development Features and it then selected the others.

This look about right?

Bruce (SqlWork.com) 68,486 Reputation points

2021-10-08T01:37:13.617+00:00

I wouldn’t. You will only learn how to deploy to an IIS site you host. The procedure will be different depending on the hosting provider you pick.

To play with deployments I’d use contains. You can pull an iis container and deploy to it with a simple folder publish.

Or just install iis on your dev box. This will require you learning iis admin that does not transfer to hosted solutions. They typically will use cPanel or some home brew system unless you pop for a vm.

First Last 1 Reputation point

2022-03-06T18:06:53.517+00:00

Well, it will help me to accomplish part 2 of my goal.

My goal is 2-fold - to test deploying my web app to IIS as well as QA test the web app in IIS.

I just want to simply deploy my web app to IIS and test my web app on IIS.

Otherwise, I will need to understand containers as you suggest.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

ASP.NET Web Deployment using Visual Studio: Deploying to Test

3 answers

Your answer