T4 template doesn't run in "T4DocoptNetHostApp" about docopt.net HOT 7 CLOSED

I have tried adding <#@ assembly name="NetStandard" #> and it seems to fix it at least for .NET Standard

from docopt.net.

I have initially tried to mitigate the problem by having the path correctly set in the NuGet install.ps1 script. The approach is brittle, but it provides some mitigation for the fresh package installs. Looking at this again, this is not supported anymore in VS 2017+ - I will dig a bit deeper.

from docopt.net.

I have tried adding <#@ assembly name="NetStandard" #> and it seems to fix it at least for .NET Standard

I wonder though how that'll sit with a non-SDK-style project that targets .NET Framework.

I do find what's being attempted with T4 is somewhat split & partial given that some code generation happens in the library:

Perhaps it's time to look for a fresh approach to the problem? Perhaps something that's done via an MSBuild task? I don't have any proposal off the top of my head at the moment.

from docopt.net.

Yes I agree. I am a bit disconnected from the .net world. How popular is T4 nowadays?

from docopt.net.

How popular is T4 nowadays?

Can't speak for everyone, but I think it's fine if used in a limited way that's not connected to the IDE and works cross-platform via mono/t4. I think what people love about T4 is the quick inner dev loop with saving and seeing the generated code/text update almost immediately. I wish dotnet watch could make up for that, but I think it's somewhat limited to web development scenarios for now. I don't have the cycles to explore the options with MS Build because I'd rather channel my energies on exploring the source generator method in PR #77. If I get lightbulb moment for T4 part or a replacement, I'll drop a PR (no promises).

from docopt.net.

Yes I would rather invest in the source code generator as well.

from docopt.net.

Closing since T4 support was removed in PR #136.

from docopt.net.