LinqPadless 1.1 - SSL certificate error about linqpadless HOT 10 CLOSED

I think this might be related to nuget.org permanently removing support for TLS 1.0 and 1.1.

Is it possible to patch it and release an update?

I'd be happy to take a PR and make a release if you can help with spotting the problem and then fixing and testing it (assuming it's urgent to you).

from linqpadless.

Something else to consider that may not require any code changes:

• Transport Layer Security (TLS) best practices with the .NET Framework, specifically section "For .NET Framework 3.5 - 4.5.2 and not WCF".

from linqpadless.

Not very urgent, I hacked around with current version to make it work for now. But I did made a simple PR that fixes this particular issue and enforces TSL 1.2.

from linqpadless.

Not very urgent, I hacked around with current version to make it work for now. But I did made a simple PR that fixes this particular issue and enforces TSL 1.2.

Thanks, but the build has failed and I am afraid I don't have much time to investigate.

Did you checkout the other workaround mentioned in the links I shared? Most of the those don't seems to need any code changes.

from linqpadless.

Thanks, but the build has failed and I am afraid I don't have much time to investigate.

Nuget packages were not restored. I'm not familiar with appveyor at all, so I don't know why. Project is built without errors locally in Debug and Release configurations.

Did you checkout the other workaround mentioned in the links I shared? Most of the those don't seems to need any code changes.

Correct. But the app is available to download in nuget and scoop https://github.com/lukesampson/scoop-extras/blob/a8bcb1b43b0230a9348a422017be31fe625cea70/bucket/linqpadless.json, but TLS issue makes it completely broken out of the box.

I wanted to fix it for everybody, not just me. It's still useful tool, even though it's technically outdated with release of new LINQPad (although v5 is still supported) and .NET. I understand that you are busy and may not have time to deal with this, but without access to build infrastructure I'm unable to help any further. Feel free to close the issue and pr.

from linqpadless.

Closed via a2e6352 that is the merge of PR #50.

from linqpadless.

The fix is now available in release 1.2.

from linqpadless.

This is amazing, thank you!

from linqpadless.

I'm really sorry, now I feel even worse. It still doesn't work on clean install. Because you moved setting SecurityProtocol down next to downloading nuget references, it will be unable to download csc from Nuget when running lpless script.linq -t exe...

from linqpadless.

Because you moved setting SecurityProtocol down next to downloading nuget references, it will be unable to download csc from Nuget when running lpless script.linq -t exe...

That's too bad. I guess what happened here was that I always tested against a LINQPad query file that referenced a NuGet package and so the TLS was always upgraded by the time it got to the compilation step and which downloaded nuget.exe and the compiler.

from linqpadless.