-
Thank you for this great program. I tried to compile the UVtool-2.13.1 with Visual stuido 2019. VS2019 can build the code, but it doesn't debug properly. With AvaloniaVS.vslx, I can't get to run designer to preview the WPF. It gave me "Invalid Markup" message in designer window and "[Error] UpdateXamlResult error". Because I am new to Avalonia and C#, I don't have any clue to solve this problem. Please let me know how to compile UVtools in VS2019. I would really appreciate your help. Sangjo |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 14 replies
-
The views are all binded to variables and due the not created instances while on preview mode it will trigger that markup/binding errors and because of that windows designs can't be previewed on Visual Studio designer. Think as it like: I can see latter if is possible to make it work with minimal effort... |
Beta Was this translation helpful? Give feedback.
-
Now I am working to compile UVtools-2.13.1 version with Visual Studio 2019 in Windows10. I succeed to build the UVtools, but debug doesn't work well. When I debug the code, the message "window was null" occurs in
"System.NullReferenceException: 'Object reference not set to an instance of an object.' window was null." What am I missing here? Please let me know how to solve this problem. Visual studio 2019, AvaloniaVS.vsix, Votive2019.vsix, wix311.exe, dotnet-sdk-5.0.300-win-x64.exe, libemgucv-windows-ipp-dldt-4.5.1.4349.exe are installed to compile the UVtools in my desktop. Thank you in advance. |
Beta Was this translation helpful? Give feedback.
The views are all binded to variables and due the not created instances while on preview mode it will trigger that markup/binding errors and because of that windows designs can't be previewed on Visual Studio designer. Think as it like:
null.getProperty
= Error!As i don't care about the the preview and blind code every window i don't include safe checks for the preview loads without errors, a check imply extra instructions which are never needed on app run. For example, every tool window requires a
SlicerFile
instance which on design time are NULL, so that's why it fails to show. It is possible to fix this but preview doesn't provide any big value since you can never use it for drag and …