# FSAC Runtime = netcore does not work with fsx #948

Closed
opened this issue Oct 20, 2018 · 13 comments

Projects
None yet

### isaacabraham commented Oct 20, 2018

 Switching to netcore for FSAC Runtime (as suggested by Ionide) does not work - I get no intellisense, no tooltips etc.. F# Language Service says stuff like the following: [19:55:49 ERROR] Cannot execute lint, File 'c:\Users\Isaac\Source\Repos\fsharp-demo\FSharpDemo\Scripts\foo.fsx' not parsed [19:55:49 ERROR] Cannot execute unusedOpens, File 'c:\Users\Isaac\Source\Repos\fsharp-demo\FSharpDemo\Scripts\foo.fsx' not parsed [19:55:49 ERROR] Cannot execute unusedDeclarations, File 'c:\Users\Isaac\Source\Repos\fsharp-demo\FSharpDemo\Scripts\foo.fsx' not parsed [19:55:49 ERROR] Cannot execute simplifiedNames, File 'c:\Users\Isaac\Source\Repos\fsharp-demo\FSharpDemo\Scripts\foo.fsx' not parsed  Anything I need to do e.g. specific version of netcore?
Member

### Krzysztof-Cieslak commented Oct 20, 2018

 Since I can see .fsx file - it's probably duplicate of #656. Please check, if it's working fine with any project, clearing cache / removing obj may be required

Closed

### melston commented Oct 23, 2018

 I am having the same problem. What is meant by "clearing cache"? I tried removing the obj directory of my projects but that had no impact.

### dougferg commented Oct 24, 2018

 I tried clearing the cache (by pressing CTRL + SHIFT + P and then typing F#: Clear Cache) in VSCode . I've experienced the problem with old/new projects on different computers as well as new single file fsx files. Clearing the cache didn't affect anything.

### dburriss commented Nov 11, 2018

 Ran into this with fsx files. I ended up uninstalling VS Code and deleting %userprofile%\AppData\Roaming\Code and %userprofile%\.vscode I was experiencing this with net and netcore. Clear cache didnt help. 2 things that happened around the time it stopped working. I was switching between .net and core in the workspace settings and I updated VS.

### da9l commented Nov 12, 2018

 Uninstalling vscode per @dburriss suggestion worked well for me now. I decided to stay on "FSharp.fsacRuntime": "net" tho. I'm guessing that this problem maybe is related with #938 and #949.