search

dotnet / fsharp

The F# compiler, F# core library, F# language service, and F# tooling integration for Visual Studio
https://dotnet.microsoft.com/languages/fsharp
MIT License
3.83k stars 773 forks source link

Impossible viable fork #17183

Closed Adahel closed 1 month ago

Adahel commented 1 month ago

Is your feature request related to a problem? Please describe.

I'm going to write a project that needs to use .NET Framework 4, which has to be 100% strong name and that needs the features of at least version 4.7 of F#. I was able to make a working fork of the latest FSharp.Core, but I can't use any closed third-party libraries, because Microsoft pseudo opened F#, but didn't open MSFT.snk like they opened Open.snk for other .NET projects. I also can't sign with my own SNK and redirect public key token from a third-party assembly because this function never existed and my goal is to backport. Late signature and public signature cannot be tolerated in my project.

My issue is simple, I can modify many strongly named libraries with Open.snk in .Net Core, but why can't I modify F#?

Describe the solution you'd like

The solution that Microsoft provides.

Describe alternatives you've considered

Factor out the prime number of MSFT.snk which is currently RSA SHA-1, using the cado-nfs program, to make F# truly open source. Since my goal is to backport any future changes to RSA SHA-2, this is irrelevant to me.

Additional context

Conversation on Microsoft Copilot: https://sl.bing.net/he65gwPYzfM

baronfel commented 1 month ago

Please extract an actual question. Your chat session link seems to say that you can't strong name sign the binaries, but it's incredibly silly to have to read a whole conversation to extract a question that you could just have easily formulated.

vzarytovskii commented 1 month ago

Please reopen with specific question.