@geeyef, since Angular is the stuff that gets sent to the client and processed there, it's should be a snap to get it going in whatever server side code you're using (i.e. Node/Express, ASP.NET, PHP, etc.).
I suggest you start by creating your ASP.NET web app. Then find a good starter project for Angular 2.0. There are a lot of them. You could use my waterbug-ui project as a starting point if you want. Then just copy that project into a folder in your ASP.NET project. A lot of people put it in a folder called public.
The hard part whenever you're using a client-side framework like Angular inside of a server-side framework like ASP.NET is figuring out what you what code you want to run where. Some sites, pages, and tasks are best executed on the server side, some are best on the client side, and overall you may have a hybrid site. You may even (I hope not) run in scenarios where the server is generating client-side code.
Modern sites, however, tend to be more simple and single-purpose (and that's a good thing) and will only be either have server-side or a client-side logic. Certainly if you're just learning Angular 2.0 and ASP.NET Core 1.0, then it might be a good idea to learn them separately.