Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Adding special target that will get a resource file and pass it to ilasm for S.R.CS.Unsafe so that it has the right version headers#31806

Merged
joperezr merged 2 commits intodotnet:release/2.1from
joperezr:FixingUnsafeVersionHeader
Sep 4, 2018
Merged

Adding special target that will get a resource file and pass it to ilasm for S.R.CS.Unsafe so that it has the right version headers#31806
joperezr merged 2 commits intodotnet:release/2.1from
joperezr:FixingUnsafeVersionHeader

Conversation

@joperezr
Copy link
Member

Fixes #24012 . Cherry-picked from #31782 [No Conflicts]

Description

System.Runtime.CompilerServices.Unsafe.dll is an ilproj in our solution, which means we build it by directly calling ILAsm. Because of this, our version headers don't get automatically embedded into the output assembly, which means that the resulting library won't have version information. This is preventing internal customers to consume this library. With the changes on this PR, we are effectively passing in a resource object to the ILAsm call, so that the right version information exists on that library.

Customer Impact

No negative impact. The only difference now will be that the assembly will have version information in it.

Regression?

No

Risk

None.

…asm for S.R.CS.Unsafe so that it has the right version headers (dotnet#31782)

* Adding special target that will get a resource file and pass it to ilasm for S.R.CS.Unsafe so that it has the right version headers

* PR Feedback

* Updating buildtools and fixing obj name
@joperezr
Copy link
Member Author

Note that in order for this to be green, we need to ingest the following buildtools change: dotnet/buildtools#2127

@joperezr joperezr requested a review from danmoseley August 16, 2018 18:15
@karelz karelz added this to the 2.1.x milestone Aug 23, 2018
@danmoseley danmoseley added the Servicing-consider Issue for next servicing release review label Aug 30, 2018
@jamshedd jamshedd added Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Aug 30, 2018
@jamshedd
Copy link
Member

Approved for 2.1.5

@danmoseley
Copy link
Member

@joperezr please merge when this is green - I merged buildtools

@joperezr joperezr merged commit 5b16645 into dotnet:release/2.1 Sep 4, 2018
@danmoseley danmoseley modified the milestones: 2.1.x, 2.1.5 Sep 13, 2018
@danmoseley danmoseley added Servicing-approved Approved for servicing release and removed Servicing-approved Approved for servicing release labels Sep 13, 2018
@joperezr joperezr deleted the FixingUnsafeVersionHeader branch November 2, 2018 20:11
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants