Home Dashboard Directory Help

Visual Studio 2012 - NetApp Ontap 8.1 by FernandoMora


 as External Help for as External

Sign in
to vote
Type: Bug
ID: 773415
Opened: 12/4/2012 6:26:20 AM
Access Restriction: Public
User(s) can reproduce this bug


We are using VB 2008 Express Edition SP1 in a classroom environment (under Windows 7 64bit, Windows XP 32bit, and Windows 2003 Server under Terminal Services).

Using new (or old projects) we are finding code changes (e.g. changing a variable value) isn't reflected in the debug code.

For example changing the constant "0.5" to "1" in the code line below isn't reflected when the debugger is run

lblVat.Text = Val(lblSubTotal.Text) * 0.5

The projects are stored on a network share (and this locaton has been set to be fully trusted in .Net) - the only change has been a migration to the storage NetApp SAN from a FAS270 to FAS3240 everything else seems to work.

It seems that on the new storage system (running OnTap 8.17) that the files in \obj\debug folder aren't being updated when the debug tool is used.

in partilcular - <project>.exe and <project>.pdb timestamps aren't changing

Deleting the entire obj folder between debug runs seems to be a workaround.

We've escalated this to our storage vendor and their Microsoft specialists, but i was wondering if anyone in the community has any insight into this?

Under VS 2012, running clean solution before debug worksaround the issue.

However under the express edition this doesn't seem to work
Sign in to post a comment.
Posted by FernandoMora on 12/4/2012 at 11:47 PM
OKay I accept that the original issue was seen in VB 2008 EE however i do go on to state that the behaviour is reproducable in Visual Studio 2012 Premium hence the submission of the feedback.

I'm disappointed that the issue has been closed outright.
Posted by Microsoft on 12/4/2012 at 10:46 PM
The product team itself no longer directly accepting feedback for Microsoft Visual Studio 2010 and earlier products. You can get support for issues with Visual Studio 2010 and earlier by visiting one of the resources in the link below:
Posted by Microsoft on 12/4/2012 at 6:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.