reference assemblies for framework .net not found
Opened this issue · 2 comments
I have been trying for a long time now and I cannot get intellisense to work, and I figured maybe you'd like to know this is a problem so you can help me and others to identify and hopefully fix the issue.
When I open vs code in any way (double click file, Assets->open c# project in code, Assets->open c# project, or even actually just opening the vs code application) after 6 seconds, a little pop-up box appears that looks like this:
When I click "Show output" I get a bunch of output in a console.
It looks like the problem is that I'm missing some sort of assembly or something. I'm not exactly sure what it means, but I have tried installing a bunch of stuff to try to fix it.
I have tried, all to no avail:
- Assets -> Reimport all
- Assets -> Open c# project
- Assets -> open c# project in code
- checking / unchecking "enable integration" in the vscode preferences pane (there were no errors in the console)
- installing .net core sdk. Not sure if I should have, but I wanted to see if that fixed it.
- deleting .sln file and .csproj files to let unity regenerate them
One thing to note is I don't know if this documentation is out of date or if mine is wrong, but my unity (2017.3) doesn't generate a -csharp.sln file.
If you can help me figure out a fix for this, and add a check in the preferences pane to auto-fix it, that would be magnificent and I'm sure you would help other people with the same problem. There is at least one other dude on reddit with the same issue as me. Thanks!
update: i finally figured it out, I had to install mono. I don't know much about it, but it was really hard to figure out that that's what I needed, so if there is a way you could check to see if mono is installed and at least put up a warning in the vscode preferences pane if it's not installed, that would be really helpful.
oh also I want to mention, you may also need to install .net sdk. the post that mentioned mono also mentions that, but I had already installed it, so I'm not 100% sure what error would occur with mono but without the .net sdk.