request feedback from a task or PBI or an an attachment to said task or PBI

When having a workitem which is ready for code review, then it would be nice that one can link to the shelveset

Code Clone is AMAZING. I have a *LOT* of cloned code due to an old codebase. I would like to prioritize by lines of code that I can fix rather than clone count. Clone count isn't always all that useful, since it prioritiezes a few cloned lines repeated dozens of times rather than whole methods that are repeated a few times.

In fact, how about this - Clone Count, Lines Affected, Total Lines (count * lines)

DbSet.Add returns the argument. AddOrUpdate should too when only one entity is supplied.

Allow something like this in c#

switch(NumDays)
{
case > 5 :
do this
break;
case <=5
do that
break;
}

I know that an if statement caters for this but i would like to do it in a case statement

C++0x final is out,
please add full C++0x support in VC++ compiler

Currently, wenn an Exception instance has some data in the Data attribute, it is not possible to to inspect this data through visual studio.

Please add a sensible display (like for other dictionaries) to the System.Collections.ListDictionaryInternal, or at least a special case for Exception.Data.

i want to manage javascript methods and logic per page, like the code behind (you can union all of them later on runtime
managing js methods in a central page is a big mess!

please include a template parameter for intelisence suggestion on a function writing time.

e.g.:
1. write "template<class A> void f(A".
2. write "&"; it's to the reference of the type A.
3. oops! it changed to "f(abort&" from "f(A".

the problem is suggestions of the intelisence are not included type A.

it's bad for an user experience. I want write through with intelisence.

(Entering a suggestion causes lots of hang-ups)

Re the V11 development interface (Showing "Visual Studio" in the top band):

In order for a pictogram (icon) to be communicative, it only requires to be visually discriminating. Packing in a lot of graphic detail is non functional, causes visual information overload, and defeats the object.

Zach.

Instead of:
internal class chi
{
public readonly char ch;
public readonly int i;
public chi(char ch, int i)
{
this.ch = ch;
this.i = i;
}
}
public static int strspn(this string str, string charsToSkip)
{
return str.Select((ch, i) => new chi(ch, i ))
.Where(c => charsToSkip.IndexOf(c.ch) < 0).DefaultIfEmpty
(new chi('x', str.Length)).First().i;
}

This:

public static int strspn(this string str, string charsToSkip)
{
return str.Select((ch, i) => (ch, i )[classname="chi"])
.Where(c => charsToSkip.IndexOf(c.ch) < 0).DefaultIfEmpty
(new chi('x', str.Length)).First().i;
}

The Javascript Parser VS2010 extension is awesome! I was able to easily dig into tons of OTHER people's cryptic Javascript code. The code as humanly minified to reduce page size. This capability needs to be integrated into Solution Explorer just like Solution Navigator Power Tools extension. The productivity will be amazing! Also, the ability to Mark (star/color/flag) a method is really great too!

I think vs needs something like maven or nuget pre-installed

i need to create new win ce application, because producers are still producting new win ce devices and our customers use them. so i cannat devolop in .net 4 and over vs2008, help me !!

After adding nuget packages to my solution, they should be referenced by in the solution explorer such that when I right click my solution and choose to check-in it will also check in the packages folders so that the references are updated for all developers. Currently this requires checking in from the project root through Source Control explorer or the file system.

In Team Foundation Services Preview there is a very nice Sprint Burndown chart.
What I miss is a Release Burndown. I have a backlog with 100 stories for release 1.5 of my product. I would like to see a v1.5 burndown.
If I place sprints under v1.5 iteration path I can see a 1.5 backlog but the chart to the top right only shows Velocity over sprints. I would like to see 1.5 burndown.

Thanks,
Simon

Much like the Run Tests After Build; continuous testing should run tests on each save.