Discover and read the best of Twitter Threads about #DotNetCore
Most recents (7)
š” Do and Don't for string in C#
1. Always use
2. Don't use š
āļøIf you like my tweets, please join 400+ Software Engineers to receive an actionable tip weekly in your inbox through my Newsletter.(lnkd.in/d69Va5CM)
#csharpĀ #dotnetĀ #dotnetcore
1. Always use
2. Don't use š
āļøIf you like my tweets, please join 400+ Software Engineers to receive an actionable tip weekly in your inbox through my Newsletter.(lnkd.in/d69Va5CM)
#csharpĀ #dotnetĀ #dotnetcore
ā
Use an overload of theĀ String.EqualsĀ method to test whether two strings are equal
ā Use theĀ String.CompareĀ andĀ String.CompareToĀ methods to sort strings, not to check for equality.
ā Use theĀ String.CompareĀ andĀ String.CompareToĀ methods to sort strings, not to check for equality.
ā
Use overloads that explicitly specify the string comparison rules for string operations. Typically, this involves calling a method overload that has a parameter of typeĀ StringComparison.
Method Safety and Idempotency
1. HTTP Methods Introduction
2. Method safety with examples
3. Method Idempotency with examples
š§µā¬
#csharp #dotnet #dotnetcore
1. HTTP Methods Introduction
2. Method safety with examples
3. Method Idempotency with examples
š§µā¬
#csharp #dotnet #dotnetcore
GET is used to retrieve data, POST is used to save, PUT is used to update existing data edit is common example of it, PATCH is lighter version of PUT , it is used to update just a specific information instead of updating all data on server DELETE is used to remove records.
In CRUD operations
C stands for create : POST
R stands for read : GET
U stands for update : PUT/PATCH
D stands for delete : DELETE
C stands for create : POST
R stands for read : GET
U stands for update : PUT/PATCH
D stands for delete : DELETE
Ok, let's take a quick look at the @jetbrains "state of developer ecosystem 2020" report and what was interesting to me.
First, almost 20,000 developers took part. Many from midsize companies, so keep that in mind.
First, almost 20,000 developers took part. Many from midsize companies, so keep that in mind.
People still read books! That makes me happy. Devs get most info from community sites and social media. A few of you love the radio, apparently.
I see so many online conferences catering to the experience, but interesting to see that the vast majority of devs show up purely for the content.
who can fix this #dotnetcore #aspnetcore #vscode #intellisense issue on #macos. This is a horrible #dotnet new mvc experience
#dotnetcore3.1.00
#vscode latest
One of the beauties of shared abstractions is once the ecosystem starts to take advantage of them, adding value becomes that much more impactful. This is one of the goals of Microsoft.Extensions.* that we built while developing ASP.NET Core #dotnetcore #aspnetcore
It serves as a building block for what we call "application models" and attempts to handle the boring boilerplate and cross cutting concerns like dependency injection, logging and configuration.
The strategy is multi pronged:
- Introduce libraries with minimal dependencies that other libraries can take a dependency on without too much burden (ILogger, IConfiguration, IOptions, IHostingEnvironment) etc.
- Introduce libraries with minimal dependencies that other libraries can take a dependency on without too much burden (ILogger, IConfiguration, IOptions, IHostingEnvironment) etc.
Ok tweeting about some hidden gems in the release that people may not know about. #aspnetcore #dotentcore
First, the generic host docs.microsoft.com/en-us/aspnet/cā¦. We like the hosting model of ASP.NET Core and think it should exist in more application types. #dotnetcore #aspnetcore
Next, IHostedService. A way to run long running background operations in both the generic host and in your web hosted applications. docs.microsoft.com/en-us/aspnet/cā¦. 2.1 added support for a BackgroundService base class that makes it trivial to write a long running async loop.
This latest thing with #dotnetcore and #dotnetstandard is understandable, but also unavoidable, I think. Core lets the team move faster and break things because you don't have to upgrade it globally on a box; you can have 2.0 and 2.0.4 and 2.1 apps in isolation. 1/
You can't do that with full NetFX (or Mono?) so updates have to be much more cautious. Going from 4.7.2 to 4.8 will affect all apps running on that box. And with the Core 2.1 changes, a LOT of BCL APIs have changed. 2/
I suspect there will be a lot of internal discussions and meetings about getting, for example, the Span/Memory APIs into a shared .NET Standard, making sure the implementations and semantics are properly understood by everyone who needs to implement them. 3/
