Add Deployable Dependencies missing from VS11 beta - by Sly.Gryphon

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 735553 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 4/4/2012 10:47:28 PM
Access Restriction Public
Moderator Decision Sent to Engineering Team for consideration

Description

The "Add Deployable Dependencies..." context menu action for ASP.NET MVC 3 projects is not available in VS11 Beta.
Sign in to post a comment.
Posted by Sly.Gryphon on 4/10/2012 at 8:35 PM
Okay, so this is only an issue if you create an MVC 3 project in VS 2010 (without bin deployable), then upgrade it to VS 11, then want to change to bin deployable.

This could still be flagged as a warning in the upgrade/conversion report, maybe with an option/suggestion to change to Nuget.
Posted by Microsoft on 4/10/2012 at 1:55 PM
Hi Sly,

The "Add Deployable Dependencies" feature was removed from Visual Studio 11. It was removed because it is no longer needed. All the web project types in Visual Studio 11, including MVC, Razor, Web API, and others, are already set up to be automatically bin-deployable. That is, no additional actions are needed by the developer in order to "add deployable dependencies" because they're already all added to the project. This is done automatically because NuGet is used to add all the project references, and it always adds everything as a deployable reference.

Thanks,
The ASP.NET Team
Posted by MS-Moderator08 [Feedback Moderator] on 4/5/2012 at 2:12 AM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 4/4/2012 at 11:55 PM
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)