Skip to content

Conversation

@KevinRansom
Copy link
Contributor

My apologies.

In my enthusiasm for sucking the bytes out of the product I made it so no one could use any tooling to work with our repo.

My bad!

Anyway this puts things back into place.

I think we will not compress the FCS metadata until after VS 2022.4 has shipped. So the first RTM FCS with compressed data will be the one that ships with VS 2022.5 ... obviously there will be previews prior to that.

That will ensure that the RTM version of VS and any tools that rely on FCS will have time to adjust. Primarily that means adopting the .Net 7.0 Sdk for builds.

<CompressMetadata>true</CompressMetadata>
<CompressMetadata Condition="'$(CompressAllMetadata)' != 'true'">false</CompressMetadata>
<NoOptimizationData>true</NoOptimizationData>
<CompressMetadata Condition="'$(CompressAllMetadata)' != 'true'">false</CompressMetadata>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate line?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes it is, copy and paste the bane of my life.

@KevinRansom KevinRansom merged commit 236db98 into dotnet:main Aug 25, 2022
@KevinRansom KevinRansom deleted the revertcompression branch October 12, 2022 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants