Unity / Visual Studio Unexpected Behaviours

I have one issue, or two issues, depending on perspective. First, WebGL isn't building and playing Vimeo videos from the Vimeo SDK in 2017.3, but some Vimeo SDK users are saying that it just doesn't work in that version, which I believe is the case.

The main thing now, while upgrading a project in working order from 2017.3 to any newer version, it loses reference to the Vimeo namespace from the Vimeo SDK. When adding the reference back in inside Visual Studio, it causes all the "namespace not found" errors to go away, and it builds. When inside Unity, the "namespace not found" errors persist. If I save the scene, close, and reopen Unity, the errors come back inside Visual Studio automatically - it dereferenced the Vimeo namespace again, despite the cs files and csproj being in the same place.

Is there a solution to this? I was not expecting this kind of behaviour.

 

Can anyone tell me if this is a bug or not? I am not sure if I should file a bug report.

 

I ended up solving the issue.

I had everything inside /Assets/Scripts/Vimeo/Scripts, and it did not work when I moved the scripts folder up one level into into /Assets/Scripts/Scripts, nor when I reimported or renamed the folder to /Assets/Scripts/ASDF. On a whim I moved all of the files inside /Assets/Scripts/Scripts up a level right into /Assets/Scripts, which although makes the folder very messy as all the Vimeo SDK files and scripts are strewn about in there, Unity is now able to find all the namespaces.

Also note that Visual Studio was able to find the files without issue and could even "Clean Solution" and "Build Solution" without any failures at all points here, it was just that Unity was never able to build without being able to find the namespaces until I moved everything up.

 

Edit > Preference > External Tools.

Pick Visual studio tick all packages (Embedded, local,registry... ) and regenerate project files. Now double click any script and vs should work with all intellisense and libs.

 

really helpful, thanks

 

THANK YOU!!!!!!!!!!!!!

 

Just want to add that
In another situation where Unity works fine but VS cannot find the namespace (e.g. in another imported package from unity asset store), trying lucernagame's solution (moving the folder which was imported at the root directory automatically, to the Assets/Scripts/ directory, will solve the issue.
Note this is not the same problem (Unity not working vs. VS not working), but the fix is the same.