You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the application uses controls provided by the Xceed WPF Toolkit, the project holds a reference to the "Xceed.WPF.AvalonDock"-assembly. While compiling the project this assembly generates some language-related folders in the output-directory.
While this is not necessarily a big issue, I still do not like it and am not sure if the reference is really needed. But simply removing the reference might break the NuGet-reference.
The text was updated successfully, but these errors were encountered:
I'm seeing these language folders copying to the output directory as well. It's more annoying than anything, but I would like to find a way to stop it from happening. It complicates the deployment for our devops.
Since the application uses controls provided by the Xceed WPF Toolkit, the project holds a reference to the "Xceed.WPF.AvalonDock"-assembly. While compiling the project this assembly generates some language-related folders in the output-directory.
While this is not necessarily a big issue, I still do not like it and am not sure if the reference is really needed. But simply removing the reference might break the NuGet-reference.
The text was updated successfully, but these errors were encountered: