-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Convert DesignTools
projects to Sdk-style
#3794
Convert DesignTools
projects to Sdk-style
#3794
Conversation
Thanks Nirmal4G for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌 |
@Nirmal4G looks like the build is failing:
This is marked as draft, is there more coming or should this be ready to review soon? We'd like to try and close out the release this week if possible. Thanks! |
6350c9e
to
48f7df1
Compare
Rebase gone wrong. Sorry about that. My patches were applicable before splitting the controls. Now, it should build fine.
There are few patches left to finish the follow-up tasks that were pending previously.
Sure. These are minor issues. Should be done within a day or two! |
Thanks @Nirmal4G! 🦙❤ Build looks good now too! 🎉 Keep us posted, sound like everything's on track. Really appreciate all your help here. |
@Nirmal4G think we can get any final updates in by tomorrow (3/10) so we can include them in 7.0? |
48f7df1
to
4c25d41
Compare
Thanks for updating @Nirmal4G. I'm still able to reproduce the HeaderedContentControl not showing up in the DocumentOutline and the MarkdownTextBlock missing from the list. Should these two issues have been fixed at this point in time yet? Considering it seem like what we have for now in main is a good first step for this transition, I'm going to not hold the release on waiting for this and move this to 7.1 so we can finish this work without pressure. Thanks! |
4c25d41
to
c843eee
Compare
@Nirmal4G does this PR need updating now that the underlying one has been merged? Or is it still waiting on another PR of yours? |
DesignTools
projects to Sdk-style
|
@RosarioPulella It was intentional. I didn't want GitHub to see the link. This PR doesn't require changes from the referenced PR. It was merely built on top of that PR and some build related issues were fixed in that PR. |
b41676e
to
a690457
Compare
a690457
to
2acd122
Compare
It might be because of the |
2acd122
to
db450f3
Compare
db450f3
to
19a4ae9
Compare
19a4ae9
to
1a4d512
Compare
Build error
|
1a4d512
to
ed3d75b
Compare
I think the build errors out because of the order of compilation of the projects. We should make sure the XML Doc is produced and copied before the |
1bbfe00
to
7f44f42
Compare
- Update Solution to Use CPS for the Design projects. - Move 'MetadataRegistration.cs' file into Common folder. - Remove 'AssemblyInfo.cs' file as it's generated by .NET SDK.
The reason we build the Controls library first is that we have a dependency on the XML Doc file it generates. The Doc file is embedded within the Design library and it uses it's type-info to populate metadata automatically.
Basic DesignTime support on-par with other controls in the toolkit. Reverts the following commit - Commit Message: `Media Controls does not have a "DesignTools" project` - Commit Hash : `1781e7f4291061c642fedfa5307aa80879838b56`
7f44f42
to
67f3906
Compare
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.
Everything is still working from my testing. Good refactor!
Thanks @Nirmal4G! This definitely makes things a lot simpler now for sure! |
Fixes #3805
Notes
We want to force the
WindowsDesktop
SDK to always useWinFX
targets from the SDK instead of using the .NET Framework's inbox version as the SDK version contains fixes around enablingPackageReference
. In .NET SDK v5, we added an overridable option to always opt-into this behavior. See dotnet/wpf#2976 and dotnet/wpf#4630. Thus, we'll be usingMicrosoft.NET.Sdk.WindowsDesktop
instead!PR Type
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
PR Checklist
Please check if your PR fulfils the following requirements:
Other information
rebase
on latestHEAD
and then commit, without updating from the latestHEAD
.Merge pull request #xxxx from repo/branch
, and commit message to either PR message or messages of individual commits. Theauto-merge
bot does this by default.