Is there a way to get the Application Initialization Module that is written for IIS 7.5 to work with IIS Express in Visual Studio? I'm trying to find a way to test my implementation of System.Web.Hosting.IProcessHostPreloadClient which is the entry point for this module.
A late answer but I was looking for the same answer and you can find it under Control Panel -> Programs and Features -> Turn Windows features on or off:
Related
I see the following error with Visual Studio 2015 (Tried both community and professional edition).
Wrote a simple Visual C++ CosoleApplication which has "printf("Hello World\n");".
Debug with Platform "x86" Compile and step through Works.
Debug with Platform "x64" Compiles but when it runs it throws this error.
Code is simple with following lines:
// ConsoleApplication1.cpp : Defines the entry point for the console application.
//
#include "stdafx.h"
int main()
{
printf("Hello World \n");
return 0;
}
My desktop has following configuration:
OS: Windows 7 Enterprise 64-bit version
Anti-Virus: McAfee Anti-virus software running; Can't disable that.
Firewall: ON (Can't disable that for security)
Question: Stepping through the code with (Debug x86 platform) works. Why "Debug x64 platform" does NOT work ?
Any suggestion would be helpful.
Thanks
gshant
I was having the same trouble. This is what I did.
Go to Project, Project properties.
Select Application Tab and make note of what framework you are using. For me it was 4.5.2.
Use the pull down to select a different Framework. At the bottom there is an option to install additional Frameworks.
After the web page opens, select the Framework you previously noted and download the Development Pack.
Close Visual Studio and install the Development Pack.
This worked for me when I selected x64.
Hope this helps you.
Make sure you have both the x86 and x64 .NET Core runtimes installed.
https://www.microsoft.com/net/download/windows
This answer deals with using IIS 7 to debug. I have not checked it with IIS Express.
If your web application is 32-bit (x86), you need to run IIS Manager and:
Look at the "Basic Settings" of your web site. Check what IIS
application pool your project is using.
Look at the "Advanced Settings" of this application pool and ensure
that "Enable 32-bit applications" is True.
This was a firewall issue for me. I'm not sure the exact root cause, but I found stopping my firewall resolves this. If I find the exact root cause, I'll update my answer so firewall exception rules can be written.
I believe the issue is when you are debugging it is actually using the remote debugger still under the hood (connecting x86 Visual Studio to an x64 process, etc) and a firewall can block this.
The solution for me was to go:
Project -> Properties -> Build -> Prefer 32-bit enabled
with Platform target -> "Any CPU".
Just migrated to VS2012 and having this issue. I need to develop against real IIS server (to be able to debug web services when they called from network devices)
Having issues with "IIS Express started on same port", etc. But there seems to be no IIS Manager for Express? How do I control and configure it?
I'd rather fall back to real IIS
Register asp.net
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i
Open Project-> Right Click Select Properties-> Select Web Tab-> Select Use Local IIS Web Server & uncheck the Use IIS Express checkbok -> Specify Project Url
To uninstall IIS Express via Windows 10
Go to Settings -> Apps and features -> Select IIS Express -> Uninstall
Note: IIS Express is packaged with Visual Studio installation (if you have selected to develop ASP.NET Web applications). I DO NOT KNOW if uninstalling IIS Express will have undesirable repercussions in your VS IDE.
I would just follow the instructions above rather than completely uninstalling IIS Express.
Cheers!
I have just installed VS2012 and created a MVC project. I right clicked on project and selected property, I chose Web tab. I selected "Use Local IIS Web server" but the "Use IIS Express" checkbox is disabled.
I checked my C:\Program Files (x86)\IIS Express\ folder and IIS Express 8 is there.
Any particular reason?
If I fall back to use Visual Studio Development Server, I have 50% of the chance to see "Server Too Busy" message.
All you have to do is to activate IIS in your development machine:
Start -> Control Panel -> Enable or disable Windows features -> Internet Services
Then check mark in World Wide Web Services -> Common HTTP Features
And check mark in World Wide Web Services -> Application development Features
That's all you need.
Using Full IIS has some benefits. One is that it is always running, so you don't have to start your VStudio Project to unit test. Another is that you can create an actual site and configure IIS mirroring production, using the same Admin Tools, which makes it easier to support when deployed in an environment. And, I seem to recall that IISExpress had issues with Application Routing. On the flip side, I don't see an issue with using the Full IIS. Granted, IISExpress is much better than Cassini, but if there is no reason to not use Full IIS then I conitnue to advocate it's use.
I'm using IIS 7.5 on Windows Server 2008 R2 x64 Enterprise Edition. In the project we have developed with ASP.NET 4.0 we used WCF Service. But it doesn't run over domain when the software is running from local computer. Otherwise, I am getting the following error:
HTTP Error 404.3-Not Found
The page you are requesting cannot be served because of the extension
configuration. If the page is script, add a handler. If the file should
be downloaded, add a MIME map.
You should install IIS sub components from
Control Panel -> Programs and Features -> Turn Windows features on or off
Internet Information Services has subsection World Wide Web Services / Application Development Features
There you must check ASP.NET (.NET Extensibility, ISAPI Extensions, ISAPI Filters will be selected automatically). Double check that specific versions are checked. Under Windows Server 2012 R2, these options are split into 4 & 4.5.
Run from cmd:
%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir
Finally check in IIS manager, that your application uses application pool with .NET framework version v4.0.
Also, look at this answer.
In my case, along with Mekanik's suggestions, I was receiving this error in Windows Server 2012 and I had to tick "HTTP Activation" in "Add Role Services".
In windows server 2012, even after installing asp.net you might run into this issue.
Check for "Http activation" feature. This feature is present under Web services as well.
Make sure you add the above and everything should be awesome for you !!!
I was having trouble accessing wcf service hosted locally in IIS. Running aspnet_regiis.exe -i wasn't working.
However, I fortunately came across the following:
Rahul's blog
which informs that servicemodelreg also needs to be run:
Run Visual Studio 2008 Command Prompt as “Administrator”.
Navigate to C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation.
Run this command servicemodelreg –i.
I have just finished the development of a web service application in visual studio.
Is there an easy way to wrap it in an installer, so that I can just ship it off to technical support, and they can have a wizard based installer that will fully setup an IIS site for them, either in 6 or 7?
You can use Visual Studio's built in setup project. I've only tried this once on a test project, but it created all the necessary stuff in IIS 6 just fine.
I would suggest you export the IIS METABASE for your local instance of the service and then this can be imported into a new server to create the correct IIS configuration. Have a look at Copying IIS Configurations using iiscnfg.vbs The METABASE is just an XML file and you will easily see the specific values that allows you to edit them should the deployment be different in anyway.