4 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Patrick commented  ·  November 13, 2012 9:13 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  You can download this extension: http://visualstudiogallery.msdn.microsoft.com/a83505c6-77b3-44a6-b53b-73d77cba84c8?SRC=Home

  It will allow you to run VS as Administrator with medium integrity level to allow d&d. Good thing is that you will have admin rights, downside is taht you won't be able to attach to processes run by other users - otherwise it also allows you to run elevated windows explorer from which you can always do d&d

• Tilo Hillenbrand commented  ·  July 11, 2012 1:24 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  That is an essential feature for me which I cannot believe that it doesn't work anymore.
  I'm developing a web application and thus VS2010 has to run in Admin Mode. My company switched from Windows XP to Windows 7 and now drag and drop is blocked in VS2010 run as Admin. I very often just open the significant logfiles like this and am a little bit confused about so much "security".

• Alan Robertson commented  ·  February 22, 2012 8:38 a.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  As a driver developer, I also often am required to run VS 11 as admin to debug system processes. This regression causes a significant productivity hit for me.

  The behavior that I Expected to find was that drag and drop would be blocked from any processes running at a lower integrity level, but allowed when both Visual Studio and the app from which files are being dragged are running elevated.

  However, the Actual behavior is that VS seems to go further and block drag and drop even when the other app is also running elevated. (As explained above, we develop drivers and simply must run VS elevated in order to debug system processes, etc.)

  This appears to be an unnecessary restriction. Drag and drop is an important productivity feature that has been supported since at least Win95.

  The following blog entry discusses UIPI, UAC, MIC, and best practices associated with drag an drop implementations. It says, "The best solution is to only use drag and drop between the same MIC levels." Please fix Visual Studio so that it follows this less burdensome, yet still very secure recommendation.

  http://blogs.msdn.com/b/patricka/archive/2010/01/28/q-why-doesn-t-drag-and-drop-work-when-my-application-is-running-elevated-a-mandatory-integrity-control-and-uipi.aspx

  Thanks for your time and consideration.

  P.S. I also have a bug on this in connect: http://connect.microsoft.com/VisualStudio/feedback/details/709552/vs11-regression-drag-drop-fromwindows-explorer-of-files-to-open-fails-intermittently

• AndrewDover commented  ·  August 18, 2011 5:33 p.m.  ·  Flag as inappropriateFlag as inappropriate  ·  Delete

  I just set a calendar item to remind me to try this for Windows 8 and VS Next. Anybody care to bet that it will have been fixed by then ?