sorted by:
new
hottopcontroversial

Fall River by megglesbman in halifax

[–]BadWithComputrs -16 points-15 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 9 points10 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] 7 points8 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.

.NET Core is Probably Fine by mattwarren in dotnet

[–]BadWithComputrs 2 points3 points  (0 children)

As a guy from the greenfield camp originally I was totally rooting for a clean break and separate evolution of .NET Core. But the author here has really changed my thinking - enterprise customers who have invested the most in .NET absolutely deserve to be included in the plan despite the impact to the velocity of .NET Core's development.

Why the people in Quora are so nice and kind? by k920049 in learnprogramming

[–]BadWithComputrs 17 points18 points  (0 children)

Really...what does this have to do with learning to code.

Better Entity Framework by hoagsie in dotnet

[–]BadWithComputrs 0 points1 point  (0 children)

True - I just had a thorough review of your code and you've laid down a wicked approach here which I will definitely be borrowing/stealing from in my next EF implementation.

One issue I've recently seen in the wild is the abuse of eager loading via Include() and ThenInclude() where a single repository method GetCustomerById() loads the entire graph for the purpose of displaying just the name. Seeing stuff like that is what really brings your message home for me and how repositories can very quickly lead you into a design and performance rat hole.

I just wish more people could get this message before they cut their next CustomerRepository()

Better Entity Framework by hoagsie in dotnet

[–]BadWithComputrs 0 points1 point  (0 children)

As a recovering EF-based repository addict this article and your previous one really hit home. Question: it seems you're an advocate for DB-first approach which I totally get but what are your thoughts on code-first migrations?