You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.
I asked a little while ago on stackoverflow about deploying an application that has a dependency on fsharp.core to a remote machine where the remote machine doesn't have the fsharp redistributable installed.
As far as I am aware, if I have signed assemblies, any assembly that then references that must also be signed. This reduces the utility of creating core libraries in F#, and makes it (more) difficult to deploy any application that depends on it.
Is it therefore worthwhile to create an FSharp.Core.Unsigned nuget package?
The text was updated successfully, but these errors were encountered:
Hi @khanage , Just deploy the signed FSharp.Core as one of the binaries of your application. Your other assemblies don't need to be signed, and nothing needs to be in the GAC.
Thanks @dsyme, I guess this wasn't all that complicated in the end. I added a reference to the FSharp.Core.Microsoft.Signed package in my library, and that came along for the ride.
Looks like the problem was just with a delay signed version of the assembly that I picked up from nuget.
I asked a little while ago on stackoverflow about deploying an application that has a dependency on fsharp.core to a remote machine where the remote machine doesn't have the fsharp redistributable installed.
As far as I am aware, if I have signed assemblies, any assembly that then references that must also be signed. This reduces the utility of creating core libraries in F#, and makes it (more) difficult to deploy any application that depends on it.
Is it therefore worthwhile to create an FSharp.Core.Unsigned nuget package?
The text was updated successfully, but these errors were encountered: