Visual Studio 2013 -> New Project -> ASP.Net MVC App -> Unspecified error e_fail - asp.net

Well, I think I have banged my head a lot to get the answer on this issue, hence raising this again.
Some people might get answer here Visual Studio 2013 > New project > unspecified error (exception from hresult: 0x80004005 (e_fail))
I have Windows 7 Pros SP1, 64bit proc.
I installed VS 2013 Prof.
Clicked New project and started with New MVC 4 Internet facing application.
Thats it. End of the story. Somehow VS dont buzz forward and just gives unspecified error (exception from hresult: 0x80004005 (e_fail))
I tried cleaning \Documents\IISExpress\config folder, resetting IIS Express, reinstalling VS, reinstalling IIS Express and nothing helps. Dont know why VS wants to add IIS Express to new solution, but can experts help me to get started with VS 2013..?

Do you tried to start another project type
Is not easy to know what's not working good but, in my opinion is the VS. Uninstall the VS and install another time. Download the last version of VS from Microsoft website.

Solution was quite simple. We need to disable the default encryption of Documents\IISExpress folder from property window.

Related

Error while running asp.net apps in Visual Studio 2015

In my company I'm running Visual Studio 2015 Enterprise and just recently upgraded to Windows 10. Unfortunately, now I can't run any web project using versions of asp.net earlier than 5 (owin/katana) - always getting error :
"Could not load file1or assembly 'XXX' or one of its dependencies.
The process cannot access the file because it is being used by another
process. (Exception from HRESULT: 0x80070020) ".
Now, I've found a few posts like this and the answer is mostly that some other application is running on port 80, 8080 etc blocking visual studio's iis express. The problem is that I get this error regardless of port I'm using (even on some random 34535 etc).
The interesting part is that when I run kestrel (app on asp.net 5) it works and runs fine without any error.
Anyone has any ideas ?
Okay, so I had this issue and resolved it by uninstalling Panda antivirus, which presumably was locking the assemblies for just long enough to interfere with loading them some of the time.
If anyone else is having this issue, and there is definitely an assembly that won't load (as opposed to a port that's already been bound to) then try checking your antivirus!

"An operation is not legal in the current state" error when trying to launch ASP.NET project in VS2013?

I have an ASP.NET web site created with WebMatrix 3. I do have the option in VS2013 checked to use the 64-bit version of IIS Express since I am running on 64-bit Windows 8.1. When I try to launch the project I get the error "An operation is not legal in the current state". Does anybody know how to fix this?
I got this same error "An operation is not legal in the current state" when running a project on Google Chrome, Stopping the project then closing all chrome instances fixed the problem.
I think it's related to visual studio not being able to attach to chrome instance for debugging.
Closing Chrome and restarting IIS (e.g. in IIS Manager) should solve the issue. It helped in my case.
Just had the same issue on VS (Visual Studio) 2017 this morning.
The steps that will resolve this are:
Stop project that runs in VS
Clean all IIS instances that VS temporarily created
Compile project and start that service again

Problem with debugging ASP.Net application on IIS 7 on Windows 7

Few weeks ago I started using VS 2008 (Professional) with Windows 7 (Enterprise).
When working with ASP.Net web applications I repeatedly stumble over the following error:
After opening a solution with a web project the first compilation and debug go perfectly fine. The second time I try to debug the solution I get the "Unable to start debugging on the web server. System call failed" error and solution does not start at all. When I try to debug it again it always shows the same error but sometimes the app actually starts but does not break on the server code at all.
Any ideas why this could happen?
Thanks a lot for any suggestions.
(I use local IIS and run VS as Administrator)
Have you installed SP1 for VS 2008? I am using Win7 as well, and alot of the issues get magically resolved with a service pack. HTH.

Visual Studio Asp.net Website Compilation error: Child nodes not allowed

"Child nodes not allowed" seems to be notorious compilation error on Asp.net website if you do some googling.
Environment: WinXp, VS2008 and VS2008 SP1, .NET 3.5 SP1
Behavior: create a brand new Asp.net website (not web application), then just build it, you got compilation error "Child nodes not allowed" on the Web.config on line where it says providerOption name="CompilerVersion" value="v3.5"/>
I got this problem after I re-installed vs2008. Now, a lot of people are suggesting fixes but none worked for us. Only one guy mentioned he successfully got rid of this problem by re-installing windows, but we don't want to go that far if we don't have to. There is another person who opened a ticket to MS but hasn't gotten back a response yet.
If there is anyone out there who has similar environment like us and know how to get around this problem, we'd really appreciate it!!!
Edit The weirdest part of all this is that I don't know how I got it. It is a brand new box and brand new installation.
My colleague just found a fix for this dreadful problem, it is a .NET Framework Cleanup Utility at http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog|_Tools/dotnetfx20|_cleanup|_tool.zip
Just download, run and restart your machine and re-install .NET Framework 3.5 SP1 (since the cleanup util removes all the .NET Frameworks for you)! Really hope this could help others who have the same problem, it's been 4 days fighting with this one issue, thanks Microsoft!
Thank you guys very much for your input, I voted up for you both, appreciate it!
Ray.
You probably need to reinstall Visual Studio 2008 SP1.
I haven't got that specific error, but try the following (if you haven't already):
Since you re-installed the vs 2008, try re-applying the SP1
Clear all the asp.net temporary folders it generates for the web sites.

The custom tool 'msdiscocodegenerator' failed

I get this error when attempting to reference a Web Service in my Compact Framework application. Hunting through Google seems to indicate it's a common occurance, but there's been no useful suggestions as to what causes it, and how to fix it. I can successfully access the web service from a WinForms application by adding a Service Reference but the CF project only has the Web Reference option.
I am running Visual Studio 2008 on Vista.
Has anybody actually solved this problem after encountering it?
Thanks
Bill
Maybe yes... I forget as it was over a year ago. I needed to use a WCF service (presented as a web service) on CF 2.0 device. But I had issues with generating the wrapper.
What I think I did in the end was do it on the desktop and then copy that generated code into the device project. I had to remove a few bits to get CF compatability but it worked in the end.
Sorry for being so vague but my memory is like that sometimes. :)
This issue has been identified as BUG from Microsoft and fixed in latest version of visual studio. you can install VS 2013 and try. It was working properly after I upgrade my Visual Studio to 2013 version.

Resources