I am currently reading Rocky's ebook on using csla.net 4 on deploying a dataportal to Windows Azure. But, I am uncertain about something because I am so new to Windows Azure. I understand the instructions on how to deploy a dataportal as a webrole. But, I don't want to incur any costs that aren't necessary. I already have one webrole, which is my ASP.NET 4 MVC web site. Do I "have to" deploy the csla.net dataportal as another webrole (and incur additional costs for another instance)? Or, can I deploy the dataportal to my existing webrole somehow? Is there a way to run both my website and the dataportal on my one Azure instance? Please excuse me if I am not asking this question in the right way.
If anyone has any experience with deploying a csla.net based website to Azure could respond, I would greatly appreciate it. Just to re-cap ... I have deployed my ASP.NET MVC 4 website to Windows Azure and my database is deployed to SQL Database (Azure). I am trying to get my dataportal working and I am hoping to find the most economical way to accomplish this task.
Best regards,
Chris
You can deploy your app in a 2-tier or 3-tier deployment.
In a 2-tier deployment your web server will configure the data portal to run in local mode.
In a 3-tier deployment your web server will configure the data portal to communicate with the app server (probably another web role).
These are the same options as deploying to IIS servers hosted by your organization. Azure has no impact on the architectural choices you can make.
Thank you kindly, Rocky! I decided to configure my app as 2-tier by setting the following config appsettings:
<add key="CslaDataPortalProxy" value="Local" />
<add key="CslaAutoCloneOnUpdate" value = "false />
I have no asynchronous work going on and I understand the risk of the second setting. For so many years I've used a remote portal that I had actually forgotten how easy it is to configure csla to run as a 2-Tier app.
I"m taking baby steps with Azure and to start off, I think this will be an economical way to deploy.
Best regards,
Chris
Copyright (c) Marimer LLC