Amadeusz Sadowski
Amadeusz Sadowski
What we want: * a `ProjectReference` to Generator project that ignores `TargetFramework` of the Generator * a reference to the Generator's assembly
> Yes, this is a tough problem that I've fought for better support for since NuGet essentially broke it years ago. One of those links above is a bug I...
Thinking about this some more. Currently for 0.7 we're shipping with the requirement for end users to mangle their references manually, as per Readme. Now, for future, I think patching...
Needed by #226
This should also include documenting *stable* extension points so consumers know what we won't break/what is considered "public".
Let's fall back a little and try to list out all the requirements that we want from code generation framework. My thoughts: 1. Roslyn's `Compilation` is available for the generator...
@Corniel let's first try to define the shape of this abstract new project. If we have something nice to show, it'll have more chance to gain interest of others. So...
I like the idea of GeneratedCode result class, that could open up possibilities. As per the attribute, we can't implement it like you've shown, because assembly where attribute is defined...
Yes I think it would be a nice simplification. (attribute in context instead of in ctor) Uno's GenerateBefore/After is actually a bit more advanced, actually. It requires multiple compilation generations/tiers....
I mean, I've never needed it, but it can be a future enhancement anyway. I'd not say this should be a part of the MVP we'd start with.