 |
This is not the intended behavior but it is part of the things we needed to change in the new version. So maybe we broke things. The syntax "<noesis:Dependency Source="Assets/User Interface/Controls/ProductMenuControl.xaml"/>" should work, I don't understand why File.Exists is failing. The file does exist, right? |
|
|
I assume this is 3.1 right? (this was originally marked as a 3.0.12 issue) |
 |
Could you open Unity C# project in Visual Studio, attach to Unity to put a breakpoint in XamlDependencies.cs, and check System.IO.Directory.GetCurrentDirectory() when debugger stops. I just did some tests with absolute paths (starting with "/Assets/...") and relative paths and both worked fine in my project. |
 |
I uncommented the lines in XamlDependencies.cs which performs the check and this time I received errors for three user controls instead of all referenced user controls. I can confirm the three user controls listed were not present and the errors shown are valid. Previously, I received errors for all user controls referenced. I removed the incorrect dependencies and upon reimport I observed a NullReferenceException from OnInitialized, which appears to be due to invalid state in my code which is referenced during XAML preview. I added if (!Application.isPlaying) return; to OnInitialized and observed no further errors. The current behavior looks bug free and correct. I am positive I received errors for all XAML dependencies initially, including the example cited above ("Assets/User Interface/Controls/ProductMenuControl.xaml") -- that one remains valid. This is Noesis 3.0.12. It is MBI, and so they are not using the newest version of Noesis, yet. I'll be upgrading Stellar Conquest to 3.1 soon, and this will be an opportunity for me to retest the initial upgrade/import process again. Environment.CurrentDirectory is correctly reported as the top-level directory of the Unity project, above .\Assets. I am OK, because it is working. |
|
|
Closing this for now. Please, reopen if necessary. |
- Anonymous
