.NET

1741 readers

1 users here now

Getting started

Useful resources

IDEs and code editors

Visual Studio (Windows/Mac)
Rider (Windows/Mac/Linux)
Visual Studio Code (Windows/Mac/Linux)

Tools

Decompilers: ILSpy, dotPeek
Scratchpad: LINQPad
Online playground and IL viewer: SharpLab

Rules

Rule 1: Follow Lemmy rules
Rule 2: Be excellent to each other, no hostility towards users for any reason
Rule 3: No spam of tools/companies/advertisements
Rule 4: Submit the original source. If a post reports on something found on another site, submit the latter

Related communities

Wikipedia pages

.NET (open source & cross platform)
.NET Framework (proprietary & Windows-only)

founded 2 years ago

MODERATORS

erlingur@programming.dev

starman@programming.dev

Spyros@programming.dev

Microsoft designates Blazor as its main future investment in Web UI for .NET (devclass.com)

submitted 1 month ago by TomasEkeli@programming.dev to c/dotnet@programming.dev

15 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] jubilationtcornpone@sh.itjust.works 0 points 1 month ago (1 children)

Client side Blazor has a bright future. Server side, not so much.

[–] Mihies@programming.dev 4 points 1 month ago

I disagree. Server side blazor is really a great fit for internal apps at least. Then you have a combination of the two, where your app starts quickly in server side mode, once the wasm code is downloaded, it switches to client side mode.