I have a ASP.NET Web API project where I use PUT and DELETE frequently. Sometime during the last couple of months PUT and DELETE stopped working. The web.config is still the same and the verbs works fine on my other machine.
I haven't worked with the project during this time. The only things I recall I have done is the Windows 10 anniversary update and a couple of Visual Studio updates, but I have done the same updates on my other machine.
During this time my WCF services stopped working too. In attempts to get them to work I reinstalled some Windows components. I have installed everything that has to do with IIS.
Can this verb problem have anything to do with missing Windows components? I have no idea what it can be.
Apparently I managed to install support for WebDav publishing when I reinstalled the Windows features for IIS. I removed it and got my PUT and DELETE back!
Related
I've been trying to fix this for a while. I'm working on a cloud service and for some reason I get an error every time I try to run it. I've done everything I could think of doing.
I disabled and re-enabled SSL
I set an iplisten for 0.0.0.0 and made sure my computer wasn't currently using the port the project is using
I tried deleting applicationhost.config and even the whole .vs folder
I tried cleaning and rebuilding the project
In combination with messing with applicationhost.config and installing the .NET framework I needed, I restarted my computer
I'm pretty sure I tried a couple other things but they're slipping my mind at the moment. I'm currently using the following/have the following installed:
I'm using Microsoft Visual Studio Community Edition v16.10.31.321.278
.NET Core v5.0.0
.NET Framework 2.0, 3.0, 3.5, and 4.8
I have "Internet Information Services" and "Internet Information Services Hostable Web Core" enabled in my features tab
I'm running the latest version of Windows 10, completely up-to-date
The weird thing about all of this is that it works fine on my boyfriend's laptop, who's working with me on the project. I'm not exactly sure where to find the IIS logs either, if anyone knows and could let me know, that'd be very appreciated. I've grown tired of searching post after post to see that nothing helps. I'll upload the error logs later if I'm able to find them.
Did you try to run VS as Administrator ?
I used to have the same issue and find out it was the only way to solve this.
kind of desperate with this problem that I don't know how to fix and I don't know the cause.
Full error when running Blazor app:
It's a WASM application hosted in .net core. Therefore there is a backend and a frontend.
I have set my backend project as Startup project, which will take care of hosting also the frontend.
Both projects are set up on .NET 5.
I have read that multiple factors can cause this error and yet I tried all the possible solutions I have found so far.
I kill manually the app processes that hang running even when I stop debugging, closed VS, deleted the whole .vs folder and then restarted VS.
I disabled script debugging
Also tried enabled and disabled:
Tried also to start it with latest version of Microsoft Edge instead of Chrome, sometimes it works and doesn't give troubles sometimes it doesn't
in a post I have read from the official support that it's a bug that is being solved already in the 16.10 VS preview version. I downloaded and installed it, still nothing.
tried both iisExpress and .net CLI as hosting profile.
Moreover when starting the app a normal blank page only opens on the browser:
Don't know honestly what to try anymore. Could anyone help? Thanks in advance!
I have had the same problem exactly with the same setup, this on a couple times and on both occasions I have deleted the VS folder, did a rebuild and then rebooted my PC.
I know this is not a root cause solution, but it has worked for me.
In my case it was missing the latest ASP.NET Core framework...
Make sure you get the hosting bundle.
.NET location: C:\Program Files\dotnet\
The following frameworks were found:
6.0.9 at [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Learn about framework resolution:
https://aka.ms/dotnet/app-launch-failed
To install missing framework, download:
https://aka.ms/dotnet-core-applaunch?framework=Microsoft.AspNetCore.App&framework_version=6.0.10&arch=x64&rid=win10-x64
I had to restart VS after installing..
Updating to the latest hosting bundle did the trick for me.
I also threw out the .vs folder as well as any obj and bin folders in the solution projects to ensure a nice and clean environment.
Reboot. Rebuild. Rejoice.
Today I updated my windows 10 Pro computer to Insider Build 14931. When update finished, I noticed IIS disappeared. I went back to Control Panel\Programs\Programs and Features where i saw Internet Information Services was unchecked. I checked, it and got IIS back. The problem is that all the websites I created disappeared (websites folders and files, remain in my computer) and PHP & many extensions I had installed are no longer.
Of course, I can download them and reinstall, but I was looking if there is a shorter solution to it. Thank you.
Backups of the IIS configuration may be stored under C:\inetpub\history, just copy the latest files to C:\Windows\System32\inetsrv\config.
I'm trying to upgrade from ASP.NET MVC3 RC to RTM? I can't get past upgrading the vs10-kb2483190-x86.exe installer. I get this error in the error log:
Do I need to uninstall the Windows Phone SDK first? Should I hunt for GUIDs in the registry?
The installer appears to launch devenv.exe behind the scenes. I decided to launch VS2010 to see if it would "unlock" something. After it launched, I closed it and the installer started progressing.
Actually, it did work - I just ran for the second time...
When you run .msp, it pops a prompt that "the network resource for Visual Studio installation files is not available". Once you update the location of vs_setup.msi everything else works fine. I didn't have to run MSIs in sequence as the post suggests - once location was correct, I just ran MVC3 installation executable, and everything got installed fine.
It looks like platform installer and MVC3 setup just fail and, worse, swallow the root cause problem.
I finally gave up and reinstalled windows when I got a new CPU/Motherboard. Took care of it, not that I suggest this solution for everyone.
I think I'm cursed in some way... I had errors while installing MVC 3 beta. and now the same thing with MVC 3 RC. I've read about this problem here : http://haacked.com/archive/2010/11/09/asp-net-mvc-3-release-candidate.aspx. But after uninstalling all the mvc-beta-nuget-asppages stuff I have the same thing hanging - this VS10-KB2385361-x86 error.
I'm on Win7 x64, and using VS 2010 x64. What might be the solution to all this? (I don't want to reinstall the whole VS because of it).
OK. I've managed to install it (after 2 days trying).
Here is what I've done:
Uninstalled ASP.NET MVC 3 run-time components,ASP.NET Web Pages run-time components. (doesn't work after this);
Reinstalled VS 2010 ( still freezes);
Launched VS (just did some work, nothing special, just writing code), then I tried installing MVC 3 RC again (it got frozen), after a while I launched installer again having the firs one opened (it prompted some message saying another installation is running), and some real magic happened because first installer suddenly started working and installed whole thing.
Don't know how it works, but everything is running well (so far).
I found this problem yesterday, but i resolve it today, ohye
1、unzip AspNetMVC3Setup.exe to a folder
2、In the AspNetMVC3Setup folder, you can install aspnetwebpages.msi and aspnetmvc3.msi and other install
I am a chinese ,so I english is not good, I found other people has the same prblem, hope you can tell them
This is due to it needing the visual studio cdrom. If you installed from MSDN mount the iso and it should work. Just tested this and it worked.
I had the same problem on Windows 7 32-bit on the first attempt, but it worked on the second try with no changes to the system. If you see this issue it's worth retrying at least one more time before trying other things.