Mike Lorbetske

This has been discussed before (though I can't seem to find the issue where it was discussed) - the thinking at the time was that it might add noise to...

This is actually more interesting than it would seem and is the reason we haven't approached calculating the namespace in the past (excepting for providing value forms that "namespace-ify" the...

This concerns me in the context of class library. It supports `netstandard1.0` ... `netstandard1.6`, `netstandard2.0`, `netcoreapp1.0`, `netcoreapp1.1`, `netcoreapp2.0` which will get super long & we've already had issues with the...

Yep, those are the same values accepted by --framework. Short forms of the TFMs are interesting, we can do that.

This is currently "by design" (see https://github.com/dotnet/templating/issues/350#issuecomment-281851892). Originally, we had standardized all content on LF line endings, but this caused issues with certain editors on Windows and produced a ton...

Hi @tintoy, these values can be accepted via parameters but cannot be figured out automatically at this time. As far as the usage of these names go (file names/namespaces/literal strings/etc),...

Moving this to the backlog as this may be something interesting to add as a "generated" type symbol that would know how to look at existing content to try to...

Properties can be added as they won't be understood by older versions. However, the approach mentioned doesn't require a schema modification (it fits nicely within the existing extensibility model); it's...

Thanks for the PoC @tintoy, I'm hesitant to take a dependency on MSBuild here though due to coordination concerns with all the different release vehicles for this project.

_From @seancpeters on June 5, 2018 23:54_ Could you post some info on the directory structure of your template source, including: - the fully expanded path to the docker file...