Visual Studio 2017 Designer Support
I am using Unity and most of my development is inside Visual Studio. When I edit a XAML file I get warnings for the noesis namespace classes. Is there an easy way to remove these warnings and retain tab-completion?
Here are things I tried:
Any thoughts around how to fix this? Not really looking for suggestions on different editors besides VS.
Here are things I tried:
- Change the build type to 'none'.
Add a noesis namespace which points to the clr library.
Edit via a different program -- which defeats the purpose of having an IDE.

Any thoughts around how to fix this? Not really looking for suggestions on different editors besides VS.
-
-
sfernandez
Site Admin
- Posts: 2062
- Joined:
Re: Visual Studio 2017 Designer Support
This might happen if you use the Visual Studio project generated by Unity, right?
I suggest you follow the approach exposed in this tutorial https://www.noesisengine.com/docs/Gui.C ... unity.html, the idea is having a different project to edit xamls in Visual Studio Blend, so you can even see the preview before you play the scene in Unity.
Please let us know if you need help on setting up that.
I suggest you follow the approach exposed in this tutorial https://www.noesisengine.com/docs/Gui.C ... unity.html, the idea is having a different project to edit xamls in Visual Studio Blend, so you can even see the preview before you play the scene in Unity.
Please let us know if you need help on setting up that.
Re: Visual Studio 2017 Designer Support
Thank you for your helpful response!
Re: Visual Studio 2017 Designer Support
All our Unity samples follow that approach, they have the Blend project next to the /Assets folder.
Who is online
Users browsing this forum: No registered users and 0 guests