If you use Visual Studio, then you’ve probably crossed path with the Text Template Transformation Toolkit (or T4). For those who aren’t familiar with it, it’s a fairly straight-forward templating engine built into Visual Studio. The recent work on ASP.NET Core to enable cross-plaform web development, got me wondered what T4 might look like in this enviroment. Last weekend, I started hacking on Bricelam.TextTemplating, a T4 implementation for ASP.NET Core.
In previous posts, I’ve talked the new .NET Core CLI commands and the enhanced NuGet commands in Entity Framework Core. This post dives into some of the changes we’ve made to enhance the design-time experience of Migrations.
With Entity Framework Core comes the great opportunity to improve upon EF’s legacy by incorporating all the lessons we’ve learned over the past few years of developing this software. For me, that means a chance to improve on one of the first features I worked on after joining the team over four years ago: Code First Migrations’ NuGet Commands. In this post, I want to talk about some of the improvements to these PowerShell commands.
One of the new platforms that we’re targeting in Entity Framework Core is ASP.NET Core. With this new platform comes a new set of challenges for how we enable the Entity Framework commands. Ever since Entity Framework 4.3, we’ve provided a set of PowerShell commands that could be run in Visual Studio from NuGet’s Package Manager Console. However, that won’t help you if you’re developing on OSX where neither PowerShell nor Visual Studio are available. This post will show you how to use the new Entity Framework .NET Core CLI Commands.
Thanks to my work on Entity Framework’s Code First Migrations NuGet PowerShell commands, I’ve gained quite a bit of experience programming in PowerShell. In this post, I want to show you some of PowerShel’s query operators.
subscribe via RSS