Home Dashboard Directory Help
Search

Visual Studio project templates for extensions confusing in New Project Dialog by Carlos J. Quintero


Status: 

Closed


1
0
Sign in
to vote
Type: Bug
ID: 792892
Opened: 7/7/2013 3:21:52 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

1) The new "Visual Studio Add-in" project template installed by the VS 2013 SDK appears in the New Project dialog under the node "Other Project Types" \ "Extensibility", but it doesn't appear under the "<Language>" \ "Extensibility" nodes as the "Visual Studio Package" template does.

2) The "Visual Studio Shell Isolated" project template appears in the New Project dialog under the node "Other Project Types" \ "Extensibility", but it doesn't appear under the "Visual C#" \ "Extensibility"
Details
Sign in to post a comment.
Posted by Microsoft on 7/8/2013 at 12:54 PM
Hi Carlos,

Thanks for the feedback - As it turns out the New Project Dialog is an area we're looking to do a significant amount of work on in the next release. Hopefully we'll be able to address general discoverability & languages issues like this one then.

For now however we don't expect to make this change in VS 2013.

Tony Goodhew,
Program Manager, VS Pro.
Posted by Carlos J. Quintero on 7/8/2013 at 10:58 AM
Hi Tony,

I know it is "by design" and not really a bug, but what I was requesting was to make the "Visual Studio Add-in" template more discoverable ;-)

The really good solution would be to remove the language page of the wizards and to inject the language from outside the wizard (as a "parameter"), depending on the selected language node in the New Project dialog.
Posted by Microsoft on 7/8/2013 at 10:28 AM
Hi Carlos,

This is by design. The two project templates you refer to "Isolated Shell" and "VS Addin" should only appear in the "Other Project Types" node. The reason for this is that both these project types are multi-language. The "VS Package" project template is often used as a component of extensions and we wanted that to be readily discoverable.

Because this is by design I'm closing this issue. Please reactivate it if you have need anything more.

Thanks,

Tony Goodhew,
Program Manager, VS Pro
Posted by Microsoft on 7/7/2013 at 11:43 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 7/7/2013 at 3:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.