Visual Studio 2019 Wont Compile After Unity 2019.3.12f1 update
I just updated my project to 2019.3.12f1 and I use VS 2019 Community. I am having issues with VS locating third-party DLLs imported from the store. Unity runs fine, but VS will not compile after this update.
Severity Code Description Project File Line Suppression State Error CS0246 The type or namespace name 'MMInformationAttribute' could not be found (are you missing a using directive or an assembly reference?
I am getting the same error with every project DLL.
I am running the latest version of VS2019 Community (as of today). I have Unity Package Visual Studio Code Editor 1.2.0 loaded. All packages are up to date.
Any idea what happened?
I am having the same issue but with VS 2017 Community. I updated to 2019.3.12f1 and VS will no longer compile the project due to missing assemblies. Unity compiles fine. 2019.3.11f1 did not have this issue. I notice Visual Studio Code Editor package went from 1.1.4 to 1.2.0. Reverting to 1.1.4 did not fix the issue.
Reverting to 2019.3.11f1 dodges the problem. That's what I'm doing for the moment.
I have encountered a similar problem and am troubled. Please take immediate action.
Answer by Jinja · May 08, 2020 at 06:23 PM
2019.3.13f1 does not have this issue for me, so you can now skip 2019.3.12f1, or stay on 2019.3.11f1. Yay!
Answer by chadfranklin47 · May 02, 2020 at 08:50 PM
Same here. I tried this: https://answers.unity.com/questions/1697513/vs-code-does-not-find-some-classes-cs0246cs0103.html and it didn't help. The only thing that's worked was downgrading to 2019.3.11. I didn't have this issue with an earlier version of 2019.3 so I believe downgrading to that should work too, but I forget exactly which version I had, probably 2019.3.0.
Please update if you find a solution.
For now though, downgrading to 2019.3.11 seems to be the best option.
https://answers.unity.com/questions/1725203/visual-studio-cant-reference-to-firstpass-assembly.html
Answer by IgnitedGames · May 09, 2020 at 03:08 AM
This seems to be a common problem, probably a problem with 3.12f1, I'd skip it if I were you and use the next version.
Actually, I've figured out that I was using 3.12f1 too. What you want to do is open a project/solution in visual studio and then open the .snl file in your unity project.
Your answer
Follow this Question
Related Questions
I am getting a CS1504 error in Unity,I am getting a CS1504 error 0 Answers
Bizarre compile errors in Unity while Visual Studio will build project successfully 0 Answers
VS Code showing errors in Editor scripts while referencing another class 1 Answer
Unable to load project - specified pathname not found compilation error 0 Answers
UWP build crashes with "Windows.Gaming.Input.dll: Access denied" - what does it mean? 0 Answers