Building Nightly HandBrake GUI with VS 2017

HandBrake for Windows support
Forum rules
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
Post Reply
virgilfox
Posts: 6
Joined: Fri Jan 23, 2015 1:07 pm

Building Nightly HandBrake GUI with VS 2017

Post by virgilfox »

Description of problem or question:

Building the nightly HandBrake GUI in VS 2017 fails. (I have successfully built the nightly libhb.dll and the CLI utility as well as the GUI in the past, but the nightly GUI build is failing now.)


Steps to reproduce the problem (If Applicable):

I followed the Windows GUI build directions in the "HandBrake Latest" documentation. After setting "HandBrakeWPF" as the startup project, I select "Build Solution" and get the output listed in the log section below.


HandBrake version (e.g., 1.0.0):

nightly as of June 7, 2018.


Operating system and version (e.g., Ubuntu 16.04 LTS, macOS 10.13 High Sierra, Windows 10 Creators Update):

Windows 10 1803 64bit, Visual Studio Community 2017


HandBrake Activity Log ***required***

Visual Studio build output:

Code: Select all

1>------ Build started: Project: HandBrake.Interop, Configuration: Release x64 ------
2>------ Build started: Project: HandBrakeTools, Configuration: Release Any CPU ------
3>------ Build started: Project: HandBrakeAppX, Configuration: Release x64 ------
3>File not found - *.exe
3>0 File(s) copied
3>File not found - *.dll
3>0 File(s) copied
3>File not found - *.config
3>0 File(s) copied
3>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\AppxPackage\Microsoft.AppXPackage.Targets(1203,5): error MSB3819: Cannot find assembly "C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrakeAppX\win32\System.Windows.Interactivity.dll", which may contain managed resources that need to be included in this app package.  Please ensure that this assembly exists.
2>  HandBrakeTools -> C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrakeTools\bin\Release\HandBrakeTools.exe
3>Done building project "HandBrakeAppX.jsproj" -- FAILED.
1>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\Interop\HbLib\hb_image_s.cs(35,20,35,25): warning CS0649: Field 'image_plane.width' is never assigned to, and will always have its default value 0
1>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\Interop\HbLib\hb_image_s.cs(34,23,34,27): warning CS0649: Field 'image_plane.data' is never assigned to, and will always have its default value
1>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\Interop\HbLib\hb_image_s.cs(21,20,21,25): warning CS0649: Field 'hb_image_s.width' is never assigned to, and will always have its default value 0
1>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\Interop\HbLib\hb_image_s.cs(37,20,37,26): warning CS0649: Field 'image_plane.stride' is never assigned to, and will always have its default value 0
1>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\Interop\HbLib\hb_image_s.cs(26,30,26,35): warning CS0649: Field 'hb_image_s.plane' is never assigned to, and will always have its default value null
1>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\Interop\HbLib\hb_image_s.cs(23,23,23,27): warning CS0649: Field 'hb_image_s.data' is never assigned to, and will always have its default value
1>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\Interop\HbLib\hb_image_s.cs(20,20,20,26): warning CS0649: Field 'hb_image_s.format' is never assigned to, and will always have its default value 0
1>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\Interop\HbLib\hb_image_s.cs(36,20,36,26): warning CS0649: Field 'image_plane.height' is never assigned to, and will always have its default value 0
1>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\Interop\HbLib\hb_image_s.cs(22,20,22,26): warning CS0649: Field 'hb_image_s.height' is never assigned to, and will always have its default value 0
1>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\Interop\HbLib\hb_image_s.cs(39,20,39,24): warning CS0649: Field 'image_plane.size' is never assigned to, and will always have its default value 0
1>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\Interop\HbLib\hb_image_s.cs(38,20,38,33): warning CS0649: Field 'image_plane.height_stride' is never assigned to, and will always have its default value 0
1>  HandBrake.Interop -> C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrake.Interop\bin\Release\HandBrake.Interop.dll
4>------ Build started: Project: HandBrakeWPF, Configuration: Release x64 ------
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "GongSolutions.Wpf.DragDrop, Version=1.1.0.0, Culture=neutral, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
4>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Ookii.Dialogs.Wpf, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0c15020868fd6249, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
4>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrakeWPF\Views\AudioDefaultsView.xaml(110,46): error MC3072: The property 'DragDrop.DropHandler' does not exist in XML namespace 'clr-namespace:GongSolutions.Wpf.DragDrop;assembly=GongSolutions.Wpf.DragDrop'. Line 110 Position 46.
4>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrakeWPF\Views\Queue\Embedded.xaml(50,18): error MC3072: The property 'DragDrop.DropHandler' does not exist in XML namespace 'clr-namespace:GongSolutions.Wpf.DragDrop;assembly=GongSolutions.Wpf.DragDrop'. Line 50 Position 18.
4>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrakeWPF\Views\SubtitlesDefaultsView.xaml(113,46): error MC3072: The property 'DragDrop.DropHandler' does not exist in XML namespace 'clr-namespace:GongSolutions.Wpf.DragDrop;assembly=GongSolutions.Wpf.DragDrop'. Line 113 Position 46.
4>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrakeWPF\Views\AudioView.xaml(107,18): error MC3072: The property 'DragDrop.DropHandler' does not exist in XML namespace 'clr-namespace:GongSolutions.Wpf.DragDrop;assembly=GongSolutions.Wpf.DragDrop'. Line 107 Position 18.
4>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrakeWPF\Views\SubtitlesView.xaml(108,18): error MC3072: The property 'DragDrop.DropHandler' does not exist in XML namespace 'clr-namespace:GongSolutions.Wpf.DragDrop;assembly=GongSolutions.Wpf.DragDrop'. Line 108 Position 18.
4>C:\Users\DAVEE\Documents\dev\HandBrake\win\CS\HandBrakeWPF\Views\QueueView.xaml(173,18): error MC3072: The property 'DragDrop.DropHandler' does not exist in XML namespace 'clr-namespace:GongSolutions.Wpf.DragDrop;assembly=GongSolutions.Wpf.DragDrop'. Line 173 Position 18.
========== Build: 2 succeeded, 2 failed, 0 up-to-date, 0 skipped ==========

virgilfox
Posts: 6
Joined: Fri Jan 23, 2015 1:07 pm

Re: Building Nightly HandBrake GUI with VS 2017

Post by virgilfox »

Nobody building the Windows GUI these days?
User avatar
s55
HandBrake Team
Posts: 10350
Joined: Sun Dec 24, 2006 1:05 pm

Re: Building Nightly HandBrake GUI with VS 2017

Post by s55 »

Looks like VS didn't run a NuGet Restore before trying to build.

You can disable the AppX project, it's not needed. (It needs hb.dll as does the HandBrakeWPF project in the bin/* dir)
virgilfox
Posts: 6
Joined: Fri Jan 23, 2015 1:07 pm

Re: Building Nightly HandBrake GUI with VS 2017

Post by virgilfox »

s55 wrote: Mon Jun 11, 2018 5:42 pm Looks like VS didn't run a NuGet Restore before trying to build.

You can disable the AppX project, it's not needed. (It needs hb.dll as does the HandBrakeWPF project in the bin/* dir)
Thanks! The restore got things going again.
Post Reply