>>>I don't use 2010 because it's buggy in C++ code generation in V10.
>>Interesting. Out of curiosity what problems did you find in 2010
>>that were not present in 2008 ?
>
>
>I worked on a large Java project that used JNI. We compiled for 32-bit and 64-bit VMs running 1.6.x and 1.7.x.
>
>In the V10 toolset my boss insisted I use, as development progresses, code that had been working fine began throwing exceptions. It was due to internal compiler or linker errors because literally nothing in the newly errant code had been changed -- no functions, structures, classes. It would just stop working properly. Rearranging the functions would almost always fix it.
>
>The incremental linker would periodically not work for the same reasons. Rearranging the functions would fix that about half the time.
>
>When rearranging the functions did not fix it, adding a few bogus locals, or inserting an extra blank line or NOP instruction (k = k) here or there would fix it.
>
>These all happened in V10 toolset, and went away simply by recompiling unchanged code in V09. The IDE otherwise was nice. I didn't like the darker blue theme as I have difficulty with my eyes and dark content for components of the background. But that was minor.
>
>As such, I used the V09 toolset for all development, and then fixed the V10 toolset "bugs" when ready to release a version. That way I had incremental linking and edit-and-continue debugging in 32-bit Java JNI code.

I'm confused. I thought we were discussing C++ on .NET. AFAIK VS doesn't support Java ?