.NET

1464 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

Related communities

Wikipedia pages

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

founded 1 year ago

MODERATORS

[email protected]

What am I losing by not using the C# Dev Kit? (programming.dev)

submitted 4 months ago by [email protected] to c/[email protected]

2 comments fedilink hide all child comments

I exclusively use Visual Studio Code for editing code. I primarily work with Go, and a little bit with JavaScript/TypeScript, but I need to do some C# work.

I have no interest in using Microsoft's proprietary C# Dev Kit or dealing with their licensing terms. What capabilities am I losing? The marketing materials for the dev kit talk about a lot of stuff that appear to be features of the open source C# extension, so it's unclear which features are actually exclusive to the dev kit.

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

[–] [email protected] 7 points 4 months ago

Unless you're part of a large enterprise, you're not missing anything you're likely to care about.

VS Professional does some counterintuitive magic for handling big related sets of related projects. It's particularly valuable if one has been cursed to work with old school C# XML SOAP web services.

You're also missing out on strong support for some other awful proprietary data connector libraries.