-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add info on FSharp.Core and type providers #22
Comments
cc @ovatsus |
To be honest, at this point I don't event really know what works best in terms of FSharp.Core and type providers. For the designtime assembly, whatever FSharp.Core you reference doesn't matter, because the version already loaded by the compiler will override it. So if you are using FSharp.Core 4.3.0.0 and the consumer of the TP library is using VS2013, or if you're using FSharp.Core 4.3.1.0.0 and the consumer of the TP library is using VS2015, everything is already messed up if you use F# types on the interface with the runtime library (like option types or lists), you will be referencing both and have type mismatches. Sometimes assembly redirects fix this, sometimes they don't, I haven't really understood on what circumstances they help or not, or why. |
BTW, the idea of having a separate tool that would do reference fix ups I mentioned yesterday won't work, as that would have to be done for all consumers of the TP library, not for the TP library itself :/ |
Another thing I just remembered, is that while references to FSharp.Core 4.3.0.0 don't happily convert to FSharp.Core 4.3.1.0 references and vice versa, that works fine between FSharp.Core 2.3.5.0 and FSharp.Core 2.3.5.1, I think they have some kind of IsRetargetable property on their strong name, don't quite remember the details |
We should add info on FSharp.Core and type providers here:
or as a separate post
The text was updated successfully, but these errors were encountered: