I'm debugging my application which has drag-n-drop features in Visual Studio 2010. I have to run the IDE in privileged mode since some of my project required so.
My problem:
I can drag-drop when run the .exe file normally (run from Windows Explorer (WE)) but when debugging in VS2010 I cannot do drag-dropping between my app and WE.
I tried to open WE in privileged mode but still cannot debug either.
Do you have the same problem? If you do, do you have any work-around for it? Please share.
Another workaround is to run the debug binary from Windows Explorer and attach to the process from within Visual Studio via the "Tools" or "Debug" menu. I have verified that drag events are received in the debugger when using this approach.
This is by design, an aspect of UAC called UIPI (User Interface Privilege Isolation). It prevents a non-elevated process from hijacking an elevated one through Windows messages or drag and drop. It protects against shatter attacks. There is a way for the elevated process to explicitly allow messages with ChangeWindowMessageFilter. But not for drag and drop, it isn't message based.
There is no decent api-level workaround for this, it has to be done declaratively. The manifest for the program needs to use uiaccess = true, be code-signed with a certificate from an approved authority and be installed in c:\windows or c:\program files.
actually i working on a Application that is going to be build for windows 8 surface and desktop but we want this not to be on store but as a business solution. but i want my app to be tested by testers but i am not getting how to provide then my full package so that they can test it. any idea is appreciated.
In Visual Studio 2012, with your Windows Store project selected, go to Project -> Store -> Create App Package...
Tell it that you do not want to upload the app package.
This will create a folder for your app that includes the .appx, the .cer, and a .psd (PowerShell script). Zip up this folder and send it to your testers. They just need to run the PowerShell script by right clicking it and clicking "Run in Powershell...". It will prompt them for a Developer's License (which they will need), but this will be retrieved automatically after signing in with their development account.
"Unable to start debugging 'C:\Windows\System32\WWAHost.exe'. The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging."
Searched for similar posts, but didn't found one. If duplicate just inform.
I am not trying to connect to any remote machine. Just testing on my local machine.
Is there any way to solve this issue. (I'm using Windows 8 Enterprise 64-bit, just a javascript project)
Problem solved. Installed Remote tools update from here and working fine. Thanks for responding. Closing the topic.
I had the same problem. I fixed it by changing properties/compile/target platform to x86 instead of Any CPU. It solved the problem in my case. Hope it helps.
This happened to me just now when I had a website set up in IIS for mydomain.com, and set my project's start up url (Local IIS) to mydomain.com, and then launched the project before remembering to add a record in the host files for the domain:
127.0.0.1 mydomain.com
This got me for a good hour before I remembered I never set the record. Adding the record fixed it right away.
Windows 7 x64, VS 2012
In my case, the Remote Debugging Monitor component was installed and the app was clearly configured to debug locally in settings. This was a WinForms app upgraded from VS 2008, .NET 3.5.
Turns out it was the Windows Firewall. By directly running:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe
A firewall dialog appeared where I could allow msvsmon.exe to run. After a VS 2012 re-start, debugging (locally) was fine!
Ensure you have Local Machine selected in this drop-down menu:
Windows 7 x64, VS 2012, VB.NET
I fixed it like this:-
Create a shortcut on your desktop to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe".
Right-click shortcut and select "Properties" from the dropdown menu. Select the "Compatibity" tab, tick "Run this program as administrator" and click OK
Create a shortcut on your desktop to "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe".
Right-click shortcut and select "Properties" from the dropdown menu. Select the "Compatibity" tab, tick "Run this program as administrator" and click OK.
To start VS2012:-
Double-click the msvsmon shortcut icon (that you created above, to launch msvsmon). Wait for the "Visual Studio Remote Debugging Monitor (Administrator)" window to display before continuing ...
Double-click the "Visual Studio 2012 Professional" shortcut icon (that you created above, to launch VS2012)
In VS2012, ensure standard toolbar is visible.
In VS2012, ensure "Solution Platforms" dropdown (on standard toolbar) is visible and set to "x86".
and debug now works (for me anyway) ...
However after 15 minutes or so, debug may stop working and you may get the msvsmon error again. If that happens, simply close VS2012 and msvsmon and then start again (from "To start VS2012:-" above) ...
Myself and several other developers have been trying to look for a solution for this problem for about 3/4 hours as Visual Studio crashed then this error would occur (twice in 2 days). I then suddenly (after a lot of debugging and trying other suggestions and headbanging) I somehow realised that the file which was highlighted had changed and when I was trying to debug was not the MVC app project, once I changed it to my project's one it then worked.
Hope this helps and saves people from hours of pain!
I also got this error, I usually run sites under a named user (which is also a database user) and forgot to set the Application Pool. (parliament's answer also helped me)
For me this worked in VS2013:
Save your work, close Visual Studio then reopen your project
I encountered this error as well.
The cause of mine was that I had accidentally emptied out the following property
Properties->Debugging->WorkingDirectory
Changing it to:
inherit from parent or project defaults
Solved the issue.
If you are using Microsoft's Azure, try attaching manually the debugger:
I have outlined the steps in the following answer:
https://stackoverflow.com/a/35738995/1057052
In the Windows 8 Start screen, I noticed that there is an Uninstall icon that appears at the bottom if you right-click on an app. For the apps that I developed, if I click on the Uninstall icon, it opens the "Programs and Features" dialog. Ideally it should instead directly launch my uninstaller. Does anyone know how to do that? Is there some registry key I need to set to associate Start Menu shortcuts with uninstallers?
I use various technologies to make my apps (e.g. Qt, C#, Visual Studio setup projects, NSIS). On Windows 7 and below, my installers put shortcuts in the Start Menu. On Windows 8, those shortcuts are displayed as a little square in the Start screen. So that shortcut is the object I am right-clicking on. Is there some way to add uninstall data to the shortcut file itself?
Tiles for desktop applications do not automatically uninstall like tiles for store applications. Choosing 'Uninstall' for a desktop applications tile launches the Add / Remove programs experience as you pointed out. This is by design.
I have a WinForm program developed in VB.Net with Visual Studio 2005. The program needs Microsoft Office Runtime installed atleast on the computer to allow the application to run without any errors.
Is their a way to check the computer to see if the minimum of the Runtime or Microsoft Office is installed on the computer? If either isn't I would like to display a message to the user on the startup of the application that states to atleast go to Microsot's site (I have full link to Runtime Download) and download the runtime for free.
Or is their a way to include the runtime as a component with my install for the application so if it isn't installed on the computer already it will install when the application is installed?
Thanks
If you more specific details please specify the exact runtime you are interested in. Office has lots of them.
For a launch condition you can try this approach:
select your setup project in solution explorer
go to its Launch Conditions Editor
create a registry search which determines if the runtime is installed or not
create a new launch condition
add the registry search property as the condition
This way the installation stops and shows the message you specify if the search doesn't find anything.
Another approach is to include the runtime as a prerequisite:
select your setup project in Solution Explorer
right-click it and select Properties context menu
click Prerequisites button in the property page
check the prerequisite you want
If the prerequisite you want is not in this list, you will have to configure it manually.