How do I distribute my web application to my company's employees?

[MMock]

I tried googling this but the various search strings I tried did not land on what I am looking for. So now that I have a web application well under way development-wise, instead of continuing in a bubble (because there is a lot more to do still) I'd like to 1) distribute the application to my co-workers to know they can get to it 2) figure out how they're going to run the pages that access to our sql server database (I am using Dapper currently for just me but we will eventually need a way without a VPN connection). Thanks for any help directing me to the right documentation on these tasks.

[techgnome]

If it's a web app, it would be deployed to a web server.... no?


-tg

[MMock]

@tg, yes, perhaps! I am new to this, LOL. Expect basic questions from me.

[MMock]

I am going this route: https://learn.microsoft.com/en-us/as...aspnetcore-7.0

[OptionBase1]

I tried googling this but the various search strings I tried did not land on what I am looking for. So now that I have a web application well under way development-wise, instead of continuing in a bubble (because there is a lot more to do still) I'd like to 1) distribute the application to my co-workers to know they can get to it 2) figure out how they're going to run the pages that access to our sql server database (I am using Dapper currently for just me but we will eventually need a way without a VPN connection). Thanks for any help directing me to the right documentation on these tasks.

@tg, yes, perhaps! I am new to this, LOL. Expect basic questions from me.

No offense, but before writing a single line of code you should have had a full understanding of underlying architecture, deployment, configuration, connectivity requirements, etc.

Writing code first without understanding how clients connect could very well lead to code that is unusable, because it was developed with certain assumptions like where the data would reside, how connections are made, etc. that could all turn out to not be correct.

[MMock]

Yes, of course. No offense taken, and no worries. Management is well aware of every design decision I've made so far so we're sure it will be runnable by our employees.

[MMock]

@tg - So you "deploy it to a web server". What does that mean? I published my files. What's next? Do I have to do all this? https://learn.microsoft.com/en-us/as...=visual-studio My coworker took over to actually deploy it, and says I have no web page to land on, there's no default.html. I'm trying to get answers to what he's doing exactly.

[MMock]

What does this mean exactly? (From same article cited above). The app is accessible in a browser after it receives the first request. Make a request to the app at the endpoint binding that you established in IIS Manager for the site.

[PlausiblyDamp]

@tg - So you "deploy it to a web server". What does that mean? I published my files. What's next? Do I have to do all this? https://learn.microsoft.com/en-us/as...=visual-studio My coworker took over to actually deploy it, and says I have no web page to land on, there's no default.html. I'm trying to get answers to what he's doing exactly.

That is a bit of a convention / historical thing - if you were serving up plain html sites the web server would need a default page to serve up; this would typically be something like index,html or default.html and that might be what your coworker is looking for. However, if you are deploying something like an MVC app then this isn't required as the .net framework takes care of what happens.

[MMock]

So this is what he asked me and yes, good question.
Do you have an example on how to access the site on a web server? There are no razer pages in the deployment and that _host file doesn't exist either. When you run it in VS does it launch a browser?
Of course when I run it in VS it launches a browser. What do you do after it's actually deployed to a web server?

[MMock]

Skip my last 3 questions. He said there was some service he hadn't started. It's working.