Make sure EF7 does not currently depend on .NET 7 packages

[ajcvickers]

Since this makes it much harder to use daily builds, and we currently target .NET 6.

See #26405

[ajcvickers]

@MCFHTAGENTS I am not able to find where the .NET 7 packages are required. I was able to create an ASP.NET Core web application targeting .NET 6 and update to EF Core daily build packages without any problems. Can you post the csproj that was causing you issues in #26405?

[MCFHTAGENTS]

Arthur Thank you - I wasn’t expecting that!! Is there somewhere I can send privately and assume you just need the .csproj? Thanks Mark

…

Sent from my iPhone On 28 Jan 2022, at 20:38, Arthur Vickers ***@***.***> wrote:  @MCFHTAGENTS<https://github.com/MCFHTAGENTS> I am not able to find where the .NET 7 packages are required. I was able to create an ASP.NET Core web application targeting .NET 6 and update to EF Core daily build packages without any problems. Can you post the csproj that was causing you issues in #26405<#26405>? — Reply to this email directly, view it on GitHub<#27254 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHN6FSWYEL5GJTIRJ4SD4DDUYL5ETANCNFSM5MSHZDQQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ajcvickers]

@MCFHTAGENTS "avickers" at where I work.

[MCFHTAGENTS]

I have emailed you a log and my project file. Thank you

[ajcvickers]

@MCFHTAGENTS Haven't heard anything from you in a while. Are you still looking into this?

[MCFHTAGENTS]

Sorry been swamped and with 6.02 out the underlying issue was fixed for me on the originating thread. Will try and look if you think valuable

…

Sent from my iPhone On 14 Feb 2022, at 19:18, Arthur Vickers ***@***.***> wrote:  @MCFHTAGENTS<https://github.com/MCFHTAGENTS> Haven't heard anything from you in a while. Are you still looking into this? — Reply to this email directly, view it on GitHub<#27254 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHN6FSSOJ7P3JZPZJRXWKN3U3FIQBANCNFSM5MSHZDQQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[AndriySvyryd]

EF Team Triage: This issue is lacking enough information for us to be able to effectively triage it. In particular, it is missing the following information requested in the new issue template. Can you please provide this information?

Steps to reproduce

Ideally include a complete code listing that we can run to reproduce the issue.

Alternatively, you can provide a project/solution that we can run.

BTW we're not just doing this to be mean 😄... we get a lot traffic on this project and it takes time to attempt to reproduce an issue based on fragments of information. In addition, our attempt is often unsuccessful as the exact conditions required to hit the issue are often not explicitly included in the code provided. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we ask that folks give us a self-contained way to reproduce an issue.

For a guide on submitting good bug reports, read Painless Bug Tracking.

BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.