-
Notifications
You must be signed in to change notification settings - Fork 149
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
Script checker options need to inject best version of FSharp.Core found #54
Comments
Could you keep me posted so I can get a potential fix into XS? Better yet a PR :-) |
Yes, I'm waiting to see how @dungpa handles it, then I'll see if I can push it into FCS. |
Here is the logic I used dungpa/PowerTools@16dc45e It uses registry readers already available in |
So in mono how would that work, the registry is not used.
|
For VFPT mono isn't important, we'll need a different approach. |
Easiest resolution for this will be to just ship FSharp.Core 4.4 |
Note: most of |
Good to know, because I have a wanted to delete it for ages! |
Just a note that upgrading to FSharp.Core 4.4.0.0 did not help. FCS always returns a reference of "FSharp.Core.dll" on Mono: https://github.com/dsyme/FSharp.Compiler.Service/blob/c5a64b00bdd645e7505dea6879673615a05df3ae/src/fsharp/build.fs#L1560 |
@rneatherway That part is used in unit testing only. We pass the Visual Studio version at https://github.com/dungpa/PowerTools/blob/dfbd8cc1c02264db883b358b10c25e97c2b84e1f/src/FSharpVSPowerTools.Logic/ProjectFactory.fs#L161-L162. |
Ah right, of course VS will tell you! Thanks. |
VS2012:
VS2015:
|
(for reference) |
Fixed by #59 |
@7sharp9 @rneatherway I know this is closed but I am experiencing the same thing with Xamarin Studio. Is the fix out yet? Can I do anything to fix this myself? |
See fsharp/fsharp-compiler-docs#384
Related to #42, for supporting VS2015 and MSBuild > 12.
The script checker options will default to the version of FSharp.Core used by FSAC, which is FSharp.Core 4.3.0.0. So this is already a minor issue w.r.t. F# 3.1/ FSharp.Core 4.3.1.0.
The text was updated successfully, but these errors were encountered: