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
would mono T4 be interested in my fork?? netcore 3.x compatible #89
Comments
I think I need this support also. |
I sure am interested. I hope they seriously look into this. |
@kccarter76 could you release your fork as nuget? seems no one here is merging your changes... |
@kccarter76 and maybe also enable issues on your fork then |
My apologies for the delay in responding. I'm definitely interested in merging any improvements, though I would want them to be split into separate PRs for each atomic change so that I can review them more easily. |
that would be very hard to do, because the fork is greater than 100 builds past the current pull request that I have pending. there are significant changes made to ensure that the transformation host/session objects, could be serialized across a named pipe. this was necessary for a net core framework app built in visual studio which was a .net framework application. actually net 5 does not change a thing in regards to debugging a t4 template. you still need the separate process in order to attach a debugger. what net 5 on both sides simplifies the serialization. It is very likely that Microsoft will roll there own with the next iteration of visual studio. |
Fair enough. The offer to review/merge PRs individual features/fixes from your fork stands. I might cherry-pick some stuff myself, do you mind if I do? I'll make sure it's properly attributed. |
that is fine |
the fork is located here.
I have done a lot of work to ensure that ParsedTemplate, TemplateSettings and the Templating interfaces are serializable. This means they can pass through a named pipe connecting two different processes. This approach supports the following scenerios, framework to netcore, mono to framework, mono to netcore.
I have also done work on Compiled Template to ensure compatibility with the AssemblyLoadContext which replaces AppDomain for netcore implementations.
this fork will help in resolving #70 ground work for #47 as well. after all I built this for visual studio 2019 solution for t4 templating between .net framework and netcore.
on another note some of the code in this project depends on the hash key never changing. this does not work between processes, this was done by the runtimes to protect against a hash attack.
below is an example of T4 template that I have been able to generate
Settings.ttinclude
SqlServer.ttinclude
DataContext.stt
DataModels.stt
The text was updated successfully, but these errors were encountered: