-
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
Don't reference AssemblyMetadataAttribute in generated AssemblyInfo.cs when targeting net40 #11862
Comments
@wli3 @dsplaisted is not defining |
Ping @wli3 @dsplaisted, is |
It was introduced in .NET 4.5. So if the TargetFrameworkIdentifier is .NETFramework and the version is less than 4.5, we should not emit this. FYI @clairernovotny @tmat, looks like we won't get the |
@clairernovotny Perhaps we should require packages to have implementation assemblies for netstandard, netcoreapp or net45+ and not validate libraries that target earlier frameworks. |
@tmat Not really sure why this matters? What do we need this attribute in the assembly for other than informational use? The thing we actually check is in the PDB. |
@clairernovotny We would use this URL to clone the sources when validating reproducibility. The info in the PDB does not include URL that can be cloned. It provides content URL pattern for each file. I guess another approach would be to fall back to downloading each file separately if the clone URL is not available. Less efficient, but perhaps ok as a fall back. |
@tmat I guess I assumed that we'd just download each file. There's no guarantee the repo format is Git either, and no need for it to be long as we can download the files via the URL. |
@clairernovotny I suspect that will be much slower than clone. But certainly something to try and measure. |
Hi @sfoslund , |
@heng-liu sure, you can set the |
Thanks! @sfoslund |
@sfoslund What version was this fixed in? |
@sharwell It should be in preview 7 |
This is necessary for us to test features like covariant returns because we need to be able to target `net5.0` in our unit test projects. Issues encountered in this update: - WinRT is no longer supported in .NET 5. As a result we no longer multi-target .NET Core in our WinRT test assembly as well as having to disabling a few WinRT tests in others. dotnet/runtime#37672 - Change our Debugger Proxy tests to react to a runtime change dotnet/runtime@c362923 - Work around .NET5 P6 bug dotnet/sdk#11862
* Move to the .NET 5 SDK This is necessary for us to test features like covariant returns because we need to be able to target `net5.0` in our unit test projects. Issues encountered in this update: - WinRT is no longer supported in .NET 5. As a result we no longer multi-target .NET Core in our WinRT test assembly as well as having to disabling a few WinRT tests in others. dotnet/runtime#37672 - Change our Debugger Proxy tests to react to a runtime change dotnet/runtime@c362923 - Work around .NET5 P6 bug dotnet/sdk#11862
The ef6 build targeting net40 failed recently with the following error after updating the .NET SDK to 5.0.100-preview.6.20266.3.
dotnet/ef6#1678
AssemblyMetadataAttribute doesn't exist in net40. ef6 has an AssemblyMetadataAttribute polyfill in some of its projects, but not the one that failed to build. Adding the polyfil works around the issue.
It looks like this is a regression introduced by #11559 and could be fixed by not generating a reference to AssemblyMetadataAttribute when targeting net40.
The text was updated successfully, but these errors were encountered: