Join Tiberiu Covaci for an in-depth discussion in this video Demo project overview, part of Deploying ASP.NET Applications.
- [Instructor] What we will need is an application to be deployed, and we can use any .net 4, asp.net 4.5 application that we have available. It can be an MVC application, it can be an asp.net webform application; any application that you have, it's possible to deploy. In my case, I chose a demo application that I will use throughout this whole course. And, it's a very simple application. It's a website that represents an eCommerce application, and the solution itself has one web application and it has a common library.
Normally, that's what you would use in your situation. One more that that it has, it has two databases that makes use of. One database, it's used as a database for our product, and the other database, it's used for our identity database or for our app DBcom text in our application. So, those databases are created on the MS Local DB database. The problem with that is this would work only on my machine; it wouldn't be possible for us, for instance, to move it on another environment.
So if I want to deploy the application on another server, I would need to make sure that I have access to a database. So, throughout the course you will see me actually copying and pasting some database connection strings. For this course, I specifically created two databases, empty databases, which I have actually a username and a password for them, and that particular user with that particular password have the owner write on that database, meaning that the database can be emptied and populated every single time we're on the application.
So, if you want to type along and do exactly the same thing as I'm doing, I recommend you create two empty databases on a database server that you have access to and use the connection string that you would have in there. Other than that, there is nothing more to mention. I just want to show you the application, how it runs. So we can just start the application now. It would get compiled, and then an instance of IAS express will be launched, and we can see our application at work.
And, here it is. There are two more things that I would like to mention. Sometimes you might need to run IAS as an administrator, especially when you want to do deployments on your local machine. So again, when that would be the case, I will call it out so you will see that you would have to do it. When you do it on your own, you might actually forget to do that. If you try to do a local deployment and you didn't start Visual Studios Administrator, Visual Studio will challenge you to do that, so there is no, there will be no harm done anyway on this kind of situation.
And another thing, you will see me working on different machines; I chose, for instance, to do some deployments on Windows servers, and those Windows server machines are virtual machines that I'm connecting with Remote Desktop to, so you might notice that the background could be a little bit off.
- Choosing a deployment strategy
- Installing IIS manually and automatically with PowerShell
- Deploying to IIS with Visual Studio
- Deploying to Azure
- Deploying to Docker