Resolved 2019.3.12f1 visual studio 2019 problem

preferences->external tools->generate .csproj files for with all checkbox checked but in visual studio 2019 can't use jump to definition in many code

 

I affirm. In 2019.3.12 Visual Studio does not see assembly definition. There is no this problem in 2019.3.11

 

Just updated my project to 2019.3.12f1 from 2019.3.11f1, many namespaces can no longer be found (SimpleJSON, MapBox, etc)

 

Same here guys! Someone did a boo-boo on this update.

 

Apparently it's from the assembly definition files. Visual Studio is not getting correctly configured by Unity when having asmdef files in the project which generates multiple C# projects...for some reason...also noticed that the project properties window inside VS doesn't open as a side-effect of all this.
But a project that generates only one C# project works and compiles correctly in VS.

 

as a quick workaround, VS Code works fine.

 

Thanks!
Yeah well for some teams changing the IDE for the entire team is not a viable solution at the moment.
Unity made a big mistake with this release. Someone got drunk or something because it's a pretty obvious and major bug.

 

Same here. Staying with 11f1 till this is fixed is likely a better workaround than switching editors for most people.

 

Well, I found the underlying reason. Unity generates main Assembly-CSharp.csproj file incorrectly.

Here is the temporary fix for those interested:

• From VS Tools/Options/Tools for Unity/Miscellaneous set "Access to project properties" to True.
• Restart VS.
• Remove the allegedly missing reference(s) from the Solution Explorer/References treeview and add them again. You can find the reference DLLs inside yourprojectfolder\Library\ScriptAssemblies\xxx.dll

But still it's a temporary fix. Adding new scripts to your project triggers regenerating csproj files and broke it again. It's a very nasty bug.

 

Yep, found that also.
Reported bug to Unity. Pretty major bug to leave out and about.

 

Glad I'm not the only one, although I'm not glad I wasted an hour on this

I was updated to the vscode 1.2 package along with the update, but this package doesn't seem to be the culprit, as 2019.3.11 with vscode 1.2 seems to work fine

 

This worked for me.

But I confirm there is a big problem, my scripts in Assembly-CSharp-Editor project don't see namespaces from the Assembly-CSharp project in visual studio, I get many intellisense errors. I just tested in Unity 2019.3.11 everything work fine.

 

Looks like this has already been noted, but I was able to revert back to 3.11f without any issues. 3.12f is definitely missing a connection between the assembly references of quite a few namespaces (Including Pun2 which is where I ran into issues). My game still operated without issue, but my code looked like I had a million errors.

 

Same issue here. Going back to 2019.3.11
This is really bad.

 

Were their QA on vacation ? How can they missed that ?

 

Same with me!

 

Lost a whole morning without writing a line of code because of this.... This is terrible.... Awful work from Unity.

 

S*** happens.
There is the official guideline to always backup your projects before upgrading to a new Unity version. This is advisable for any engine / tech out there. There will always be a factor of human error.
I personally restored back the project to using 2019.3.11f1.

 

Sure, I can relate to that, we have VCS on all our projects but lets not forget we're not talking about alpha or beta release. This is a feature release.

 

Anyone got a link to a formal bug report on this?

 

I have the same issue with Visual Studio 2019, but I found that everything works fine in Visual Studio Code... Anyone got a link to a bug report?

 

Damn... just wasted whole day trying to figure this out.. Ha..................................................................................

Anyone with bug report? Link? Anyone from Unity?

 

We've also stumbled on that issue. Not sure how this could slip through the cracks.

 

I have actually tried to down verson to 1.1.4 but that did not helped..

I have even uninstalled VS 2017 and installed VS 2019 , but also not helped.

 

[QUOTE="The regression is caused by an invalid ReferenceOutputAssembly key set to false for ProjectRefence in the csproj files. By removing this field it will resolve the issue correctly. Unfortunately any asset changes will result in this getting overwritten again.[/QUOTE]

Where can the relevant csproj files be found so I can hack that in?

 

I also have a bug report that has made it to the issue tracker here: https://issuetracker.unity3d.com/is...ng-assembly-references-when-building-solution

 

my god, same problem and waste some hour, we should downgraded to 2019.3.11.

 

Same probleme for me. i loose 2 days before finding this thread. i will try to downgrade unity editor to 2019.3.11f.

 

I'm also having library linking issues with unity 2019.3.12. It only happens in Visual Studio, unity compiles properly.

I'm downgrading to 2019.3.11

 

Found this thread after discovering that my PUN2 VS project was broken after upgrading to 2019.3.12f1. (Should've learned by now never to upgrade mid-project. Sigh....)

 

Same issue happened to me when I just moved to another device, so I kept installing and uninstalling stuff thinking that it is somehow related to setup. That's until I went back to the original device and saw that the same problem exists there too. Wasted more than half a day on this.

It would be really beneficial if these issues were noted under Known Issues of the new version.

 

Nice, back in business

 

Thanks, I can attach the debugger again now.

 

Yep. Thanks!
Installed, tested and everything seems to be working fine and then some.

 

Unfortunately 2019.3.13f1 does not fix this issue for me. 11f1 works fine. Is there something else I might be missing?

 

I'm also having problems with this in 2019.3.14f1. I was getting namespace errors until I deleted the assembly definition file I was trying to set up for unit testing.

 

I have problem that go to definition it go to meta data file in version 2019.3.15.
I want to ask is this the same problem?

 

This issue reappeared for me in 2019.4.5f1





If I manually select the reference in the list and then look into the property tab, then references gets updated for the current project.

Example :



Then I click on tab



and it resolves



Very strange behaviour.

 

I am not sure if it is just me, but when I attach debugger to Unity and then start playing, it disconnects and I have to reattach it again. Anyone has the same problem? Debug mode is on to start with.