• .NET Framework (for these apps, there’s also the.NET Porting Assistance).
  • Desktop
  • Xamarin
  • Other Windows-native Applications

It doesn’t also support.NET AWS Lambda function, but that tooling will be added eventually. AWS stated that it is seeking customer feedback to improve its.NET app deployment process in light of the increasing complexity of AWS and.NET environments. This was apparently due to the fact that the process was too difficult to use existing tools. The feedback could be summarized into three questions, according to the team.

  • What is the best service for my application? There are many compute services available in AWS. It can be confusing to choose the right one if you’re new to AWS.
  • How can I make the learning curve shorter? There is still much to learn once you have chosen a compute service. It can be both overwhelming and time-consuming.
  • How can I encourage the best deployment practices in my team? Visual Studio is great for prototyping, initial testing, and deployment. Customers want to share their best practices with other teams once they have moved beyond this phase. This is why automated deployments are used.

AWS said that this resulted in a 180-degree shift in the company’s approach. “Instead of providing a plethora for compute services, we want a single tool that starts at the.NET app; a tool which provides an opinion and guides to the right service to your application.” AWS noted that the developer preview addresses only the first two items from the feedback list. The second item is “How can I promote best deployment practices within our team?” The AWS Cloud Development Kit (CDK) will be used to address these issues. The initial experience will be completely managed, but developers will soon be able to gain a better understanding of the features and functionality. More information is available here.