With the new iteration configuration in TFS2012, it would be beneficial to be add a few custom fields the dialog. In TFS2010, this functionality was a work item type so it was very easy to add additional fields. Also, this was a good place to put goals for the iteration and the details from the retrospective. This has now all been lost.
I like the direction TFS2012 went, but now have lost some of the functionality that was quite useful int TFS2010.8 votes
Right now there are too many places admin links are are given to the end user. Even though user will not have access, links should also be hidden based on role (just like any other M$ product). All right click -> security, all admin links on Web UI and Team Explorer settings should only be visible to TFS admins.7 votes
At the moment there are only 2 ways of populating the allowed values list in a work item. In the work item definition itself or in a global list. Some more flexibility would be great here. Besides that. Allowing a list of values to be displayed as a tree would be great as well. Not limit this only to the area and iteration field. Another solution might be to enable non admin users to add values to the allowed values list without "hacking" in the work items or Global Lists8 votes
You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it's too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future.6,171 votes
We have more information on the next version of InstallShield Limited Edition that will be included in Visual Studio 2013.
We’d like to thank you all for your comments on this UserVoice entry. We have been discussing the comments on InstallShield Limited Edition (ISLE) raised here with Flexera and we are currently working with them to address the top issues. At this stage we have no plans to include the former Visual Studio Setup Projects in future product versions but we will continue to work with Flexera and the community to ensure Visual Studio customers’ setup needs will be met with no-cost tooling that supports a broad range of scenarios.
Tony Goodhew, Program Manager, VS Pro.
To keep up with improving processes, there needs to be a migration path for existing templates to be upgraded to new templates. Some information in work items may be lost when mapping these to new work item types of the new templates, but this may well worth the benefits of moving to a newer process. Creating a new team project is not always feasible, especially if the source code versioning needs to be in place.1,275 votes
Currently, to get these features into a CI build, we have to pass a lot of MS Build properties around. Having gone through the trouble of creating my own templates to handle these features, it would be nice to see them included out of the box.290 votes
This suggestion is on our product backlog for consideration in a future release.