Go to the web.config and add a tag just before the end of the section. (Some of these might have been fixed if you are using a newer release of XAF than 12.1.7.)Īlso, if there are any errors, we don’t get much useful feedback unless we turn custom errors off. set the CopyLocal flag to true for all DevExpress assemblies.add a reference to the project 12.1.UI.remove the reference to stdole in the web.config section.(These will cause deployment in problems any environment, not just Amazon Web Services.) Ignore the long list of amazing additional features for now, (but one day you might need them.) Prepare the MainDemo for deploymentįirst we need to fix a few problems with the MainDemo. It is the recommended starting point for all new deployments regardless of size. In fact (and Amazon should advertise this better), the Elastic Beanstalk is designed to make it very simple to deploy applications quickly even if you have no intention of ever needing more than a single little instance. There are other Amazon Machine Images (AMIs) that include SQL Server Express, but these don’t support automatic deployment from Visual Studio. We could connect to it and install it, but it ends up being a lot of extra steps. However, the default ‘single machine’ does not have SQL Server Express installed. It might seem that the simplest would be to put everything on a ‘single machine’ instance. An Amazon EC2 instance is a virtual machine running an actual Windows (or other) operating system that you can connect to with Remote Desktop and configure however you want. With Amazon Web Services, the choices are endless. That sounds like a lot of features we don’t really need for the MainDemo, so let me explain.
Amazon Elastic BeanstalkĪmazon Elastic Beanstalk provides automatic capacity provisioning, load balancing, auto-scaling, and application health monitoring.
This part guides you through publishing the DevExpress XAF MainDemo application to the Amazon Elastic Beanstalk. Make sure this is up and running before continuing. In Part 1 we created an Amazon RDS instance of SQL Server to act as the database for the deployment. This is the second post in a series about deploying ASP.NET applications to the Amazon cloud.
0 kommentar(er)
