Backend assemblies not copied to build output on Windows

[Viklor]

It is better to use Visual Studio Code than Visual Studio to work with the project, because in Visual Studio the project is compiled but cannot run.

Для работы с проектом лучше использовать Visual Studio Code чем Visual Studio, так как в Visual Studio проект компилируется, но не может запуститься.

[roman-yagodin]

I don't know, which is better...

• Which Visual Studio version/edition you referring to?
• Does it produces the .exe file in the build output directory after build?
• If so, can you run the .exe without issues or not (e.g. some .dlls are missing)?

[roman-yagodin]

• Have you tried Visual Studio Code to build the project, or the statement "it is better to use Visual Studio Code..." is just an assumption?
• Please provide error logs/screenshots here, if any.

[Viklor]

I used Visual Studio 2019.
The fact that Visual Studio Code is better than Visual Studio is just my guess, since I don't know how to use Visual Studio Code yet.
When launching R7.Webmate.Xwt in Visual Studio, these errors appear:

[Viklor]

When the R7.Webmate.Xwt.exe file was launched, nothing happened. This problem was solved when I moved the Xwt.WPF.dll file from the "packages" folder to the directory with R7.Webmate.Xwt.exe, and it started.

При запуске R7.Webmate.Xwt.ехе файла ничего не происходило. Эта проблема решилась, когда я из папки "packages" переместил файл Xwt.WPF.dll в директорию с R7.Webmate.Xwt.ехе, и он запустился.

[Viklor]

After solving the problem with the missing .dll file, the project can be launched through Visual Studio.

[roman-yagodin]

I see.

It looks like msbuild cannot properly invoke the CopyDependentAssemblies.ps1 script on Windows. So we need more cross-platform way to do that.

Could you provide raw build output from the VS?

[roman-yagodin]

The b8ad9d0 should probably fix the issue. @Viklor could you test this?