Bug Assembly-Csharp-Editor Reference issue.

Assembly-Csharp-Editor Reference issue.
Does anyone know how to fix it?

 

If I search in the scripting API then HexCoordinates is not found. https://docs.unity3d.com/ScriptReference/30_search.html?q=HexCoordinates
Therefore it seems logical it's not in the Assembly. What namespace is HexCoordinates in? What does the "show potential fixes" offer in VisualStudio?

 

HexCoordinates is a struct created under project root namespace.

I am learning how to build a Hex Map from this tutorial Hex Map 1 (catlikecoding.com). At part 4.1 <Coordinates in the Inspector>, I followed tutorial but got an error as stated above. I tried to add using MyProjectRoodNameSpace but apparently it doesn't recognize that namespace.

I have also checked several other similar posts. (Can't properly reference public classes from the Assembly-CSharp into Assembly-CSharp-Editor - Unity Forum) Seems like they got it solved but I don't know what it means by saying Assembly Reference and Definitions files and how to create them exactly.

 

You can try to recreated the project files for VisualStudio from Unity, it sometimes helps with these errors. It's under Preferences > External Tools > Regenerate project files

 

I tried. Not working. I still think that's some random reference bug since I can't reference any script in my editor project.

 

Then the only other thing I can think of would be a typo / compile error in the HexCoordinates class. You can try to make a new class and try to import that (just to test if it's a general issue or HexCoordinates specific).

 

Well, first of all, ignore everything that VisualStudio is telling you. Check the errors in Unity. That's the only place that matters. VS is not compiling your code, Unity is. Also when you check the console for errors, ALWAYS fix the top error first. The editor assembly is compiled after the normal runtime assembly has finished compiling. If there's any error in any runtime script the runtime assembly won't be compiled at all and can not be referenced by the editor assembly.

If you have no error inside Unity at all, the issue may be just the solution / csproj file. Either it's write protected or did not update for whatever reasons.