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

Proposal to add Framework specific inbox source generators #181

Merged
merged 18 commits into from
Jun 24, 2021

Conversation

ericstj
Copy link
Member

@ericstj ericstj commented Feb 23, 2021

This document describes desired characteristics for source generators we
wish to add to .NET 6.0.

This document describes desired characteristics for source generators we
wish to add to .NET 6.0.
ericstj and others added 2 commits February 23, 2021 00:08
Co-authored-by: Jan Kotas <jkotas@microsoft.com>
Co-authored-by: Jan Kotas <jkotas@microsoft.com>
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
@ericstj
Copy link
Member Author

ericstj commented Mar 5, 2021

@elinor-fung I addressed most of your feedback, care to have another look?

@elinor-fung
Copy link
Member

Looks good. Thanks for clarifying/removing the side-by-side terminology - definitely helpful for me.

accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
Co-authored-by: Jeff Handley <jeffhandley@users.noreply.github.com>
accepted/2021/InboxSourceGenerators.md Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Outdated Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Show resolved Hide resolved
accepted/2021/InboxSourceGenerators.md Show resolved Hide resolved
Co-authored-by: Jared Parsons <jaredpparsons@gmail.com>
@danmoseley
Copy link
Member

@RussKie could you share briefly what source generators the Winforms team is creating this cycle? Just curious for those not aware.

@RussKie
Copy link
Member

RussKie commented May 27, 2021

Here're the details #223

RussKie added a commit to dotnet/wpf that referenced this pull request Jun 2, 2021
Provide a mechanism to ingest Windows Forms specific analyzer props and
targets into Microsoft.NET.Sdk.WindowsDesktop from Windows Forms transport
package, and copy these files into `targets` folder of the SDK, so that
the props files are resolved and imported when a developer builds a Windows
Forms app.

In the end the new props file will end up in a location similar to this:
`C:\Program Files\dotnet\sdk\6.0.<version>\Sdks\Microsoft.NET.Sdk.WindowsDesktop\targets\`.

This work relates to dotnet/designs#223, and acts
as a workaround until dotnet/designs#181 is
approved and implemented.
RussKie added a commit to dotnet/windowsdesktop that referenced this pull request Jun 2, 2021
Provide a mechanism to import Windows Forms specific analyzers from
Windows Forms transport package, and and package those into
Microsoft.WindowsDesktop.App.Ref bundle, so that they are available in
Windows Forms app out of the box.

The analyzers are referenced via props and targets located in
`C:\Program Files\dotnet\sdk\6.0.<version>\Sdks\Microsoft.NET.Sdk.WindowsDesktop\targets\`,
which is facilitated by dotnet/wpf#4605.

This work relates to dotnet/designs#223, and acts
as a workaround until dotnet/designs#181 is
approved and implemented.
RussKie added a commit to dotnet/wpf that referenced this pull request Jun 7, 2021
Provide a mechanism to ingest Windows Forms specific analyzer props and
targets into Microsoft.NET.Sdk.WindowsDesktop from Windows Forms transport
package, and copy these files into `targets` folder of the SDK, so that
the props files are resolved and imported when a developer builds a Windows
Forms app.

In the end the new props file will end up in a location similar to this:
`C:\Program Files\dotnet\sdk\6.0.<version>\Sdks\Microsoft.NET.Sdk.WindowsDesktop\targets\`.

This work relates to dotnet/designs#223, and acts
as a workaround until dotnet/designs#181 is
approved and implemented.
@terrajobst
Copy link
Member

@ericstj should this be merged now?

@ericstj
Copy link
Member Author

ericstj commented Jun 9, 2021

@ericstj should this be merged now?

Nearly. I think I have POR now that we want to do this. I want to take one last read through and make sure I don't need to update some of the details. Expect to merge by end of week.

@ericstj
Copy link
Member Author

ericstj commented Jun 17, 2021

I haven't forgotten about this, just had less time than I thought last week due to a family visit / time off. I'll move this forward shortly.

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.