Creating a New Project with ASP.NET Core and Angular

You would think that creating an ASP.NET Core application that uses Angular would be easy-peasy. After all, there's an "Angular" option in the new project wizard for an ASP.NET Core application! Sadly, reality is a cruel mistress, and if you take that approach to creating your next Angular + ASP.NET Core project, you'll be in for a world of hurt. Here's a better approach. Please note: This article was written for the .NET Core 2.0 project templates. The new .NET 2.1 templates, currently in preview, change things up for the better. Here's an overview of the new template, including some improvements! Credit where credit is due: this post was inspired by Levi Fuller's take on the topic. I made a few changes along the way, but his approach got me started! Friends Don't Let Friends Use File - New Project - Angular Let's get this out of the way: yes, there is an easy-to-use, File - New Project way to make an ASP.NET Core application with Angular. But you don't want to use that. This will give you an Angular 4x project built directly around Webpack.

✔ Read More...

I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

asp.net core,angular,visual studio 2017