Updated DesignTools project's output path

[brianlagunas]

Description of Change

Modified the build output path of the DesignTools projects from the old net45 to net462 due to the recent framework upgrades.

Bugs Fixed

• Related to work done for Nuget package for net6.0-windows #102

PR Checklist

• Has tests (if omitted, state reason in description)
• Rebased on top of master at time of PR
• Changes adhere to coding standard

[brianlagunas]

I have an overall concern about the current approach for building the design projects.

@mgoertz-msft can you confirm this is the correct way to output these design assemblies? Do we do something in Azure DevOps to correctly package the design assemblies for each TFM?

[mgoertz-msft]

I guess the validation error may have the answer...

[mgoertz-msft]

@brianlagunas Found it:

XamlBehaviorsWpf/src/Microsoft.Xaml.Behaviors/Microsoft.Xaml.Behaviors.csproj

Line 90 in 691f2e4

<Target Name="IncludeProjectToProjectAssets">

Perhaps we need to put the TFMs we are targeting in a .props file so we don't have to change them in multiple different places

[brianlagunas]

Yeah, I think this is an area that needs improvement. I'll get this fixed so that what we have builds, then look to improve this process in the future.