Just as in old versions add the template of 'web service page' in the 'add new item' sub-menu which is missing in VS 11

1. packages for different architectures can be choosen during installation. e.g. if I don't develop fo Itatium, just give me a option not to
install anything(headers, libraries) related to Intel Itatium, and when updating service pack, don't install sp for features I haven't installed.
2.

In the several windows we can fill in values. Especially for new users it's easer to learn TFS when they get familiar with the keywords like Effort, Business Value etc. Can be a tooltip or other technique to show the corresponding information.

Thanks.

When adding a SharePoint group to a resource calendar/group calendar that contains one or more Active Directory groups, one should be able to select an option to expand the individual users assigned to the AD group. This will allow all of the individual resources/users to be visible on the resource/group calendar. The current implementation only displays the name of the Active Directory group, thereby providing no insight into individual user/resource calendar details.

When have requirements based Test Suite you cannot order the tests, in regular query there is an Column Options box that contains a Sort Tab that will allow you to order your query. This feature should also be in the Requirements based Query.

I'd prefer property declarations within an Interface to remain one one-line while property implementations in the class appear on multiples, making interfaces easier to read.

e.g.:

public interface IMyType
{
string MyName { get; set; }
string MyAge { get; }
}

public class MyType: IMyType
{
public string MyName
{
get;
set;
}

public string MyAge
{
get;
}
}

Both formatting styles IMO work well in their own right, as the interface is easier to read while retaining the auto-new line formatting of property implementations.

in old diff, there was a popup when files were identical. although I hate popups, it was nice to have something "in your face" letting you know the files were identical. please add a high-contrast status bar with a message stating they are identical. please DO NOT use a popup dialog!

Revision control based on pessimistic concurrency has been obsolete for years (to say nothing of non-distributed revision control). The lock icon for an untouched file looks really silly.

Instead, I would go with icons to indicate new files, changed files, and maybe deleted files (with the file name greyed out).

If you're gonna go Metro (and I think you should), go all the way! I'd love to see the entire UI skinnable via CSS, right down to every last dialog.

It'll make writing UI themes much easier.

One of the primary ideas behind a REST API is that it is stateless. The current implementation of Web API seems to rely on Form Based Authentication. I would suggest ripping API Authentication out by default and have the default Web API template modified to reflect that. A selection of authentication of providers should be provided by the community or separate plug and play solutions.

Silverlight has already supported the custom markup extension.

Because Static, DynamicResource and DataType markup extensions connot be use on metro style app, at least, it is nessesary to support custom markup extension for metro style app.

Suppose I have a class and I'd like to define an interface such that this class implements this (new) interface I'd like to define. That is the the re-factoring will define an interface for me such that the public members and properties of the class are the members of the interface.

Of course the class should be modified to now implement this interface as well.

The selection in the statment completion window ist nearly invisible (light yellow frame on white background).
It shoud have more contrast (black frame?) or should be customizable.

When a test scenario failed and you do a retest after the bug is solved (with play the recorded test) it is not possible to continue your test from the solved point and start recording again (append to the existing recording).
At this moment you have to start again and select "overwrite existing recording" and rexecute the full test scenario again from the beginning.

It would be great if there where parameters available that insert the date of today. Date of today - x days or + xdays, months, years. It should be possible to format this date (@Dateformatted(dd/MM/yyyy HHmm))
-> This would make test that checks on a date < today or > today still work on a later date without having to convert the test to a codeduitest and create a custom methode.
-> Is can also be used in a name to make a value unique if there is a condition that values need to be unique.