With all the extra configuration, no way. I've done all sorts of variations and I'm visual studio all the way now. I'm even back to using Resharper.
Yes you can even use cli but we don't even bother with that. And hot module replacement is awesome and already set up in the environment. I've also got asp.net membership integrated,and I can call existing dot net code in dot net framework. I can even use entity framework canvas in dot net core 2 if I want to. On 21 Nov 2017 11:05 PM, "Craig van Nieuwkerk" <[email protected]> wrote: > The article is a bit old, but still relevant. The dotnet cli was not a > temporary solution until VS2017 supported the features, for most people who > are developing greenfields it should be their go to solution. Personally I > find using VS2017 for Angular or similar is really a legacy way of doing > things when your back end and front end are tightly coupled, and if you are > fitting a new front end to an existing product probably makes sense. I > would use VSCode every day of the week given the choice though. > > Craig > > On Tue, Nov 21, 2017 at 10:56 PM, Tony Wright <[email protected]> wrote: > >> That's old. That's before they provided templates in visual studio. You >> won't get as great an experience using vs code and good luck integrating >> your older code base. >> >> On 21 Nov 2017 8:13 PM, "Craig van Nieuwkerk" <[email protected]> wrote: >> >>> Also, you are best not using Visual Studio but using Visual Studio Code. >>> >>> https://www.hanselman.com/blog/dotnetNewAngularAndDotnetNewReact.aspx >>> >>> Craig >>> >>> On Tue, Nov 21, 2017 at 8:00 PM, Greg Keogh <[email protected]> wrote: >>> >>>> It will create all the plumbing and you just click Start with >>>>> everything in place. >>>>> >>>> >>>> Okay, I'll give it a bash tomorrow - fingers crossed - *GK* >>>> >>>> >>> >
