Skip to content

Allow Options With Folder Structure When Creating a Diagnostic or Refactoring Extension #192

@JasonBock

Description

@JasonBock

If I create a project like a class library in a solution, the template creates that one project within the solution's folder. For example, if I have a solution called Solution1, and I create ClassLibrary1 within that solution, a ClassLibrary1 folder is created within the Solution1 folder, and ClassLibrary1's assets are within the ClassLibrary1 folder.

When I create a diagnostic, an intermediate folder is created. For example, making Diagnostic1 creates a Diagnostic1 folder under Solution1, and then the Diagnostic1, Diagnostic1.Test, and Diagnostic1.Vsix folders are under Diagnostic1. Also, the template automatically creates a test project. While I'm personally an advocate for tests, I think the user should have the option to make it. Also, don't append ".Test"; I usually name my test assemblies ".Tests" and the user should control over the naming of their assets.

I'd like it if the template gave the user more control over the location of the generated projects on disks along with their names.

(This currently exists with the VS2015 CTP5 templates and has been the case for some time).

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions