NOTE: This post is part 4 of a series on developing and deploying cross-platform web apps with ASP.NET 5:
Download instructions and code for this post here: https://github.com/tonysneed/Deploy-AspNet5-Azure-Docker.
Over the past few years, a phenomenon known as “the Cloud” has appeared. While the term is rather nebulous and can mean a number of different things, with regard to business applications it generally refers to a deployment model where apps run on servers provided by a third party that rents out computational resources, such as CPU cycles, memory and storage, on a pay-as-you-go basis. There are different service models for cloud computing, including infrastructure (IaaS), platform (PaaS) and software (Saas). In this post I’ll focus on the first option, infrastructure, which allows you set up Linux virtual machines where you can deploy Docker images with your ASP.NET 5 apps and all their dependencies. There are a number of players in the IaaS market, including Amazon Elastic Compute Cloud (EC2), Google Compute Engine (GCE) and Microsoft Azure, but I’ll show you how to deploy a Dockerized ASP.NET 5 app to Azure using Docker Hub, GitHub and the Docker Client for Windows.… Read more
Not too long ago I posted a tweet that immediately went viral. (OK, it’s all relative – to me 66 retweets and 120 favorites is viral.) It referred to Microsoft’s Engineering Guidelines for contributing to its open-source repository on GitHub for the next version of its web development platform, ASP.NET 5.
You may be familiar with other C# Coding Guidelines. And generally I’m a huge fan of picking a set of guidelines, making necessary adjustments, and sticking to them as a team. But what I appreciate about the ASP.NET 5 guidelines is that they not only cover coding guidelines, but also include other vital aspects of software development, such as source code management, product planning and issue tracking.
One of the first things listed is the guidelines for submitting pull requests and a description of how they are reviewed and approved (using an emoticon!). Their Git branching strategy is also described, as well as the solution and project folder structure and the assembly naming pattern. It’s notable that xUnit is used for all testing and is indicative that xUnit has now supplanted both MSTest and NUnit as the preeminent testing platform. (In other words, just use it.) It’s also worth noting that to use xUnit you no longer need to install a Visual Studio extension – adding the xUnit NuGet package is all you need to do for tests to show up in the Visual Studio Test Explorer. … Read more
Now that I’ve jumped fully on board the Git and GitHub bandwagon, I’m spending a lot more time at the command line. In fact, I find myself working with both Visual Studio and the command prompt simultaneously, constantly switching back and forth between the two. The main reason is that, while Visual Studio 2013 makes a great Git client and tools such as TortoiseGit are a great help, there are some Git commands, like stash and rebase, that either aren’t supported well by the tools or are just easier to perform at the command line. Besides, most of the online Git tutorials list Git commands.
DOWNLOAD Cmder here: http://bliker.github.io/cmder.
Another reason why I find myself more on the command line is that I’m working with ASP.NET 5, which requires the use of a command prompt for managing versions of the runtime and generally embraces command line tools as a first class citizen. Finally, there’s Chocolatey, for easily installing tools at the command line, and, of course, PowerShell for automating actions with scripts.
As my need to work at the command line has increased, so has my frustration with the standard windows command prompt. Thankfully, I’ve run across a very nice command prompt replacement called Cmder, which combines the console emulator, ConEmu, with cmd enhancements from Clink and Git support from msysgit. … Read more
The next version of Entity Framework will be called “Version 7” and will be released as part of the next version of ASP.NET, called “ASP.NET 5.” If you’re currently on EF6, you might jump to the conclusion that you should upgrade to EF7 as soon as it hits the streets. But the EF team has made clear that you’re going to want to hold off upgrading to EF7 for a while:
“We won’t be pushing EF7 as the ‘go-to release’ for all platforms at the time of the initial release to support ASP.NET 5. EF7 will be the default data stack for ASP.NET 5 applications, but we will not recommend it as an alternative to EF6 in other applications until we have more functionality implemented.”
This means that the initial release of EF7 won’t include all the features a real-world ORM (Object-Relational Mapping) tool should support (for example, inheritance mapping). But if you can live without those features, or if you are developing an ASP.NET 5 app that needs to target CoreCLR, then feel free to make the move to EF7.
So when might you want to upgrade from EF6 to EF7?
For some folks the answer will be, “Maybe never.” That’s right.… Read more