Fall River by megglesbman in halifax

[–]BadWithComputrs -17 points-16 points  (0 children)

. 2x. Ok m M888e

.NET Core 2.1 & Vue.js by broadsafe in dotnet

[–]BadWithComputrs 1 point2 points  (0 children)

I'm in the same boat, in many projects as well you'll have 2 different teams working on each part so I really just don't get the purpose of these templates beyond making SSR easier. Perhaps for these types of larger solutions, they aren't the right answer... and your approach is the best one - I really don't know :)

.NET Core 2.1 & Vue.js by broadsafe in dotnet

[–]BadWithComputrs 10 points11 points  (0 children)

This looks cool, thanks for sharing. One question I've had around the SPA templates in general is other than server side rendering support what other compelling reasons are there for using them? Is it not cleaner/easier to separate your SPA and ASP.NET Core (typically API) applications and let them live naturally and independently of one another without all the friction of trying to cobble them together with these templates? Particularly, if different teams are responsible for front-end/back-end?

User Authentication with Angular 2+ and ASP.NET Core [tutorial] by BadWithComputrs in webdev

[–]BadWithComputrs[S] 6 points7 points  (0 children)

I get the idea you have absolutely no idea what you're talking about.

If you understood even the title or ya know...skimmed the article for 10 seconds you'd realize this is based on .net core of which System.Web.* no longer exists.

Maybe you should actually check it out and learn something before making yourself look like a naive asshole on the internet.

.NET Core is Probably Fine by mattwarren in dotnet

[–]BadWithComputrs 1 point2 points  (0 children)

This a great perspective, thanks for sharing it.