C# Dev Kit – Now Generally Available
source link: https://devblogs.microsoft.com/dotnet/csharp-dev-kit-now-generally-available/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
C# Dev Kit – Now Generally Available
Wendy Breiding (SHE/HER)
Today, we are thrilled to announce the general availability of C# Dev Kit, a Visual Studio Code extension that brings an improved editor-first C# development experience to Linux, macOS, and Windows.
A Community Effort – Thank You!
Since our initial preview in June, we have received both quantifiable data and invaluable community feedback that have shaped this product. Approximately 350 issues, primarily reported by our community, have been addressed. These enhancements range from quality improvements to scenario clarifications. Your active engagement has led to over 300 targeted improvements, rendering a more robust and reliable extension. This combined effort was crucial in our decision to transition from preview to general availability and to initiate official support for Visual Studio subscribers.
What is C# Dev Kit?
The C# Dev Kit leverages the core C# language services and delivers additional productivity value to developers. While these core productivity features are now generally available, additional experiences that support .NET MAUI and Unity are still in preview, leveraging the C# Dev Kit. These extensions continue to benefit from feedback and improving your development workflows for MAUI and Unity in VS Code.
What’s Next for C# Dev Kit
Today’s official launch is only the start as we will continue to listen to your feedback and work toward improved performance, reliability, and adding features to support your C# development in VS Code with updates to the extension on a monthly cadence. If you want to get the early bits, opt-in to the pre-release channel where we will insert fixes and previews of new features as they are developed.
Please share your feedback by reporting new issues via VS code or searching the existing enhancement and issues and give your ‘thumbs up’ or additional context to the issue to help us prioritize.
Learn More
If you would like to learn more about C# Dev Kit, you can catch some great sessions coming to Ignite and .NET Conf in November or explore our updated C# VS Code documentation and Get Started docs. Try out the new C# environment with C# Dev Kit today!
Wendy Breiding (SHE/HER) Senior Manager, Product Management
Follow
Posted in .NET .NET Core ASP.NET ASP.NET Core DebuggingTagged Csharp vscode
Read next
12 comments
Log in to join the discussion.
Sasa Krsmanovic
October 5, 2023 6:38 am
0
CONGRATS!
Can’t wait to see how our VS Code plugin integrates with it https://marketplace.visualstudio.com/items?itemName=unoplatform.vscode . Start the clock, we are on it
Marina Sundström
October 5, 2023 1:47 pm
0
Dev Kit has stopped working for me. Tried to reinstall it without luck.
I don’t have a build of RC 2 installed. Just RC 1.Starting Spawn .NET server... Starting Open a solution... Starting Open a solution with environment service... Starting Clear environment... Using preinstalled .NET runtime at "/usr/local/share/dotnet/dotnet" Using runtime installed in SDK. .NET server STDERR: Failed to load /usr/local/share/dotnet/host/fxr/8.0.0-rc.2.23418.14/libhostfxr.dylib, error: dlopen(/usr/local/share/dotnet/host/fxr/8.0.0-rc.2.23418.14/libhostfxr.dylib, 0x0001): tried: '/usr/local/share/dotnet/host/fxr/8.0.0-rc.2.23418.14/libhostfxr.dylib' (code signature in '/usr/local/share/dotnet/host/fxr/8.0.0-rc.2.23418.14/libhostfxr.dylib' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/share/dotnet/host/fxr/8.0.0-rc.2.23418.14/libhostfxr.dylib' (no such file), '/usr/local/share/dotnet/host/fxr/8.0.0-rc.2.23418.14/libhostfxr.dylib' (code signature in '/usr/local/share/dotnet/host/fxr/8.0.0-rc.2.23418.14/libhostfxr.dylib' not valid for use in process: mapping process and mapped file (non-platform) have different Team IDs) The library libhostfxr.dylib was found, but loading it from /usr/local/share/dotnet/host/fxr/8.0.0-rc.2.23418.14/libhostfxr.dylib failed - Installing .NET prerequisites might help resolve this problem. https://go.microsoft.com/fwlink/?linkid=2063366 .NET server exited with 130-
Marina, I am so sorry you are experiencing a problem working with C# Dev Kit. Can you please file an issue either through “Report Issue” in VS Code or through our GitHub repo so the team has information needed to investigate and resolve for you.
Lifeng Lu
October 5, 2023 7:28 pm 1
When you install an ad-hoc signed SDK to a MAC machine, MAC security layer will block it to be used by any signed application/process except a small sets added as development tool on the machine. For CDK, you need turn on a machine level setting on VS code, so it would run under a compatible mode to allow it to work with ad-hoc signed SDKs. It would change some behaviors, for example, always downloading a signed runtime instead of using the installed SDK to load some of its processes, so it would not run into security blocks. The compatible mode is therefor slower, and not necessary for majority users who install fully signed SDK only.
You can find the setting through vs code setting pages, and expand extension/C# Dev Kit/Working with test signed SDK.
You have to reload the workspace after changing the setting. (You also need ensure vs code is listed as development tool on the Mac through its security setting pages, if it is not yet there.)Marina Sundström
October 5, 2023 11:53 pm
1
Thank you, Lifeng. That solved my problem.
It never occurred to me that I had to enable something in the settings, plus do some stuff in Security settings.
I would have hoped that the extensions should perhaps have warned the user, or at least, give it a clear hint.
Lifeng Lu
October 6, 2023 12:23 pm 0
yes, we thought that would be a good idea too. But it was delayed due to other priority work. That security check also blocks the product code in various different places, based on scenarios, which made it more work to provide recommend when it happened.
Actually, there are more people using ad-hoc builds than I originally thought, certainly more than the inner SDK developer team, so providing a hint may be more valuable than first impression.
-
Michal Dobrodenka
October 6, 2023 1:49 am
0
Can I use to debug catalyst app (without MAUI) on mac?
David Taylor
October 6, 2023 5:00 am
0
Hi Wendy. I broke out an old Raspberry PI 4, and installed VS Code and .NET 7 today for my kids to play with, which worked perfectly.
Unfortunately I got an error message that Dev Kit and the base C# plugin does not run on that version of ARM, even though I think it is 64 bit. It would be great if Microsoft can also get Dev Kit working on the PI 4 or even just the PI 5 about to come out.
Eric Ison
October 6, 2023 9:43 am
0
Even though the processor is ARM64, by default the Raspberry Pi Imager will install the 32-bit OS, I’m still new to the whole Raspberry Pi thing though, so I could be wrong. But maybe try installing the 64bit OS?
Steve Tabler
October 6, 2023 7:14 am
0
Not trying to be a moron here, but what does it do? Does it let you write C# apps on Linux that run on Linux? Or does it run on Linux so you can write C# apps that will only run on Windows? Does it fully support Windows Forms on Linux yet?
Andrew Witte
October 6, 2023 12:11 pm
0
C# already lets you write apps for almost any platform.
This is a vscode IDE extension that makes writing C# apps a little easier.
However vscode makes C# feel like a second class citizen vs older IDEs and I feel like this is only further putting a bad taste in peoples mouths when it comes to C#.
Andrew Witte
October 6, 2023 12:31 pm
0
Its ok if its your only option.
Pros:
* Only free portable option now for Open-Source projects
* It existsCons:
* Building an IDE around HTLM/JS/TS was a huge mistake.
* Making users sign into MS accounts is a huge mistake.
* Most serious cross-platform dev is now going to be using Rider as VScode is a massive IDE regression from MonoDevelop.
* Long run this could actually do harm to C# as a language because it now feels like a alien to the IDE and a second class citizen.
* No way to open .sln files without opening folders first (again feels like C# is now a second class citizen)
* No NuGet management without using command line?
* No way to manage .csprojs in solution
* No way to unload .csprojs in solutionWhile its good this exists when everything else is going dry… I can’t but help think this is going to contribute to more negativity around C# as a lang.
VScode was never built to handle a lang like C# and it really shows IMO. The constant battle with .sln files relevancy needs to be further improved (or some equivalent needs to exist thats human readable idk). Also maybe vscode needs to let extensions have more control & allow adding file menu options among other things as well?
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK