New Azure App Service deployment

[michaelcsikos]

Azure Cloud Services and Web Roles have effectively been replaced by the new Azure App Service.

The API, Web and Mobile Apps are basically the same. "The only difference between the three app types (API, web, mobile) is the name and icon used for them in the Azure portal."

Is there a planned update to the Data Portal Configuration e-book or a blog post showing how to set up and deploy an n-tier CSLA app with the new App Services?

[rockfordlhotka]

Perhaps at some point, but there's no meaningful difference in how you create an ASP.NET host for the data portal in an App Service from any other ASP.NET hosting scenario.

[michaelcsikos]

Hi Rocky

OK, I have tried deploying several different ways but I can't get it to work properly. The SQL database and BLOB storage are both working on Azure. I can connect to them via the localhost on my PC (WebUI -> WcfPortal -> SQL). When I publish the WebUI and WcfPortal they display something but I can't get them to talk to each other.

I have created a new project with the following options: ASP.NET Web Application (.NET Framework) Empty template [x] Host in the cloud with App service

This creates a new app service, app service plan, and publish profile. I copied the WcfPortal.svc file and copied the appropriate nodes into Web.config. This project publishes successfully, and the (example).azurewebsites.net/WcfPortal.svc displays.

Then I published the WebUI to the same app service. (Or should this be to a second app service?) The main page displays, but trying to communicate with the WcfPortal shows an error, "Content Type application/soap+xml; charset=utf-8 was not supported by service (address). The client and service bindings may be mismatched." I have searched and tried different Web.config settings for the binding. The client and server settings seem to match, and of course it runs perfectly on my dev PC.

Then I tried creating a Cloud Service project with a WebRole. Again, the cloud service displays the WcfPortal.svc page. I published the WebUI to an app service, but now I get the error, "The caller was not authenticated by the service."

I have look at every Web.config file in the CSLA samples but nothing seemed to help.

What I'd really like is a sample with a database, DAL, biz library, WcfPortal and WebUI (preferably MVC5) and step-by-step instructions to deploy it to our own Azure account (preferably as an app service). I'd be happy to pay for an updated e-book or video showing this.

I'm using CSLA 4.6.500, .NET 4.6, MVC5.

Thanks for your help.

[rockfordlhotka]

You might want to look at this project: https://github.com/Magenic/MyVote

This is the demo used for the Modern Apps Live conference, and its services are hosted in an App Service. I think in the latest release from Orlando it is also hosted in ASP.NET Core, but if you go to the Las Vegas 2016 release it was using regular .NET in an App Service.

[michaelcsikos]

Thanks, I'll check it out.

[michaelcsikos]

I've looked at the the Las Vegas 2015 and 2016 solutions. It looks like they are not running a separate WcfPortal as recommended in the Data Portal Configuration e-book. I have given up on a 3-tier deployment for now. I've added the Dal, DalEf and DalMock references to the the WebUI project and published it successfully. I may look at a 3-tier deployment at a later stage when the project requires it.

[rockfordlhotka]

Ahh yes, you are right - that app uses HttpProxy instead of WCF because we support (or supported) client device types where WCF doesn't exist.

You might do that instead - I suspect you aren't running into a CSLA problem as much as a WCF security issue with newer versions of ASP.NET or the hosting environment. I generally always use HttpProxy these days, as we've put a lot of work into making it the best option with the lowest overhead and easiest configuration.