-
Notifications
You must be signed in to change notification settings - Fork 165
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
Package the T4 for distribution #4
Comments
I'm not sure you can actually package it as a NuGet package. I'd recommend just copying the file into your repo. It hasn't changed in years. |
Please find my PR at your convenience. Thank you... |
Hi, decided not to go ahead with NuGet packaging. I really don't want this to be a shared library. It's just web blog sample code with unit tests. People should adapt/copy as appropriate. |
No problem. Thanks for letting me know anyway. Moving forward, you expect the library to stay pretty much as-is? In other words, I'll be happy to package it myself, as I think it provides good value for folks on this path. At least it did for me. Thanks again. |
It's possible additional classes will come depending on my own personal needs. If you do package it up please don't publish it publicly - I don't want the confusion. |
I'm running it by you as a first right of refusal. If you're unwilling to publish it, I will; just giving you the nod ahead of time. Along which lines, you expect additional parts to come, I am more than happy to coordinate some packaging along these lines. Thanks again. |
No quite sure what you mean by that. |
At the moment I've cloned the repo as a submodule, but this just doesn't feel right. I certainly don't need the CSharp bits, for instance.
I don't know if NuGet is an appropriate distribution channel for T4-based concerns? Considering also that T4 is a VS extension.
It's a thought.
Thanks!
The text was updated successfully, but these errors were encountered: