Error Occurs to run local IIS in visual studio 2013 ultimate - asp.net-mvc-4

I have configure the IIS server 8.5 in my windows 8.1. But when i tried to run my mvc project on Local IIS server an error occurs. A dialog box appears having the statement "cannot debug some of the code in process w3wp.exe[3276]. IntelliTrace code failed. The System cannot find the file specified. Managed (v4.5, v4.0) code succeeded"
What I supposed to do now?

Check your App Pool on your IIS is set to Enable 32bit Applications to True, Rebuild your Project and try again.

Related

Missing components to configure and manage IIS express

I am attempting to launch & debug an ASP.NET 5 project from within Visual Studio, and getting the error message "Missing components to configure and manage IIS express".
The solution builds without error. But IIS Express will not start and allow me to debug.
I have tried restarting Visual Studio and ensuring that the ports used by the project are free to use.
close Visual Studio
try deleting .vs folder and rerunning
open Visual Studio and try relaunching
According to the error message, we can have a try with the following:
1.Close solution, delete .vs folder if this issue only happens in the specific solution
2.Delete the folder IIS express folder: C:\Users\UserName\Documents\iisexpress
3.Delete temporary ASP.NET Files located: C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root
Start > Run > appwiz.cpl > Add/Remove Components > Install the full version of IIS.
Or if the full version of Internet Information Services (IIS) is currently installed do a Repair.

Running IIS Express in 32-bit crashes my ASP.NET Core web application

I have an ASP.NET Core web application which I'm trying to run in 32-bit with IIS Express. I followed other guides and tips to make IIS run in 32-bit, but every time i try to run the application it crashes with the error message:
System.BadImageFormatException: Could not load file or assembly. An
attempt was made to load a program with an incorrect format.
I have tried the following:
Set the build and debug to run x86
And unchecked the Use the 64 bit version of IIS Express for web sites and projects
But my project still closes almost immediately with the error mention above. Is there a setting that I am forgetting about or something else I need to do before the project can run in 32-bit.
I'm using visual studio 2017 on Windows 10 with IIS Express version 10.0.14393.0 and AspNetCore 2.1

Register .NET Framework 4.5 in IIS 7.5

Pieces of the puzzle:
Windows 7
.NET Framework 4.5 (installed)
IIS 7(Version 7.5.7600.16385)
Visual Studio (Ultimate 2013)
MVC4 (multiple projects in the solution)
The solution I'm running in Visual Studio works and runs as expected with IISExpress.
To set up my site to use IIS, I tried the following steps:
Right-click the projects in the solution that are currently being hosted by IISExpress.
Click Properties.
Toggle the Servers drop-down from IISExpress to Local IIS
Try to build/run the application
At this point, I get an HTTP 500.21 error.
I have also tried to run aspnet_regiis.exe -i using Visual Studio's command prompt (as an Administrator), but each time I run the command, I receive the following error:
Command 'aspnet_regiis.exe' is not valid.
I also confirmed that I do have the right aspnet_regiis.exe installed (by checking here) (.NET Framework version 4 (64-bit systems)).
What do I need to do to register .NET Framework 4.5 in IIS 7.5?
You can find the aspnet_regiis in the following directory:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319
Go to the directory and run the command form there. I guess the path is missing in your PATH variable.
Hosting asp.net 4.5/4.5.1 Web application on Local IIS
1)Be Sure
IIS Installation before Visual Installation Installataion then aspnet_regiis will already registerd with IIS
If Not Install IIS and then Register aspnet_regiis with IIS by cmd Editor
For VS2012 and 32 bit OS Run Below code on command editor :
1)Install IIS First & then
2)
cd C:\Windows\Microsoft.NET\Framework\v4.0.30319
C:\Windows\Microsoft.NET\Framework\v4.0.30319> aspnet_regiis -i
For VS2012 and 64 bit OS Below code on command editor:
1)Install IIS First & then
2)
cd C:\Windows\Microsoft.NET\Framework64\v4.0.30319
C:\Windows\Microsoft.NET\Framework64\v4.0.30319> aspnet_regiis -i
BY Following Above Steps Current Version of VS2012 registered with IIS
Hosting (VS2012 Web APP)
Create VS2012 Web Application(WebForm/MVC) then Build Application
Right Click On WebApplication(WebForm/MVC) go to 'Properties'
Click On 'Web' Tab on then 'Use Local IIS Web Server'
Then Uncheck 'Use IIS Express'
(If Visul Studio 2013 Select 'Local IIS' from Dropdown)
Provide Project Url like "http://localhost/MvcDemoApp"
Then Click On 'Create Virtual Directory' Button
Then Open IIS by Prssing 'Window + R' Run Command and type 'inetmgr' and 'Enter' (or 'OK' Button)
Then Expand 'Sites->Default Web Site' you Hosted Successfully.
If Still Gets any Server Error
like 'The resource cannot be found.'
Then Include following code in web.config
<configuration>
<system.webServer>
<modules runAllManagedModulesForAllRequests="true"></modules>
And Run Application
If still problem occurs
Check application pool by : In iis Right click on application->Manage Application->Advanced setting->General. you see the application pool.
then close advance setting window.
click on 'Application Pools' you will see the all application pools in middle window.
Right click on application pool in which application hosted(DefaultAppPool).
click 'Basic Setting' -> Change .Net FrameWork Version to->.Net FrameWork v4.0.30349
For Windows 8 and Windows Server 2012 use dism /online /enable-feature /featurename:IIS-ASPNET45
As administrative command prompt.
I got into this mess twice and after searching long and hard and following what others did absolutely nothing worked for me but to uninstall and install IIS back once on Windows 7 machine and then on Windows server 2012 R2.
use .NET3.5 it worked for me for similar issue.

wcfsvchost and VS 2012 express

I'm trying to get started on WCF using VS Studio 2012 Express for Web 32bit on a Win7 x64 machine. THe debugger is supposed to launch wcfsvchost.exe to test out my WCF service, but this file is nowhere on my machine. I have tried re-installing VS 2012 and updating to Update 3 but still no sign of this exe on my machine. I cannot find any info on the net indicating this utility is not provided with the Express version of VS.
Any help on what I am missing greatly appreciated.
You need to set few things in the WCF project Properties in order to open the WCFService test Client.
Project-> Right Click -> Debug -> Chooose Start Project radio Button.
and set the following parameter in commandlike argument.
/client:"WcfTestClient.exe"

Running .EXE file made in visual studio 2005 failure

I would like to run a .exe file made with visual studio 2003 but I get an error every time I run it on a windows 7 machine, vista machine, and xp machine. The error on Windows 7 and vista says "application has stopped working" and then makes me close the error box.
In windows xp it's a little different error, "the application failed to operate (0xc0000135) Click on OK to terminate the application."
That error code seems to indicate the application failed to initialize correctly.
It is possible that the anticipated .NET version is not present.
As far as I know, VS 2003 by default compiles against the .NET 1.1 library. There is no straightforward way of installing this on a Windows 7 or Vista box. Do you need to compile it against the .NET 1.1 library, or can you load it in VS2005, change the output .net version to 2.0 or higher, and recompile the application?
If you have the source code to the application, try running the application in debug mode and stepping through line by line until you find the exception. If you do not have the source code, possibly try running the application in a couple different compatibility modes. Another option to try is to check the windows event log for anything more specific.
If you want to get really deep into it, you can use SysInternals ProcMon.exe and filter on the failing exe to view the WinAPI calls that are happening during the failure.
Also, a basic search of forums shows that error is usually accompanied with framework issues. Either recompile the application or check out what your required framework is in the VS2003 project settings.