-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import Windows desktop target when property is set #12106
Conversation
src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.Sdk.props
Outdated
Show resolved
Hide resolved
src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.TargetFrameworkInference.targets
Outdated
Show resolved
Hide resolved
src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.Sdk.targets
Outdated
Show resolved
Hide resolved
src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.Sdk.targets
Outdated
Show resolved
Hide resolved
Find the weird issue (the reason of test failed. dotnet build are all fine. However, dotnet add packages chock on missing |
|
||
<!--https://github.com/dotnet/sdk/issues/12403--> | ||
<PropertyGroup> | ||
<_TargetFrameworkVersionValue>0.0</_TargetFrameworkVersionValue> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dsplaisted I added this to workaround the missing property issue while I am checking into dotnet/wpf
Hello @wli3! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
@@ -127,5 +127,7 @@ Copyright (c) .NET Foundation. All rights reserved. | |||
|
|||
<Import Project="$(MSBuildThisFileDirectory)Microsoft.NET.PackTool.props" /> | |||
<Import Project="$(MSBuildThisFileDirectory)Microsoft.NET.PackProjectTool.props" /> | |||
|
|||
<Import Project="$(MSBuildThisFileDirectory)../../Microsoft.NET.Sdk.WindowsDesktop/targets/Microsoft.NET.Sdk.WindowsDesktop.props" Condition="'$(_MicrosoftWindowsDesktopSdkImported)' != 'true'"/> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<Import Project="$(MSBuildThisFileDirectory)../../Microsoft.NET.Sdk.WindowsDesktop/targets/Microsoft.NET.Sdk.WindowsDesktop.props" Condition="'$(_MicrosoftWindowsDesktopSdkImported)' != 'true'"/> | |
<Import Sdk="Microsoft.NET.Sdk.WindowsDesktop" Project="../targets/Microsoft.NET.Sdk.WindowsDesktop.props" Condition="'$(_MicrosoftWindowsDesktopSdkImported)' != 'true'"/> |
I just ran into an issue where I need to test a patched Desktop SDK. This allows easier substitution of SDK via global json from a custom NuGet feed.
@wli3 @dsplaisted Can I ask why this pattern wasn't used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Nirmal4G I don't know that we considered it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dsplaisted Can we do this then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What advantage that give us? I think it is easy to understand what a simple file import does.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, but it does not allow substitute Sdks from a custom NuGet feed without patching the base SDK.
No description provided.