I am teaching myself how to build websites using asp.net core/mvc6. For the same, I installed VS2015 update 3 community edition. I have extensive background with C# and .NET Framework, but not much with web applications
I am just trying to create a simple project and start debugging, but the debug mostly (say 90% times) fails with the below message
An error occurred attempting to determine the process id if the
{APPLICATION} which is hosting your application
You can reproduce my issue by following the below steps:
Create a new "ASP.NET CORE" application in visual studio, using default selections
Build the project successfully without errors or warnings
Click the "Start Debugging" button
I get the "Debug is starting" progressbar,
After that it mostly fails but sometimes succeeds in starting the debug session. When it fails, I get the below message.
When it succeeds I first get a dialog complaining about 64 bit debugging and then the debug session starts fine.
I have tried the below with no luck
I can run fine the website through Visual Studio without debugging.
I can also debug and run fine a .NET core console application from within VS.
I have Avira (antivirus) and ZoneAlarm (Firewall) installed on the machine where I am trying all this. I have tried exiting ZoneAlarm and stopping real-time protection on Avira and set my UAC to not prompt, and then try debugging, but no luck. I cannot uninstall those items for trying.
I have tried repairing VS2015.3. I have also tried uninstalling and installing cleanly VS2015.3.
If I follow the below steps, the debugger starts fine (sometimes with the 64 bit debugging warning). I am sure that attaching the debugger to the running website would also work fine:
Start Debugging using F5
Right click IIS Express and browse to the application quickly
The debug works fine, if I use the kestrel web-server
I have tried using ASP.NET Core 1.0.1 and 1.1.0.
Using IE instead of Chrome did not make any difference
I even tried using VS 2017 RC2
I would like to be able to debug without any "hacks" and also, get rid of the 64 bit slowness complains
It works fine in my VS2015.3 (version 14.0.25431.01) based on your steps and successful no matter how many times I debug it.
Please check your .NET Core version to make sure it is the latest version first. The latest version should be NET Core 1.0.3. You could get it from this link: https://www.microsoft.com/net/download/core
And according to the message when you could successful debugging, your are using some 3rd party networking software. So please make sure you closed all other programs when debugging.
In addition, I found you are debugging using Chrome. Please choose Internet Explorer to confirm whether this issue related to the Chrome.
Related
Attempting to launch the SQL Server Management Studio set-up exe leads to an icon briefly appearing in the taskbar, before disappearing without any further screen showing up. The task manager does not show any running instance for the installer either.
I have tried various versions of the SSMS installer executables posted on Microsoft's official documentation for SSMS, including version 18.8, 18.7.1, and 17.9.1.
Also tried updating the .NET framework, as suggested here (Why the SSMS-setup-ENU for version 17.8.1 isn't running?), but the latest version is already showed as having been installed.
I did a soft and hard reboot both, without success.
Confused as to how to proceed and install the software now. Any help would be appreciated.
I've recently upgraded my OS to Windows 10. I have a very basic Silverlight 5 application which gives me Unable to start Debugging. The Silverlight Developer Runtime Not Installed. Please Installed a matching version error in VS 2010 whenever I am trying to run the project.
I have :
Target Silverlight version is set to Silverlight 5 in web project.
I have installed Silverlight SDK, Silverlight5_Tools with SP1 installed & Silverlight Runtime which is 64-bit.
After doing all these steps and going through many online posts, still I'm unable to resolve this issue.
My Doubts are :
Do the Windows 10 upgrade has anything to do with this situation?
Windows 10 comes with a new browser Edge, is this because of this browser? Like Silverlight compability.
Again I am not sure but these are my doubt. Any suggestions?
Do you have a 64 bit OS ?
If so - uninstall Silverlight (developer!) and make sure you install the silverlight.exe (developer!) not the 64 bit version.
That worked for me.
HTH
Go to the properties of the Web folder start project. Click Web on the left tab. Unclick Silverlight in the debuggers.
Not a total solution but at least it allows you to debug other portions.
I had this issue and Uninstalling and Reinstalling didn't work.
Error in debug mode (F5 Debug solution configuration) was "Unable to start debugging. The Silverlight Developer Runtime is not installed"
In Debug configuration I would get the above error but finally I put the solution into release mode and it worked - then back to debug mode and everything worked without error.
Seems like a really odd fix but sure enough closing and re-opening the solution everything works now - Same install procedure as OP.
Another thing that's interesting is, the Debug only works in Chrome. If I target IE or edge I still get "Unable to start debugging. The Silverlight Developer Runtime is not installed"
I uninstalled Silverlight and then installed Silverlight_Developer.exe. I also switched default browser in Visual Studio to Internet Explorer (I have Edge otherwise which won't work...).
Nice to see some more people also using Silverlight these days, hehehe.
This is a really old thread, but I just ran into this issue with a project. I was getting the message that the Developer runtime was not installed, but in fact it was, and another similar project ran just fine on the same machine with the same version of VS 2015.
The fix was to ensure that the startup project is the WEB project, not the Silverlight project. Somehow, the default startup project got switched to the SL project. After I switched back, then it worked just fine.
I have an intermittent issue when trying to debug local IIS sites.
Visual will hang and eventually displays the error:
The web server did not respond in a timely manner. This may be because another debugger is already attached to the web server
If I wait a minute and hit "Start Debugging" again it will work (sometimes I may get the error several times but it eventually works).
There is nothing in the Event Viewer around the times I try to debug.
The app pool is .net V4.0 Integrated.
I am running Windows 8 Pro with IIS 8 and Visual Studio 2010.
Also its a site using EpiServer 6 R2.
I have tried IISReset, stopping/starting the site, closing and reopening Visual, rebooting my machine. None of that seems to make a difference, its hit and miss whether the solution will debug or not.
Once the solution is debugging, it runs fine without issue. Until I stop debugging and try and start debugging again.
The site runs fine in all other aspects, its only when I try to debug.
So... I never fixed this issue, but have since upgraded to a solid state drive. So I now have a fresh install of Windows 8 Pro and Visual and the issue has not resurfaced.
All the sudden started getting the following error while trying to debug a worker role:
"Windows Azure Tools for Microsoft Visual Studio
There was an error attaching the debugger to the role instance 'deployment16(360)blah blah' with Process Id: '8780'. Unable to attach. The Microsoft Visual Studio Remote Debugging Monitor has been closed on the remote machine."
Restarting Visual Studio and the machine do not help.
As you start getting this problem all of sudden in your development machine something must have changed and it is mostly due to some of the OS auto-update and/or some application update you installed in your machine. There could be any random reason for this problem however if I would have hit the exact same problem here is what I would do to troubleshoot such issue:
To start, first thing is to just check it is not an application specific problem by creating a base app from web/worker template and see if that exhibit the problem.
If you have installed new release Windows Azure SDK 1.7 check with both SDK 1.6 and 1.7 to verify if both exhibit the problem.
Check if your could debug IIS based application as well outside Compute Emulator. This will isolate if the problem is specific to Windows Azure development Fabric or bind to your IIS itself.
If this is IIS specific issue, Check IIS configuration for all enabled functionalities, try resetting Application Pool configuration, running "ASPnet_regiis -i" etc to fix the issue.
If it is Windows Azure Computer Emulator specific, I know sometime OS updates may make application unstable so in that case, I will re-install .net 4.0 and VS2010 SP1 again respectively. (This does help so many time) then re-install Azure SDK 1.7 completely.
Such random problem mostly occur due to some change in your machine configuration, so restoring the VS2010 and the re-installing all other application does help to solve problems.
If you have an exception in the role's OnStart() or in Application_Start() that the debugger doesn't pick up, you may also receive this message. Application_Start() errors are especially pernicious because the debugger doesn't attach to the web process until after this method returns.
If you are wedded to cloud specific classes such as RoleEnvironment and cannot make the web role a startup project, you can use Ctrl-F5 to run the cloud project without debugging. With some luck you'll get a yellow screen of death to show you the true error.
Avkash covers the points.
I had the same issue recently. I set my web project as start-up rather than Azure and I discovered that that web project didn't actually run. Turned out somehow when of my projects was compiling for X64. I changed that and it worked.
I am attempting to create a simple silverlight 4 application in visual studio 2010 ultimate running on windows 7 x64 and I am unable to use f5 debugging.
The error is:
Unable to start debugging. A fatal
error occurred. For more details,
please see the Microsoft Help and
Support web site. HRESULT=0x8004005.
In researching this I see a few people who say that reinstalling the developer runtime will correct the issue. I have done this several times but the issue remains. I have also tried running without debugging (works fine) and then attaching the debugger to the ie silverlight process, however this doesn't work either (it only breaks on the 'throw new Error(...)' javascript eval code.
I can do f5 debugging of asp.net projects without issue.
I have looked at several other silverlight debugging posts and either their error is different or their solution did not work for me.
This appears to have been caused by a windows phone 7 tools beta. By uninstalling it and installing the rtm version, the issue went away. shrug