Skip to content
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

Closed
rneatherway opened this issue Aug 2, 2015 · 16 comments
Closed
Labels
Milestone

Comments

@rneatherway
Copy link
Contributor

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.

@rneatherway rneatherway added the bug label Aug 2, 2015
@7sharp9
Copy link
Contributor

7sharp9 commented Aug 2, 2015

Could you keep me posted so I can get a potential fix into XS? Better yet a PR :-)

@rneatherway
Copy link
Contributor Author

Yes, I'm waiting to see how @dungpa handles it, then I'll see if I can push it into FCS.

@dungpa
Copy link

dungpa commented Aug 2, 2015

Here is the logic I used dungpa/PowerTools@16dc45e It uses registry readers already available in CompilerLocationUtils.fs.

@7sharp9
Copy link
Contributor

7sharp9 commented Aug 2, 2015

So in mono how would that work, the registry is not used.

On 2 Aug 2015, at 14:09, Anh-Dung Phan notifications@github.com wrote:

Here is the logic I used dungpa/PowerTools@16dc45e It use registry readers already available in CompilerLocationUtils.fs.


Reply to this email directly or view it on GitHub.

@rneatherway
Copy link
Contributor Author

For VFPT mono isn't important, we'll need a different approach.

@rneatherway
Copy link
Contributor Author

Easiest resolution for this will be to just ship FSharp.Core 4.4

@7sharp9
Copy link
Contributor

7sharp9 commented Aug 4, 2015

Note: most of CompilerLocationUtils.fs is now depreciated.

@rneatherway
Copy link
Contributor Author

Good to know, because I have a wanted to delete it for ages!

@rneatherway rneatherway modified the milestones: 0.22, 0.23 Aug 7, 2015
@rneatherway
Copy link
Contributor Author

@dungpa: I was just looking at this to see how you actually detect the Visual Studio version and it looks hardcoded to VS2013 for scripts. Does that get overridden somewhere that I'm not seeing?

@rneatherway
Copy link
Contributor Author

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

@dungpa
Copy link

dungpa commented Aug 10, 2015

@rneatherway
Copy link
Contributor Author

Ah right, of course VS will tell you! Thanks.

@rneatherway
Copy link
Contributor Author

VS2012:

fsc.exe found at 'C:\Program Files (x86)\Microsoft SDKs\F#\3.1\Framework\v4.0\fsc.exe'
FSharp.Core found at 'C:\Program Files (x86)\Reference Assemblies\Microsoft\FSharp.NETFramework\v4.0\4.3.1.0\FSharp.Core.dll'
msbuild.exe found at 'C:\Program Files (x86)\MSBuild\12.0\Bin\MSBuild.exe'

VS2015:

fsc.exe found at 'C:\Program Files (x86)\Microsoft SDKs\F#\4.0\Framework\v4.0\fsc.exe'
FSharp.Core found at 'C:\Program Files (x86)\Reference Assemblies\Microsoft\FSharp.NETFramework\v4.0\4.4.0.0\FSharp.Core.dll'
msbuild.exe found at 'C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe'

@rneatherway
Copy link
Contributor Author

(for reference)

@rneatherway
Copy link
Contributor Author

Fixed by #59

@monkieboy
Copy link

@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?

screen shot 2015-12-01 at 20 00 41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

4 participants