.NET

1832 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

.NET Framework 3.5 Moves to Standalone Deployment in new versions of Windows (devblogs.microsoft.com)

submitted 1 month ago by nemeski@mander.xyz to c/dotnet@programming.dev

1 comments fedilink hide all child comments

top 1 comments

sorted by: hot top controversial new old

[–] transporter_ii@programming.dev 1 points 2 weeks ago

So, I had a version of Win10 that apparently didn't have .Net 3.5 Framework on it. It took an act of congress to get it to install. I eventually found a version of 4.x that included 3.5 in it. This installed.

I don't understand how I could have that much trouble with one of Microsoft's flagship products. Also, I could dig up programs I used on Windows 3.1 that would probably still run today. I get that things get old, but .Net 3.5 is not that old, at least compared to something that would run on Windows 3.1.

It bugs me that they think everyone can just move everything to the next .Net version every time one rolls out.

Man, it wasn't that long ago that I worked at a place that still has a classic ASP web page running.