Activities of "godrunner"

Well @BBakerMMC, actually, I think that what needs to be done is that you need to donate the entire source for you project to the team here so we can then just scaffold that up and we will have nothing left to learn! :-) Just think, it would be for the betterment of humanity and likely save the planet too.

The problem I had with Azure was some of the settings for multi tenancy in appsettings.json. Once I got that straightened out it wasn't a big deal.

I agree that actually taking the time to look for an answer and knowing where to look is the biggie. Right now there are quite a few places to look. For me, working examples are really the best.

@BBakerMMC, you have some great points!

I think you misunderstood me a bit. Maybe I just speak Canadian 'eh? :-)

• My point is, if the same questions are being answered many times over, (like publishing on Azure for example) then the answers need to be easier to find. Having them in one place with links if applicable would save everyone a lot of time in the long run. Many of the answers are in this forum, on github or in the Zero or ABP docs or a sample. So, just a link even that says, "There is a good example of how to do this here" would help and save time for everyone perhaps.
• When starting out cold, in takes a while to sort out what technologies are coming from where and just a simple list a least kind of like I did above might help others. This was actually the list I made up of thingss I needed to refresh or learn. I was a bit rusty. It would have helped me. I did the learning. Maybe links are not necessary for this.
• I hear you on the .js mess. It is stunning the number of dependencies that is for sure. Maybe with the recent exploits and all people will start using script blockers, then we are out of business. :-) I'll take another look at MPA. It didn't look as elegant to me but maybe it solves some other problems.

@pankajmathur, you could trying temporarily bumping up the level is SQL Server service/performance. See if that makes any difference....

@BBakerMMC, why do you always answer questions JUST before I to? I know, I know, you are on AU time right?

:-)

@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.