Hi Greg, As an aside, these “Website” projects are really a simple compile on demand project type. You optionally have web.config, a bin folder to drop pre-compiled assemblies into, an App_Code folder for code.
We use this project type for our non mvc web projects because for us, it allows us to work faster, no having to run, find bug, stop, edit, compile and re-run, it simply becomes run, find bug, edit, refresh David From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Coates (DX AUSTRALIA) Sent: Thursday, 28 January 2016 8:14 p.m. To: ozDotNet <[email protected]> Subject: RE: Azure static web sites https://blogs.msdn.microsoft.com/acoat/2016/01/28/publish-a-static-web-site-using-azure-web-apps/ Cheers Andrew Coates, ME, MCPD, MCSD MCTS, Developer Evangelist, Microsoft, 1 Epping Road, NORTH RYDE NSW 2113 Ph: +61 (2) 9870 2719 • Mob +61 (416) 134 993 • Fax: +61 (2) 9870 2400 • http://blogs.msdn.com/acoat From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Thursday, 28 January 2016 2:13 PM To: ozDotNet <[email protected]<mailto:[email protected]>> Subject: Re: Azure static web sites I could do a quick walkthrough later today if that’d help. There aren’t many options that need to be chosen. That'd be great if you have a break. Only the skeleton of the steps should get me going. Once I get the files in the right sort of project and deploy with suitable settings I should be able to extrapolate and find all the configuration stuff about host headers and DNS and the like. I'll make a blog post after I get it all working -- Greg K
