Skip to content
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

[BinFmt] Investigate the need of removal from deprecated code #8822

Closed
JanKrivanek opened this issue Jun 1, 2023 · 1 comment
Closed

[BinFmt] Investigate the need of removal from deprecated code #8822

JanKrivanek opened this issue Jun 1, 2023 · 1 comment

Comments

@JanKrivanek
Copy link
Member

JanKrivanek commented Jun 1, 2023

Background

#6215
This subitem is focused on code in src/Deprecated/*
Currently 11 usages. Hopefuly this doesn't need to be touched, or at worst just conditioned, otherwise cost might be significant

Expected output

Find answers to below questions (and if any work is recommended to be done - create item for next sprint):

  • Are there any scenarios where code in src/Deprecated/* can be part of NET binaries (not FullFW)?
  • Is it find to ceompletely left out this code from BinaryFormatter deprecation effort? Or do we need put usages behind explicit opt-in?
  • Based on above findings - what is the suggested resolution for code in src/Deprecated/*?
@ladipro
Copy link
Member

ladipro commented Jun 6, 2023

Microsoft.Build.Engine is FullFramework only, no need to worry about it for BF deprecation just yet. The longer-term plan is to remove it from main and stop shipping it altogether (#8826).

@ladipro ladipro closed this as completed Jun 6, 2023
@AR-May AR-May added the triaged label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants