You are new to cloud development, your executive team has charged you with developing some prototypes or real-life applications in the cloud space.
You are mainly a Microsoft shop (Visual Studio, .NET, C#, ASP.NET, SQL server, etc) or you are the Microsoft workload champion at your company.
You are open to Azure or AWS. Where do you start? I am here to guide you! I'm going to show you how to effectively start with cloud development using visual studio IDE. The Journey starts here: https://azure.microsoft.com/en-us/product-categories/developer-tools/
If you need to read more about cloud development with visual studio, then proceed here: https://azure.microsoft.com/en-us/products/visual-studio/
The next thing from there is to hop over to visualstudio.microsoft.com and download the appropriate visual studio edition. But, for the purpose of this post, I am assuming you are downloading the free community addition.
Download Visual Studio 2019 Community Edition for FREE from here: https://visualstudio.microsoft.com/downloads/
And one question people often ask is this: what is the difference between visual studio community addition and visual studio professional or visual studio enterprise?
In terms of supported usage scenario, the only difference is that you cannot use the visual studio community Edition in a medium or large enterprise, meaning a company with more than 250 PCs or $1,000,000 in annual revenue.
As for the integrated development environment, quite frankly visual studio community and visual studio professional offer almost the same features . CodeLens is a little striped down in the community edition.
Visual studio community and visual studio professional 2019 offer the same integrated development environment in terms of advanced debugging and diagnostic, and the 2 edition offer the exact same feature in terms of testing tools, Cross-platform development and collaboration.
Alright, so hold your peace, go over to visualstudio.microsoft.com and download the visual studio community edition and don't worry, you are getting almost the same thing as visual studio professional.
Now, with that behind us, I assume you have downloaded visual studio Community Edition.
The installer is a collection of features called workloads, that you need to select depending on the type of development you are engaged in, and this is very important so you don't load everything that you don't really need or miss out on the features required for cloud development.
In the Visual Studio installer, install Visual Studio (or modify an existing installation). Make sure the Azure development and ASP.NET and web development workloads are selected.
Once you select those workloads, the Azure Development workload installs the following features:
I recommend at this stage, you jump over to:
Create your first App as in the following article:
Now, did you follow the above instructions and published your first app to Azure? If yes, congratulations! If not, make an effort and do it, because I am just going to build on that.
So instead of publishing directly to a Microsoft Azure what you should do is create a source control account like on github or Azure DevOps and rather push your code to that source control system, then build some type of continuous integration continuous deployment pipeline that would take your code and deploy to Azure.
Now how do you get the infrastructure in place in Azure and this is where we build on what you did on the previous tutorial instead of publishing directly to Azure and selecting services by clicking on the UI and all of that, we are going to add a new project to our solution, an Azure resource group project, and immediately you will notice that this project is going to inherit the name of our web project.
In this case, I added a new Azure resource Group project called IaC.Pacosoft.Web and it generated all the scripts needed to create our Azure App Service.
This concept of Infrastructure as Code is crucial because you want to make sure your application is deployed to the same environment at all time: This project will then be updated and even be used to create infrastructure deployment for Staging and Production environment, and can be deployed separately from your code or included as the first step in your CI/CD pipeline.
You can read more and follow the tutorial for Creating and deploying Azure resource groups through Visual Studio here:
Once you setup your source control management system (GitHub, Azure Repos, etc), you can now setup your CI/CD pipeline that will look like this:
From this point on, you and your fellow developers only have to focus on writing code and checking in. Never again will you or your Operation Team worry about infrastructure. Never!
That is the beauty of cloud development.
Popular posts from this blog
So, you fire up Visual Studio, create simple ASP.net web site. Hit F5 and crash! You get a weird error that says: Specified argument was out of the range of valid values.Parameter name: site I had this issue recently after a major Windows PC crash/refresh and as I finally found out the issue was IIS not running, I wondered why the above error message is not a little bit more precise. Anyway, just re-install IIS features and you are ready to go. Windows + R (open the run box) Type AppWiz.cpl (Start the control panel for apps and features) Click "Turn Windows Features On or Off" Make sure Internet Information Services is checked as below:
Exam 70-487: Accessing Data - How to choose the Appropriate Data Access Technology - Entity Framework?
Since the days of Visual Studio 2008 and .NET Framework 3.5 in 2008, Entity Framework has served as the primary data-access technology for the .NET ecosystem. Entity Framework is an object-relational mapper (O/RM) that enables .NET developers to work with a database using .NET objects. It eliminates the need for most of the data-access code that developers usually need to write. While Microsoft is aggressively pushing for cloud version of pretty much every piece of software they have ever created, Entity Framework still enjoys tremendous popularity, it was last year described by Microsoft as the most popular package listed by NuGet.org . Which is normal because "Entity Framework is Microsoft's recommended data access technology for new applications.", as Microsoft puts it. A comprehensive version history from EF 3.5 to EF 6.2 of today can be found here and the current state of EF and future updates (Entity Framework Core, Entity Framework 6, Compare and choose betw
Exam 70-487: Accessing Data - How to choose the Appropriate Data Access Technology - Azure Cosmos DB?
According to Microsoft, Azure Cosmos DB is a database for building blazing fast, planet scale applications with native support for NoSQL. It was built from the ground up with global distribution and horizontal scale at its core. It offers turnkey global distribution across any number of Azure regions by transparently scaling and replicating your data wherever your users are. Azure cosmos DB is now part of Exam 70-487's latest update and you should study it deeply. Focus on understanding when it is a perfect choice for data storage and access.It is important to read some of the use cases presented by Microsoft: Common Azure Cosmos DB use cases CosmosDB can be used for document, key value, relational, and graph models. It is more or less a NoSQL database because it does not rely on any schemas. However, it uses query language similar to SQL and can easily support ACID transactions. CosmosDB is useful for companies that are looking for a database system that is scalable and