Earlier quoted context omitted.
Why is BinaryFormatter insecure? Edit: Never mind, see https://docs.microsoft.com/en-us/dotnet/standard/serializati...
It's possible to use different formatters for H.Pipes. I will probably update the post to not mislead.
Named Pipes in .NET 6 with Tray Icon and Service
51–54 of 54 posts
Re: Named Pipes in .NET 6 with Tray Icon and Service
#52Just to clarify something at the start of the article... If you are using full Visual Studio to develop with .NET 6, you will need 2022. If not, (eg. VS Code), will work with the command line sdk.
Pretty sure there isn't anything you can't do in Jetbrains Rider EAP. Edit: would like to know why I'm being downvoted.
I've seen a lot of documentation (third party and Microsoft) that just start in on a "Visual Studio"-based solution while ignoring everything else, which kind of rubs me the wrong way.
Re: Named Pipes in .NET 6 with Tray Icon and Service
#53Earlier quoted context omitted.
It's possible to use different formatters for H.Pipes. I will probably update the post to not mislead.
I've recently done something close to this, and found Ceras[0] to be an excellent choice for the serialization layer. [0] https://github.com/rikimaru0345/Ceras
Re: Named Pipes in .NET 6 with Tray Icon and Service
#54Earlier quoted context omitted.
Pretty sure there isn't anything you can't do in Jetbrains Rider EAP. Edit: would like to know why I'm being downvoted.
Apologies - my comment was poorly worded and I think it caused confusion. The article sort of implied that Visual Studio was "The Way to Develop in .NET", while both you and I obviously know that's not true. I've seen a lot of documentation (third party and Microsoft) that just start in on a "Visual Studio"-based solution while ignoring everything else, which kind of rubs me the wrong way.
Yeah I know the feeling. I like to remind people there is a good development experience on linux also when using Rider. Sometimes feel like people are still stuck on “.net is windows only!”