In production solutions when there many threads are executed. ThreadPool, Tasks and Threads and others
Debugging of code is pain as quite often it is slow, you have to go step by step very deep, by pressing F8 into, and usually when you are close to line where is bug, after press F8, debugger behave like you presses F5.

This means you have to do all process again.
Usually it happens, if other threads in time of debugging failing, by time out error. (WCF Time outs, or Socket timeouts). But I expiriences it quite often randomly.

My idea is:

Debugger in VS2012 should be improved to respect user, name it for example like : USER MODE

Debugging in USER Mode means that debugger begin to understand that user begin special session, when he don't want to be interrapted by

1. Time outs
2. Termination of active thread. Must be not terminated
3. Error, like DEBUG.FAIL from other thread which popup every second
4. Switch to othere thread without prompt, like when you debugging one thread only
5. Watch errors, when some value can't not evaluated by time outs and whole VS2012 freezed.

List can be exptended, but idea is that Microsoft take some big real producation service: WCF, Sockets, COM, C++, C#, Interop and will make debugging of this service comfortable for people.

Visual studio used to have a kick *** interface. However, everything about the 2012 interface looks.. amateurish.

-The icon looks like something a 3 year old did.

-The lack of depth makes the whole thing jump into my face.

-The upper cased menus are screaming at me (try posting on a forum in all caps... see what the response is).

In a nutshell, whoever designed the interface needs to go back to the grade school I'm sure they dropped out of and finish their education. Maybe get a job at a fast food place running a cash register... Because they have zero talent for making a good looking UI.

We have incredibly high resolution monitors that can render beautiful images. To go all grey (or black) is such a step backwards that I can not believe this really passed user testing.

You'll notice that iPhones went from this type of boring UI and changed to using high res displays with lots of good color. You should have also noticed that this was exactly what people wanted.. and they sold like hotcakes.

In the old days people scrambled to get color monitors just to get away from the ho-hum grayness of working with a machine all day. To send us backwards is irritating at best and abusive at worst.

Please, make Visual Studio look good again.

I don't care about metro, or whatever your calling it these days. I figure it'll take 3 years for you to figure out what a mistake that is and fix it. In the meantime, let me keep the Win7 look.

Note, I wouldn't post anything if I didn't care. I do. I want to use the best. This, well, isn't. It's not even a "good effort". Instead, it looks like something that was slapped together at the last minute.

I can't figure this out, and nobody at Microsoft has been able to tell me either despite spending 250$ to not find out.

In VS2010 with Phone SDK 7 on Win 7 I was able to set breakpoints and debug javascript. It worked well and is absolutely necessary if you want to build cross platform code.

Now I migrated up to Win8 and javascript debugging doesn't work at all.

I has since given up on developing for WinPhone and will target the others because they have development environments that work.

What is going on MS?

Why can't we debug js, and how come nobody in the company knows what is going on with this?

Spent 250$ to open a Micosoft Support Case and got zero info, zero value, and zero ability to debug js.

James