I am not sure what the gotcha microsofti have in their own mind but it's going useless in some cases.

1. 2008 interface is easy to use. 2010 have worst experience with performance 2012 come with their own problems.

2. forget the sense of common and usability. 2010 is hard to use and 2012 are neither not look so cool. yeah, color themes is just excuse. really not great.

I like the "Preview" tab that opens up at the right-hand side as you're navigating among source code files. Great idea, thank you! It is useful for using 'Go To Definition' without causing clutter. As a further convenince for navigating source code, please also forget the regions which have been expanded. It's always nice to open a code file and have all regions tidily collapsed. While navigating using the Preview tab, I do not wish being bothered to collapse the regions after use.

When I invite a member to a TFS Project or collection. Send an Invitiation email to the new member of the team with a link to the project.

I am amazed at something with my Vs. When I install them (in last month) first it show me professional then premium for check the matter I open Vs then splash screen show me premium but it's ultimate (yes i install ultimate Rc for try)

I have take update of july already but it's tell me to do today again. Is this happen because yesterday I reset my vs settings.

I could like to inform you about my idea. I want to make an Historic Map and to watch the sky and the universe from a telescope with my WPF program. I would like to make this for astonomy and for progress of mathematics.

Please implement alignas keyword , so code like this compiles

// every object of type sse_t will be aligned to 16-byte boundary
struct alignas(16) sse_t
{
float sse_data[4];
};

Now it compiles as

// every object of type sse_t will be aligned to 16-byte boundary
struct __declspec(align(16)) sse_t
{
float sse_data[4];
};

In Visual Studio 2010 it was possible to make a define,
In Visual Studio 2012 rc is not, because alignas is treated in the headers as c++ keyword.

Add in C# the "WITH" keyword from VB. I'm tired of typing MyWonderfulObject.Height = 9;
MyWonderfulObject.Width=10;
MyWonderfulObject.Might=Moderate;
MyWonderfulObject.Color=Color.Red;
etc
etc.

I would like this:

With MyWonderfulObject
{
.Length=10;
.Height=10;
.Color=Color.Red;
}

I suggest using a toast or notification with a friendly message when app crashes unexpectedly and before or after it closes. Instead as of today when the app just closes down and the user is left with a question mark to what happend.

It could be just as simple as "The app closed down unexpectedly", visible for a few seconds.
And the toast / notification could for example contain an question mark-button pointing to some help section explaining why the message appeared and what possible solutions there is.

Maybe this could be configurable, but enabled by default.

TFS consumes a lot of memory usually. Therefore, using Visual Studio to connect to TFS makes CPU 100%. When I make it offline , everything is working properly. I hope Visual Studio can have “Go Offline” option besides “Go Online”

when I put second style in visual studio first is removed.

Ability to dynamically link to .net or native dlls at runtime.
E.g. if the library has been altered, it will cause exceptions to be thrown. If you could check the library version before using it, you could have error messages of your own or better handling.

have an option to control how the collapse button work in Solution Explorer -- currently it collapse everything, would be good to either "collapse up to file", "collapse up to project", "collapse up to folder" or "collapse up to solution (current default)" etc
thx

The current implementation of LS does not expose the Computed Property - At the very least last computed result should be exposed as a Property within the OData endpoint.

http://social.msdn.microsoft.com/Forums/en-US/LightSwitchDev11Beta/thread/bb8ffe0a-8239-429c-a528-d2cbfa850f42

First, there is documented UX research showing that words written in all caps are ****** to read and recognize quickly. Please change the top menu bar from all caps back to typical capitalization! I find the menus so hard to read!
Second, I don't like the lack of color differentiation on the Solution Explorer.. Folders, Forms, Script files etc are all the same color, making it extremely hard to differentiate between them quickly. Again, use of color is a basic UX principle, why abandon it?

If you type:
Dim A(0 to
intellisense suggests Today which it selects by default if you press space. I know it can be shortened to Dim A(n) but still....

I have a TextHelper that does this, but it is a very long to type String.IsNullOrEmpty() when you have compound if statements.

// existing compound if statement
if ((this.HasGateway) && (!String.IsNullOrEmpty(connectionString)))
{
}

// Much shorter to type
if ((this.HasGateway) && (!String.Exists(connectionString)))
{
}

I'm constantly sending emails to clients and colleagues from Visual Studio but each time it creates the email it uses Times New Roman as the font within the email; however I've set Calibri as my default font when creating new emails. I'm having to constantly go and reformat the additional text and feedback to the font I've set as my default within the emails.