I'm using the Performance Wizard in Visual Studio 2010 Ultimate. I have selected Instrumentation and the type of profiling JavaScript for my Web Project. When I Launch the wizard I receive the error:
PRF0005: Launch Error Unable to execute (iexplore.exe).
Any Ideas anyone. Thanks In advance.
Got same error on C# desktop project. If WebProject have manifest, possible reason is
<requestedExecutionLevel level="highestAvailable" uiAccess="false" />`
so solution is
<requestedExecutionLevel level="asInvoker" uiAccess="false" />`
Sounds like a firewall problem, Either disable it or make an exception in your firewall. If you have McAfee, Check to see if you have McAfee Host Intrusion Prevention turned on, check activity logs to see it there is a time that matches the time you tried to launch the wizard.
Related
Since today I can't debug any applications anymore.
If I want to start the debug session, I get the error message
error while trying to run application: invalid pointer
It doesn't depends on the project, this behaviour appears in every project/solution.
What i've already tried:
Reset VS settings
repair Visual Studio
complete reinstall of visual studio
Changed Build Platform to x86/x64
Enabled native code debugging
If you press Ctrl-F5 to run the application, you won't get the error and the application will start, but you can't do debug, so this isn't a real solution.
The only way to solve the problem is to update Visual Studio: I had the same problem (WPF application), which was solved by the Microsoft Visual Studio 2013 Update 4.
If you're running VS 2013 and get an error that's pointing to the body tag, try adding this to the web.config under
<appSettings>
<add key="PageInspector:ServerCodeMappingSupport" value="Disabled" />
That key disables browser link which currently isn't playing nice.
I have a solution where i have 8/9 projects.
everything was working good and suddenly, I started to get an error when I start to debug. and it says
Unable to start debugging.
If I close visual studio and run it again, it works in the first try.
and after that it stops working.
In the configuration manager it is set to "Any CPU".
I tried many thing with no luck. Is there any help??
this is how the error looks like..
I got similar error:
"Unable to start debugging. Check your debugger settings by opening
project properties and navigation to 'Configuration properties --> Debugging"
I have solved it by setting :
Properties--> Debugging --> Working Directory
to $(ProjectDir)
As it's an MVC web application, there's a couple of things to check. Firstly, are you sure the web project is set as your startup (this catches me and a couple of others in my office out from time to time)?
Secondly, where are you hosting the project? Are you using Cassini, or are you hosting it in IIS while you debug? If so, check IIS and make sure that the site is started, there's no issues with the AppPool, etc.
Finally, one way to try is to actually press Ctrl+F5 to run without the debugger attached, I often find that IE will then actually display an error that's causing the issue.
I have a Visual Basic 2010 Console application,
That I created a couple of months ago,
I needed to prevent administrative request,
So I just Went to “View Windows Settings”,
And changed the app.manifest “requestedExecutionLevel” to:
<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
And now the executable has a special administrative icon that differentiates it from others.
The code worked well and did not ask me for administrative rights,
But now it is asking me!!
Does someone know why?
But now it is asking me!!
That's entirely normal. When you use "requireAdministrator" then Windows is going to display the UAC prompt to warn the user.
What was not normal is that it didn't display the prompt before. Otherwise easily explained, Windows only displays the prompt when necessary. If you are already running Visual Studio elevated for example and press F5 then you won't see it. The only surefire way to not get the prompt is to use "asInvoker" instead of "requireAdministrator". But then of course your program won't run with admin rights. If you need them then your program will fail.
If your real question is "can I get elevation without a prompt?" then the answer is: absolutely not.
I am suddenly unable to debug in VS. I am developing an MVC app. I made no changes whatsoever to application settings. I simply modified a property in a class like I've done many of times.
I am getting the popup
Debugging Not Enabled
This page cannot be run in debug mode because debugging is not enabled in the Web.config file. What would you like to do?
(.)Modify the Web.config file to enable debugging.
( )Run without debugging.
I have compilation debug="true" targetFramework="4.0" in my Web.Config file. Clearly debugging is enabled. I've restarted VS, rebooted, but same thing.
When I say immediately, I mean from one debug session, to another within about 10 minutes. Any ideas why this is happening?
Copying somebody else's fix to your question, see if that helps:
Fixed this by registering/installing ASP.NET 4.0
c:\windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i
If you're using 32 bit change Framework64 to Framework.
Link is Unable to start debugging on the web server
Try see if it works
I'm running Visual Studio 2008 on Windows 7 64-bit. I'm logged in as administrator, and I'm running it as administrator, but the program I'm working on fails with access denied when I call a restricted API. If run the program from Explorer with "Run as Administrator" it works.
I was under the belief that Visual Studio 2008 debugs programs with whatever rights Visual Studio 2008 itself is running with. As it stands I can't debug my application due to this, and I'm at a loss as to what's going on.
This works for Visual Studio 2012.
Create a manifest file: right click on the project and select "Add New Item", select "Application Manifest File". This will add a file named app.manifest to the project.
Edit manifest file: set attribute level for tag requestedExecutionLevel to requireAdministrator.
Now your program will always require admin privileges, wherever it is executed. If launched by Visual Studio debugger, it will prompt you for restarting Visual Studio as administrator, if needed.
It's best to run Visual Studio 2008 as administrator. Moreover, it's good to change your application's manifest settings to require administrator privileges. You will be prompted by the system to elevate to system administrator each time you start your application, and when running under Visual Studio 2008 the IDE will offer you the elevation before start of debugging.
To change the setting, open project properties and go to Configuration Properties → Linker → Manifest file → UAC Execution Level.
I found the answer. It turns out that it is, in fact, a manifest issue: by default if you have a manifest you need to set the appropriate administrator privilege.
The default is asInvoker, but that doesn't work if you need elevated privileges; you instead have to set it to requireAdministrator in the manifest properties.
Run Visual Studio 2008 as administrator.
I had a case where I put in the
<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
settings (described by another answer at this post)........and did not work.
I found another tip (seen below)...and unchecking that option allowed my code to work.
Try going into the project properties, and under the "debug" tab,
uncheck "enable the Visual Studio hosting process" and see if that
fixes your problem.
(from https://social.msdn.microsoft.com/Forums/vstudio/en-US/b5c4da93-5d64-442e-af28-df6d10765538/debug-as-administrator?forum=vbgeneral)
So I needed the app.manifest settings AND the "uncheck".
My testing with Windows Vista and Visual Studio 2005 showed that when you use a host process, the behavior under the debugger depends only on how you launched Visual Studio and not on the manifest (or lack of manifest) of your application. When Visual Studio is launched elevated, the behavior depends only on the use (or not) of a host process, not on the manifest. This is probably still true with Windows 7 and Visual Studio 2008.
Also, have you tried launching the application outside Visual Studio and using Attach to Process?