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
Was trying to add another components (headered controls) as a project reference to the samples of another project (behaviors.samples) so that I could use the control within the samples for other examples in the Toolkit.
However, in VS, trying to use the UI causes a 'Missing value for TargetPlatformWinMDLocation property' error to appear. Not sure if we're missing this property and need to do something to 'trick' VS, or if we need to report this to VS?
Steps to reproduce
1) Open Behaviors component solution
2) Right-click on Behaviors.Samples project
3) Add -> Project Reference
4) See Error
Expected behavior
Able to add reference to project via VS UI
Screenshots
Code Platform
UWP
WinAppSDK / WinUI 3
Web Assembly (WASM)
Android
iOS
MacOS
Linux / GTK
Windows Build Number
Windows 10 1809 (Build 17763)
Windows 10 1903 (Build 18362)
Windows 10 1909 (Build 18363)
Windows 10 2004 (Build 19041)
Windows 10 20H2 (Build 19042)
Windows 10 21H1 (Build 19043)
Windows 11 21H2 (Build 22000)
Other (specify)
Other Windows Build number
No response
App minimum and target SDK version
Windows 10, version 1809 (Build 17763)
Windows 10, version 1903 (Build 18362)
Windows 10, version 1909 (Build 18363)
Windows 10, version 2004 (Build 19041)
Other (specify)
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
No response
Help us help you
No, I'm unable to contribute a solution.
The text was updated successfully, but these errors were encountered:
Describe the bug
Was trying to add another components (headered controls) as a project reference to the samples of another project (behaviors.samples) so that I could use the control within the samples for other examples in the Toolkit.
However, in VS, trying to use the UI causes a 'Missing value for TargetPlatformWinMDLocation property' error to appear. Not sure if we're missing this property and need to do something to 'trick' VS, or if we need to report this to VS?
Steps to reproduce
Expected behavior
Able to add reference to project via VS UI
Screenshots
Code Platform
Windows Build Number
Other Windows Build number
No response
App minimum and target SDK version
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
No response
Help us help you
No, I'm unable to contribute a solution.
The text was updated successfully, but these errors were encountered: