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

Namespace not defined #414

Closed
ghost opened this issue Apr 19, 2017 · 1 comment
Closed

Namespace not defined #414

ghost opened this issue Apr 19, 2017 · 1 comment

Comments

@ghost
Copy link

ghost commented Apr 19, 2017

With only VS 2017 installed and only F# 4.1 installed.
System: Windows 10 1703
ionide: 2.25.9

It's unable to resolve namespace. Simple step to reproduce is just to create a expecto project from template in vs code.

Some log here:

System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Build.Utilities.v12.0, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.\r\nFile name: 'Microsoft.Build.Utilities.v12.0, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'\r\n   at Microsoft.FSharp.Compiler.SourceCodeServices.ProjectCrackerTool.ProjectCrackerTool.FSharpProjectFileInfo..ctor(String fsprojFileName, FSharpOption`1 properties, FSharpOption`1 enableLogging)\r\n   at Microsoft.FSharp.Compiler.SourceCodeServices.ProjectCrackerTool.ProjectCrackerTool.getOptions@387(Boolean enableLogging, FSharpList`1 properties, String file)\r\n   at Microsoft.FSharp.Compiler.SourceCodeServices.ProjectCrackerTool.ProjectCrackerTool.getOptions(String file, Boolean enableLogging, FSharpList`1 properties)

Seems like FSAC looking for msbuild12?

@Krzysztof-Cieslak
Copy link
Member

We don't yet support VS2017 only installation, requirements for the plugin are listed in readme.

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

No branches or pull requests

1 participant