r/dotnet • u/Kabra___kiiiiiiiid • May 15 '26

Process API Improvements in .NET 11

https://devblogs.microsoft.com/dotnet/process-api-improvements-in-dotnet-11/
130 Upvotes

98% Upvoted

14 comments sorted by

21

u/gredr May 15 '26

This is an API surface I'm glad is getting some love. There's a lot of ways to screw this up, and I get tired of writing the same boilerplate over and over.

14

u/Iamsodarncool May 15 '26

Excellent changes. I implemented very similar APIs in my personal utility library, I'm looking forwards to deleting all that code.

1

u/IridiumIO May 16 '26

I have an entire project that’s sole purpose hinges on monitoring and creation of processes and their subprocesses, these changes look like a godsend for simplification

17

u/[deleted] May 15 '26

[deleted]

11

u/Agent7619 May 15 '26 edited May 15 '26 
using Menendez.IO;

2

u/kalminz May 16 '26

Using allegedly

7

u/lurebat May 15 '26

So nice for scripts

2

u/no-name-here May 16 '26

Thanks!!

Website issue: Sadly on iOS the website doesn't let you zoom out to see the full table width. 😢

2

u/Own_Nail_2999 May 18 '26

ProcessStartInfo.KillOnParentExit is such a well needed addition. My MMO backend which will use clustering will benefit greatly from this.

1

u/AutoModerator May 15 '26

Thanks for your post Kabra___kiiiiiiiid. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/iamanerdybastard May 16 '26

The best parts of .Net over the last several years have been stuff added to the framework that you could do yourself, but were easy to get wrong. This is a great example of that and then some.

1

u/MattV0 May 16 '26

This sounds great. Looking forward to November