Rename doesn't seem to work

Hi.

I’ve tried building and running dotnet-new3 from the master branch and, although it copies the file in question, it fails to rename it in one of my templates.

BTW, I have to rename this file after copying because, if it’s already called template.json then dotnet new -i will pick up the template content as another template to install (which isn’t correct since this template is actually for creating new templates).

Given that I’ve never seen this feature work correctly, I’m open to the idea that perhaps I’m just doing it wrong 😉

Either way, any assistance would be greatly appreciated.

[mlorbetske]

Found the issue, checked in the fix & kicking off a new build. Thanks for pointing this out 😃

[mlorbetske]

Agreed. We’ve been discussing for months which sets of information are relevant in the different contexts and how we should surface that information. We haven’t really landed on a solid plan for this yet, but I’m thinking something along the lines of diagnostics streams will need to be added to the host interface, all “interesting” cases would be logged via the new methods and there’d be some mechanism for enabling/disabling/filtering the records logged.

@seancpeters