-
Notifications
You must be signed in to change notification settings - Fork 808
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
Consume projections via nupkg vs. checked-in binaries #2733
base: develop
Are you sure you want to change the base?
Conversation
There is two instance of WINOBJC_SDK\ usage, that is being cleaned up now :) |
@rajsesh-msft the projection code is generated after applying the fixes to winmd2objc (my other CRs) #ByDesign |
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.
Per offline discussion, let us not check-in the generated code. Since this doesn't need to be built every day, we could just wrap the generation step in a script or a build task. This also doesn't have to be nightly built either.
msvc/sdk-build.props
Outdated
@@ -24,6 +24,10 @@ | |||
</ProjectReference> | |||
</ItemGroup> | |||
|
|||
<ItemGroup> | |||
<PackageReference Condition="'$(BuildingFrameworksCore)' != 'true'" Include="WinObjC.Frameworks.UWP" Version="*" /> |
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.
This is an interesting approach!
Do you think it should go down with the other PackageReferences?
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.
nope, we want to avoid Frameworks.Core from consuming this package.
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.
That doesn't mean it can't go in the same block of package references... that just means we have to keep the Condition
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.
ah, I assumed you meant to just include it without the condition.
Consider it moved.
@@ -223,6 +223,9 @@ | |||
<ItemGroup> | |||
<ClInclude Include="..\..\..\..\tests\unittests\Starboard\LifetimeCounting.h" /> | |||
</ItemGroup> | |||
<ItemGroup> | |||
<PackageReference Include="WinObjC.Frameworks.UWP" Version="*" /> |
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.
Indentation is odd here!
old method was not using the local package, if we can't find a package locally, we look it up in mscodehub
ac37502
to
4e5e83b
Compare
This saw random failures with NotificationQueue and filemanager tests. |
ping! @rajsesh-msft @DHowett-MSFT |
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.
Moderately apprehensive about using BuildingFrameworksCore to turn off the package reference instead of inserting the package reference in every project that consumes UWP.
Also, don't our internal frameworks avoid Projections now? They should be generally free of it, and we might not want to even ALLOW them to link against it so we don't accidentally reintroduce dependencies.
This will establish the WinObjC.Frameworks.UWP/MSAds packages and will be consumed by projects via the nupkg
Fixes #2688, #2687
This change is