Hello…
Yesterday, I did extensive testing with incorporating the UNO Cross-Platform Tools and the Water IDE with C#\NET\WPF applications.
My hope was to use the Water IDE to bring my rather large development effort to the Linux Platform, were I could not only move away from the Windows OS, but do all my development under Linux.
All of my attempts, with the aid of the DeepSeek AI for research, with melding the UNO Platform and Water failed.
Even though I could see the UNO Platform assemblies referenced in the project solution, when attempting to compile the project, the compiler, using the EBuild system could not resolve these references.
It appears that the EBuild system was not referencing the NuGet Cache in order to resolve such references. And no matter how many tweaks I applied or modifications I made to the project configuration, nothing worked.
At first, I believed that the Ebuild system was simply ignoring the NuGet assembly cache on my system, and this is still possible, since the EBuild System sits outside from the MSBuild System, where the latter already knows to access referenced NuGet assemblies in a project.
However, reading through the Water Documentation again regarding NuGet, Gradle, and EBuild, I saw that I may have possibly missed something with my project configuration that would specifically tell the EBuild System to resolve the UNO assembly references within the UNO cache.
If someone could review this information I would greatly appreciate it since I would like to move to the Water IDE, but as long as I cannot get my WPF project some form of cross-platform compatibility with the XAML Markup System, this move will not be possible. Trying to convert WPF to GTK# would be an enormous endeavor, which I simply do not have the time for right now.
Thank you…
Steve Naidamast (Sr. Software Engineer)