Why so mean? You can look at all of the commits and see that the same dev who has been writing these drivers and apps pretty much single handedly has been making commits on the site for the past few years. https://github.com/microsoft/MIDI/commits/main/docs
You can even PR fixes if you want to show off your web dev skills.
I've been doing this lately, building a Godot game with Copilot CLI. I'm using Godot MCP Pro which can automate interactions and screenshots, and have the whole game script in a markdown doc. I was happily surprised when I asked for a walkthrough and it all just worked, found and fixed some regressions while I was sleeping.
What's with the "just copy it" thing? Nobody does that, we use NuGet packages, GitHub Actions, SDK supported containers, reproducible cross-platform builds from command line, etc.
edit: I'm sure some people use file/copy, but you sure don't have to. That stopped being a common thing 10+ years ago with cross-platform .NET.
There are several ways to manage migrations depending on the team structure and dev practices: SQL scripts, command line, bundles (single-file executables), and in-app. The team recommends SQL scripts since they can be reviewed, tuned, and managed by a DBA but take your pick. https://learn.microsoft.com/ef/core/managing-schemas/migrati...
The post specifically calls out wealth concentration (e.g. becoming wealthier than one's fellows) as a major problem, and the donations are focused on working against that. Review the list of dentations, as you may have missed that these are organizations that help people in need rather than, say, recent examples of billionaires buying votes.
Install size depends on the features you pick when you install. Web / service / library development is small, desktop / mobile / C++ gets bigger as the toolchains + sdks + emulators are big. If your VS install is 30 GB and that's a problem, run the installer, click modify, and uncheck stuff you're not using. A lot of devs check off everything "just in case" but since you can add other features when you need them, it's better to start with what you know you'll use.
The installer is a separate binary and currently still requires Rosetta. There's an update due out very soon (a few weeks) that will remove the Rosetta requirement. The team prioritized getting the application fully native before the installer since you spend a lot more time running the app than the installer.
Also it's important to know that Visual Studio for Mac isn't the exact same application as Visual Studio (Windows). Visual Studio is 25 years old and has some Windows specific features that don't make sense on macOS. Also, Visual Studio for Mac is optimized to integrate with macOS features (e.g. accessibility and themeing). There's a lot of code shared between the editor, project system, debuggers, etc., and we try to balance making them as similar as possible while following the macOS app guidelines and conventions.
Disclaimer: I'm on the .NET team at Microsoft, and work with the Visual Studio for Mac team a lot.
There is the Blazor Hybrid option with .NET MAUI. You write your UI using Razor (HTML + C#) and can use native controls and features when needed. As a .NET dev who prefers HTML to XAML, this feels more natural to me for a lot of apps.
A little oversimplified - Visual Studio Community can be used to develop commercial software, with restrictions to (summarizing) 5 conccurrent users in non-enterprise organizations. https://visualstudio.microsoft.com/license-terms/mlt031819/
Hi, I'm on the .NET community team. Here's what we see as the happy path for .NET:
- .NET website (https://dot.net) - High level info on different workloads, 5 minute in-browser tutorials, links to live shows and community
- MS Learn (https://aka.ms/mslearn-dotnet) - Interactive tutorials with learning paths built from 30ish minute learning tutorials
- Docs (https://aka.ms/msdocs-dotnet) - More in-depth documentation on specific tasks and features, e.g. API documentation, performance optimization, security guidance, etc.
While you can go directly to any of them, the dot.net site will link you to Learn modules that will link you to docs, so hopefully you can start on the dot.net site and it will help you find the right place.
One thing I really like (and I'm totally biased because I've helped set it up) is https://live.dot.net. Those are all our live shows with the PM and dev teams. We've got a show every day of the week, and there's always really good Q&A in the chat.
Here's a really simple example of something that would benefit standard websites, not just complex web applications: image lazy loading.
<img src="..." loading=lazy>
Sure you can handle this with JavaScript, etc. The point is that this is one of countless papercuts - standard, useful behaviors that work everywhere but Safari.
I think this is a good partnership. One of the goals of open source software foundations is to eliminate risks due to dependency on a small developer team. In this case, HIBP is a fantastic resource being maintained, and paid for, by one developer. That's not good for the maintainer, it's not good for the community, and it's risky to the community. If the sole developer wins a spot on the next flight to Mars or time travels to A.D. 802,701, the code becomes unmaintained and the site hosting payment expires. Software foundations governed by rotating teams and aren't dependant on a single individual. This is an example of something that's relatively low investment for an established software foundation - some legal fees and discounted cloud hosting from a sponsor - and benefits the whole community.
Brief mention in the post, but FYI to the thread - .NET Foundation is an independant non-profit (501c6) foundation that supports the .NET open source community. It's run by a community elected board and funded by member donations and a diverse group of corporate sponsors. This is a great example of the kind of work they do to support the community.
Disclaimer: I was on staff at .NET Foundation 2016-2019.