r7-labs / R7.Webmate

Desktop productivity toolbox
GNU General Public License v3.0
1 stars 1 forks source link

Backend assemblies not copied to build output on Windows #30

Open Viklor opened 4 years ago

Viklor commented 4 years ago

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 commented 4 years ago

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

roman-yagodin commented 4 years ago
Viklor commented 4 years ago

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: image

Viklor commented 4 years ago

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 commented 4 years ago

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

roman-yagodin commented 4 years ago

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 commented 4 years ago

The https://github.com/roman-yagodin/R7.Webmate/commit/b8ad9d054e7db236d0ee5e99983b3a985b11178c should probably fix the issue. @Viklor could you test this?