System.Net.Sockets spookyness
Hello! :
I've been tasked with updating our web app backend to .net 6 and I am almost done. However, while it was working fine locally and on our Dev environment, I've hit a wall when trying to deploy in our QA environment. Here's what's happening :
- Running our app on our QA environment gives me an error I don't get on other environment
- OSes :
- Dev environment runs on Windows Server 2012 R2 ;
- QA runs on Windows Server 2016 ;
- Local is Windows 10 Pro
- When trying to connect to other processes, I get the following exception : System.PlatformNotSupportedException: 'Operation is not supported on this platform.'
- Exception is triggered by System.Net.Sockets.UnixDomainSocketEndPoint
- My research seems to indicate that Windows Server 2016 does not support UDS. But it isn't supported by Windows Server 2012 R2 either, where the build runs without any problem
I can't get try to run in debug on WS2012 R2, since VS 2022 isn't compatible with it. But I guess this is due to what it decides to try and call via the Kestrel Server, which only has port registration on Listen(int 32) if the config specifies IP and Port, and ListenAnyIP if the config has a port, but no specific IP. So, Listen UnixSocket(...) is never explicitly called.
Anyone faced something similar and know what could be happening here?
Thanks!
I've been tasked with updating our web app backend to .net 6 and I am almost done. However, while it was working fine locally and on our Dev environment, I've hit a wall when trying to deploy in our QA environment. Here's what's happening :
- Running our app on our QA environment gives me an error I don't get on other environment
- OSes :
- Dev environment runs on Windows Server 2012 R2 ;
- QA runs on Windows Server 2016 ;
- Local is Windows 10 Pro
- When trying to connect to other processes, I get the following exception : System.PlatformNotSupportedException: 'Operation is not supported on this platform.'
- Exception is triggered by System.Net.Sockets.UnixDomainSocketEndPoint
- My research seems to indicate that Windows Server 2016 does not support UDS. But it isn't supported by Windows Server 2012 R2 either, where the build runs without any problem
I can't get try to run in debug on WS2012 R2, since VS 2022 isn't compatible with it. But I guess this is due to what it decides to try and call via the Kestrel Server, which only has port registration on Listen(int 32) if the config specifies IP and Port, and ListenAnyIP if the config has a port, but no specific IP. So, Listen UnixSocket(...) is never explicitly called.
Anyone faced something similar and know what could be happening here?
Thanks!
