Visual studio 2017 cannot debug .Net core web api? - asp.net

I created a new .Net 2.0 web api project. And then click the "> IIS Express" button to test it. However, I got a popup of Windows Explorer.
Windows Explorer has stopped working
A problem caused the program to stop working correctly. Please close the program.
Close the program
Debug the program
Another window pops up after close the window.
Unable to start program 'http://locahost:24175/api/values'.
Invalid prointer
However, "Start without debugging" works.

Seems like you deleted the default ValueController without changing your default route. Check this answer on how to change it:
https://stackoverflow.com/a/44731550/837623

Related

IIS Express in visual studio 2017 crashes when debugging app and selecting file input

I have a form with a file field.
In VS 2017 the upload doesn’t work and it returns the error: "The program '[19000] iisexpress.exe' has exited with code 4294967295 (0xffffffff)."
The upload operation when run from kills IIS Express, it basically evaporates. Any idea on how to fix this.
Thanks in advance.
ok, found the answer here: IIS Express stops suddenly when I click on a text box in my web app.
This did the trick:
The checkbox was clear in VS 2017.

Problems with .Net Core SignalR's HubConnectionBuilder in Tizen

I am developping a Xamarin.Forms app that should be compatible with Windows(UWP), Android and TizenTV. I am using .Net Core SignalR Client. The App works fine on Windows & Android but I can't get it to Work on Tizen (main Code is the same). Especially one line of code from signalR is not Working.
hubConnection = new HubConnectionBuilder().WithUrl(apiUrl+ "registration-hub").Build();
If it is excecuted in an Emulator with the Visual Studio Debugger the code just leaves the thread and doesn't continue after this line.
It doesn't log errors or anything else. If try to change the Exception Settings in Visual Studio i get this notification:
This debug engine does not support exception conditions. The condition(s) will be ignored.
I tried updating & downgrading packages but nothing worked. I can reproduce this in new empty .Net Tizen Projects.
I've just had exactly the same problem on my Xamarin forms project. For me, the fix was:
Start debugging
"Exception Settings" window
Click 5th icon: "Restore the list fo the default settings"

IISExpress shows up as host for browser in Visual Studio and messes up everything - how to get back to local?

All of a sudden after I installed Microsoft Edge on Windows 10 gd, Visual Studio is using IIS Express when debugging a web application and it is messing up everything.
How do I get back to normal, so that stupid IISExpress is not used anymore?
Go to the project settings and on the web tab is a drop down that allows you to choose which engine to use.
I went to Project > Properties > Startup Project and then set my start up projects to start the services I need and my project. This reverted my button back to just "Start".

Limited browser functionality when developing in Windows 8

Has anyone else run into this problem and resolved it?
I am developing with Visual Studio 2010 in a clean install of RTM of Windows 8. While developing an ASP.NET application and RUNNING it with the Debugger Attached, I can not click on HTML links in ANY application and have it open up a browser window.
I will be running(debugging through VS) my application in Firefox, and I can't click on links sent in Google Talk or Outlook.
If I stop the application from running, I can then click on those links.
I have also seen that while debugging, I am using jQuery Drag-N-Drop HTML 5 functionality in my application. I can't use that functionality while it is running under the debugger, it just doesn't work. This happens with all browsers (Chrome, Firefox and IE). But if I stop debugging, and run it without the debugger on, it then works.
Any ideas?
Try to disable the debuging for "Javascript" in Visual Studio 2012.

Visual Studio 2012 Web Publish on Windows 8 RTM Fails Browser Launch

I'm developing an ASP.NET MVC 4 site using Visual Studio 2012 Premium on Windows 8 RTM x64. When I right click on the web application and choose Publish, Visual Studio 2012 returns the message:
"fail to open url of 'http://.../'.
Exception:Class not registered"
The publish process seems to work correctly but it fails to launch the browser. This happens every time I try to Publish the site and it happens with Chrome (21.0.1180.79 m) or Firefox (14.0.1).
Furthermore, since the site isn't launching post Publish, I do it manually using Ctrl-F5. I'm able to navigate around the site normally, but if I right click on the browser's icon on the task bar to launch another browser instance, nothing happens. Once I close all browser instances, the browser task bar icon reverts to its normal behavior.
I'm not sure if these two issues are related, but the common theme here is launching a browser from Visual Studio 2012 causes unexpected side effects. The browser either fails to launch on Publish or launches with Ctrl-F5 but renders launching another instance useless using the task bar icon.
Any help is appreciated.
EDIT: I've re-installed the entire software stack (Windows 8, Office 2010, Visual Studio 2012, Windows Update, Chrome, Firefox). The above issues continue, unless I make Internet Explorer the default browser.
Thanks.
I filed a Chrome bug, it was a browser registration thing. If you uninstall and reinstall from a Download and be SURE to say Yes to the UAC prompt, Chrome will register Machine Wide, rather than User. That is required to launch as Admin. (HKLM vs. HKCU)
It appears this problem is much more widespread than the Web Publish operation. Anytime you use the ShellExecute() API (or Process.Start) to access a URL it fails when running under elevated rights (ie. Run As Administrator).
I see this in any application that uses Process.Start() or ShellExecute(). When UAC is on and I run it normally under the UAC account everything works and the browser opens. Run with "Run As Administrator" it fails. It's easy to test.
Not sure if this is a bug in the OS, or whether Microsoft deems this as a security 'feature'.
FWIW, some people have mentioned the setting IE as the default browser works, but it doesn't work for me. Basically no links work if I've elevated rights. This has actually broken quite a few administrative applications we use in the back office for administration.

Resources