ASP.NET Core 101 -- Making an ASP.NET Core Website [2 of 13]

Making an ASP.NET Core Website

There's a checkbox. It says, "Place solution and project in the same directory," or we can maybe if in the future you and I are going to have different projects,we might have those in separate directories,so I'll just make them separate for now if that's okay with you, and we'll call the main solution 'XXX' but it's up to you.

So any graphics(图样; 图案; ), any CSS,any JavaScript to be put in there(wwwroot),it's going to automatically be served by our Webserver.

And then we've got pages and these are like a dynamic code,and then our main program that starts up there as well as some app settings here.

debugging

There's two ways to do this. We can click the play button,and that'll go and do a debugging session,and you know all about that because you own the debugger.Or I can say, "Start without debugging."

Is there a reason to do one or the other? Sometimes starting without debugging can be a little bit faster.
So if you don't really care about debugging your application at this given point in time,you can go ahead and run it with no problems.

SSL

 

  "Hey,this project is configured to use SSL."What is that? Secure sockets like do we want it to be HTTPS, that's cool.But we're on a local computer,and this is saying well,you need to get a free certificate so you can be secure locally.

So I'm going to go ahead and say,"Yes",and it's going to tell me that it's going to install our certificate,and that certificate is just to make sure it works on my local machine.

IIS express

And down here in the lower corner it says, "IIS express."

 

If you're running this on Windows,you can right-click and say show all applications,and I can actually see something interesting.It's running on two different ports.One is secure and one is not, and that's because we had that secure certificate at the beginning.