Closed Schafwolle closed 3 years ago
You don't need to build the entire solution to work on Vocup 2.0. The projects Vocup
and Vocup.Packaging
contain the code of Vocup 1.X. I kept them there because that's more convenient than changing branches all the time. You can just build an run Vocup.Windows
which references Vocup.Avalonia
and Vocup.Core
where all the new code is located.
However, everyone should be able to build and debug the current version, too. I haven't been using a German localization of Visual Studio anymore for many years now but I'm not surprised to see more errors with Windows Forms key bindings. Maybe I should add a notice for that to the README.
To resolve the second error just remove the section <PackageCertificateThumbprint>
from Vocup.Packaging.wapproj
. This certificate is only required for Microsoft Store submission but I was tired of creating new certificates for every release so just committed that line 😅
Building only "Vocup.Windows" works.
I normally use English localization for my development tools but only German was installed. So I first tried it with German.
Hy I tried to build the current avalonia branch. I have installed Visual Studio 2019 and opened the solution checked in. Then I tried to build the debug version of the entire solution. The build failes with:
After that I tried to change the language to english. Now the following error occure:
I hope that this not a stupid mistake on my side. I know how to program in C# but when it comes to GUIs and XAML, I am lost.