-
Notifications
You must be signed in to change notification settings - Fork 606
Backport master changes to 5.x #710
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
Conversation
(cherry picked from commit 4a18ddf)
@stebet - If I could ask a big favor. Could you please backport your changes in #687 to the
I really appreciate it. |
Sure, I'll take a look at that tomorrow. |
@stebet great thank you very much |
@@ -71,7 +71,7 @@ | |||
</ItemGroup> | |||
|
|||
<ItemGroup> | |||
<PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies" Version="1.0.0" PrivateAssets="All" /> | |||
<PackageReference Include="Microsoft.NETFramework.ReferenceAssemblies.net451" Version="1.0.0" PrivateAssets="All" /> |
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 failure were you seeing? You shouldn't need to directly reference those sub packages. That should be correctly handled by referencing the Microsoft.NETFramework.ReferenceAssemblies
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.
On Linux and OS X builds -
https://gist.github.com/lukebakken/30d05fc5f03ee9ff47527e5d09864f26
This is the Vagrantfile
that can bring up a Debian 10 VM with the same packages as our CI build - https://gist.github.com/lukebakken/676bb6d75e30aa5a0bc533f9af87a336
I have no idea what's up, just that these changes fix the builds! 🤷♂
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 really make sense though, because those packages would already be referenced with the original reference.
You would need to add Microsoft.NETFramework.ReferenceAssemblies to the WinRT project, but shouldn't need to reference a specific one directly like that.
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.
I will give the WinRT suggestion a try. That's probably 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.
e7578bf works. The reference is required in all of those .csproj
files.
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.
Thanks for double-checking.
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.
If you're still having a problem with that change, post the build log failure, and I'll see if I can figure it out.
Ultimately I guess it does't matter, but it always bothers me when there's something weird going on without an explanation why. 😄
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, should have refreshed before posting. Glad to see that solved 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.
it always bothers me when there's something weird going on without an explanation why.
Me too, so thanks for checking. I don't have the time to dig into package / assembly / nuget issues and it's been long enough that I've been out of the .NET world that I'm quite rusty.
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.
Things have also changed pretty dramatically with the introduction of PackageReferences and the new project system.
(cherry picked from commit 04518f1)
(cherry picked from commit db2f5a9)
(cherry picked from commit fca0136)
(cherry picked from commit 0ecf37d)
Use "dotnet build" command (cherry picked from commit 5b6bf18)
Remove unused files (cherry picked from commit 9e30a1b)
(cherry picked from commit 07c1936)
(cherry picked from commit 172ad8c)
(cherry picked from commit 308f37e)
(cherry picked from commit 6378d05)
Let operating system choose which TLS version to use (cherry picked from commit 57cb199)
(cherry picked from commit d0c5123)
(cherry picked from commit 1e07323)
🔎 Sourcelink added! (cherry picked from commit d81dd9d)
cba2b26
to
e7578bf
Compare
@lukebakken How closely did you look at the approval test changes in this branch to make sure there aren't breaking changes to types? That's my main concern with the backport process since breaking changes were okay when this stuff was merged into |
Well I don't think there were changes to that but now you've got me double-checking... |
Well that's super, changes made it in that I didn't expect. Re-re-re-checking. |
Maybe not. I see that there is a package added for the approval tests, and the expectation file, but the actual test itself isn't run. Going to address that because it will determine if API changes were made. |
If any of the task changes caused API changes, let me know so I can fix them. There shouldn't be any need to change the API and cause breaking changes for them. |
I'm getting the API approval test running in the |
Backport master changes to 5.x (cherry picked from commit ad20306)
I am reviewing all changes to
master
since the5.1.2
release and backporting all that are appropriate for a5.2.0
release.