1

I'm trying to update some of our software to .Net 4.6.2 for TLS1.2 compliance (eWAY for example). When I run the application standalone it connects fine, but when I debug it via Visual Studio 2015 I get the error indicating I'm not using the correct TLS version (and hence .Net version).

I have ReSharper installed which included dotPeek, so I peeked and see that vshost is still using the 4.5 framework:
framework version comparison

I "cleaned" the solution, and forcibly deleted everything from the output directory (had to shut down VS to delete the .vshost.exe file). Still the same behaviour.

Have I missed a setting somewhere? I don't like the fact that when I debug I'm getting different behaviour to when I release the application.

Ian
  • 1,475
  • 2
  • 15
  • 31
  • Just disable it: Project > Properties > Debug tab > untick the "Enable the Visual Studio hosting process". Nothing lost, it was removed completely in VS2017. – Hans Passant Aug 07 '17 at 09:50
  • @HansPassant I could, but ["The hosting process is a feature in Visual Studio that improves debugging performance, enables partial trust debugging, and enables design time expression evaluation."](https://learn.microsoft.com/en-us/visualstudio/ide/hosting-process-vshost-exe) – Ian Aug 07 '17 at 23:45
  • 1
    So you have no idea what any of this means. Then how do you know you need it? You don't. – Hans Passant Aug 08 '17 at 22:29
  • @HansPassant Hah, good call. For the most part true. But I understand it makes debugging launch faster. Additionally there must be a way to debug _the same code_ that I'm going to deploy! It's a matter of principle. At this point I don't need to debug it any further, but I'd still like to know why the debugger doesn't behave correctly. – Ian Aug 08 '17 at 22:33
  • And are there any other instances where the debugger doesn't accurately reflect deployed code. I've lost trust. – Ian Aug 08 '17 at 23:32

0 Answers0