@dparizek, although I have never tried the merged version, my guess is there isn't that much difference except primarily the location of the files.
The big downside of Azure App Services is that you can't use ports, however, for us at this point, after a lot of testing with some other options, it really works nice to have them separated and ya gotta love those slots.
@Mudase, I have a test deployment working on Azure with no SSL for now and it works fine. You just have to configure your site in the Azure "Custom domains" page for your app service and make the required changes to your DNS as per the instruction on that page.
Excellent. Glad we got that settled! If you read some other comments here, you can see how valuable it would be for you guys if you came up with a way for your customers to find ongoing value over time in a cleaner way to upgrade projects. I don't know if there is a good solution for that but something to keep in mind!!
Greetings @JapNolt
Here is The. Really. Simple Solution.
When I first got started with ASPNET Zero, I spent quite a bit of time evaluating which versions to use and the related pro’s and cons of each. I settled on Angular deployed to two Azure App services. (not merged) Although this will cost a bit more, it keeps my options wide open for some things I need to acomplish. One big drawback of App Services is you can not use specific ports. One big plus though is the “slots” and many other features. It is a nice solution if you want to have a complete staging environment as well as production. It can save a lot of time, the workflow is less error-prone and for me, that more than offsets a bit of added expense. So, here is the simple solution. (NOTE: I used 4.5.1 for my testing but I am pretty sure this will all still work with 5.x. I am waiting for 5.1 to upgrade my project to let some of the bugs/dust settle a bit.) :-)
Step 1 - Create App Services on Azure All you have to do is set up AppServiceA for your Angular project let’s say AppServiceH for your web.host project.
Step 2 - Tweak web.host appsettings.*.json files only ONCE In your web.host project, add an appsettings.Production.json right along side of appsettings.json if it is not there already. (if I recall correctly a default App Service will default to production) Now you can leave your appsettings.json set to your production environment and configure your appsettings.Production.json to look something like mine below. Use the same principle for Staging. These correspond to your slots on Azure.
In your appsettings.Production.json file, change the connection string to point to your Azure DB and make the following changes below that. This is all you need to have in that file.
"App": {
"ServerRootAddress": "http://{TENANCY_NAME}.AppServiceH.com",
"ClientRootAddress": "http://{TENANCY_NAME}.AppServiceA.com",
"CorsOrigins": "http://AppServiceA.com"
}
}
Step 3 - Tweak appconfig.production in the angular project
{
"remoteServiceBaseUrl": "http://{TENANCY_NAME}.appserviceH.com",
"appBaseUrl": "http://{TENANCY_NAME}.appserviceA.com"
}
Step 4 - Build and Publish
Publish your web.host project to AppServiceH and I just FTP the Angular app up to AppServiceA (including web.config) and viola! Everything works perfectly with multitenancy!
@hikalkan, to clarify, do you mean:
The license check is only enforced during the duration of a valid subscription to ASP.NET Zero.
If so, that might help to clear things up a bit.
Greetings @bolenton!
I am hosting as an app in my testing and think I will do that when I go to production. That is just what I am thinking.
Greetings @bolenton!
In my testing, I have had it all running successfully on Windows Server with IIS as well as Azure. I really like Azure Webapps because of the "slots" feature, but you can't user ports there. Either way, you need to make sure you have full access to DNS settings.
Greetings and congratulations again on v5! As I was looking through some new docs, I had a look at the roadmap. Very interesting! I see, “RAD (Rapid Application Development) tooling.” What is the plan for this? Complete drag and drop solution that does all the work for us? Lol Ok … how about scaffolding based on some classes that model the DB? It would be quite a time saver if one could scaffold right up to and including even a basic app service? So much of that is redundant. Maybe even into the UI a bit? Nice!
C:>ZeroCreate myapp --template EverythingINeed
Also as for the “Calendar Module”, what are you thinking for this? Basic scheduling? That would be pretty nice too! :-)
Hey @poolman!
<cite>poolman: </cite> Can anybody actually log in with 5.0.2?
I have the ASP.NET & Angular version working fine here. I did delete the old DB first though. Maybe try deleting some cookies and try again?
<cite>godrunner: </cite> I also noticed that the download page says v5.0.0 when yesterday it said v5.0.1, so that is confusing as to what version is actually available.
I was looking for v5.0.2
Oh, I see now that after selecting the "Project Type" the version number changed from 5.0.0 to 5.0.2.