This is the first in a multi-part blog series where I will discuss building an application using Angular2, Typescript, Webpack, .NET Core, Web API and Entity Framework.
I tend to skip through long blog posts, espcially those littered with screenshots of Visual Studio dialogs or similar. I like to get to the point when reading blogs and aim to do the same when writing them. That said, the series wouldn’t be complete without a brief introduction to each of these technologies.
Early releases of Angular focused on System.js for module loading. Since then, the Angular team has fully embraced Webpack which has become the tool of choice for build scripting, bundling and module loading. Honestly Webpack is a big topic that I’m only beginning to grasp so I will give a brief introduction to this topic. For more information see http://webpack.github.io/
.NET is a huge subject and no-doubt if you’re reading this you are very familiar with it. .NET Core is its newest incarnation and is the first version that can run cross-platform. As long as we don’t need any features in standard .NET, I’d like to build the application in .NET Core even though I will most likely only be hosting the application on Windows.
.NET Web API is the server-side technology that we’ll use to create your REST server. There are many other choices that we could have used such as Node.js or Java, but for me .NET Web API is a powerful choice that lets us develop our backend quickly while utilizing a language that I know very well, C#.
We’ll be building out our persistence using Entity Framework and SQL Server. I’ll briefly cover Code first migrations and how to build a data access layer using Entity Framework and how to provide that our Web API layer.