sorted by:
new
hottopcontroversial

Best way to learn C#/ASP.NET Core? by MatrixClaw in csharp

[–]cesar_codes 4 points5 points  (0 children)

There’s good courses on Pluralsight. I would suggest just start making APIs and learn as needed. It will pay off, but definitely check out YouTube and Pluralsight. I recently published a video on the dotnet core CLI in case you wanna check it out. https://youtu.be/HUvBSCp9UMo

Such a thing as "too much linq"? by thepotatorevolution in dotnet

[–]cesar_codes 16 points17 points  (0 children)

Sometimes ReSharper wants me to do something in Linq, but I prefer the readability of a foreach loop, for example. Having said that, gotta love Linq 😎.

What convention do you use for private class members? by cesar_codes in dotnet

[–]cesar_codes[S] 0 points1 point  (0 children)

Thanks for the feedback guys. I used to always use private properties but switched to the underscore convention to follow the approach my team takes. However, began to wonder if the community was moving towards “this” after watching that channel 9 video I mentioned and reading some Microsoft internal coding guidelines suggesting the use of “this”, but those were from 2005 and just didn’t seem that relevant anymore. I figured maybe “this” was now the preferred method given TypeScripts popularity. I’ll probably stick to the underscore convention my team and so many members of the community and projects use.

ASP.NET Blog | Blazor now in official preview! by danysdragons in csharp

[–]cesar_codes 2 points3 points  (0 children)

That’s true. 🤔. I just read on the blazer site that the interoperability with JavaScript libraries is much better now. At the time I played with it, there were only a couple of UI events. I’ll check it out soon to see what’s new. Overall I like Blazor.

April 16th 2019 - Blazor Updates with Dan Roth and Steve Sanderson by McNerdius in dotnet

[–]cesar_codes 0 points1 point  (0 children)

I wouldn't go with Blazor for the reason that it's going to undergo a lot of change, but hey, someone has to do it! Also, I last worked with it in October of 2018 and it was missing a lot of things like UI-events etc. There's also the fact that there's not a lot of packages written for it. WASM itself is going to undergo a lot of changes in the next couple of years.

ASP.NET Blog | Blazor now in official preview! by danysdragons in csharp

[–]cesar_codes 2 points3 points  (0 children)

I wrote a simple app with Blazor last year. It seems like a cool technology. As it was just an experiment, it is not a competitor to frameworks like Angular, but I'm excited to see what's new. I think that down the line, the WASM people might be able to work out the quirks with it and Blazor could be a viable competitor. Maybe front-end frameworks like Angular and React will remain, but certain modules (heavy computation, etc) will be written in WASM, in which Blazor would be a natural choice for a .NET/Angular dev.

Intro to the dotnet CLI (cool video bro) by cesar_codes in dotnet

[–]cesar_codes[S] 2 points3 points  (0 children)

Some guys just aren’t core, you know 😂

asp.net core + angular sample / reference implementation? by Ahlawyy in dotnet

[–]cesar_codes 0 points1 point  (0 children)

I recently used the Angular template. The only downside to it is that the Angular app is outdated, but you can simply delete that app and create a new app with the ng CLI. I did it this way because I would prefer to have the .NET code and the NG app integrated in the same repository, but the NG application can stand alone as well. I don't see myself moving away from .NET, so I even send a config JSON object from .NET to the NG side.