Posts Tagged 'iis'

3rd-Party Keep-Alive HTTP Module for IIS

This product from Xepient looks interesting.  And only 5 Euros!  Whatever that is in USD, it feels cheap.

Advertisements

Disable Keep-Alive in IIS 7.0

This technet article says that I should

  1. Open IIS Manager and navigate to the level you want to manage.
  2. In Features View, double-click HTTP Response Headers.
  3. On the HTTP Response Headers page, in the Actions pane, click Set Common Headers.
  4. In the Set Common HTTP Response Headers dialog box, select the Enable HTTP keep-alive check box and then click OK.

But I don’t see the “HTTP Response Headers” option in my web application configuration (see image below). What am I doing wrong?

IIS 7 Control Panel

ASP.NET Futures Release July 2007

I just installed the ASP.NET Futures Release from July in order to get my hands on the new XAML server control.

One interesting note about the installation: the docs imply (and other commenters have noticed) that you need to manually add the MIME types for .xaml and .dll in IIS:

To run ASP.NET Web pages that contain the Media or Xaml controls when using features such as the XamlUrl property, managed code, or dynamic languages, you must set up MIME types in IIS for the following file name extensions: .xaml, .dll (for using managed code assemblies), and .py and .jsx (for using dynamic languages). For more information about how to configure ASP.NET Web sites for using Silverlight controls, see the Readme.htm file in the Silverlight_1.1_Quickstarts.Zip file. This .zip file is part of the Microsoft Silverlight 1.1 Alpha Software Development Kit (SDK) on the Silverlight Web site.

However, running Vista Ultimate with IIS7, I found that after the Futures install I already had those items mapped properly. I can’t say for sure that this install did that, but can’t think why the Silverlight 1.1 SDK would have set those MIME types for me.

Blogged with Flock

Tags: , ,

Debugging Silverlight via IIS

This one has me scratching my head. I noticed tonight as I was investigating how to get QueryString parameters to my XAML code-behind file that the default Silverlight Project configuration opens your .html page via the filesystem, NOT as a website (virtual or otherwise). When I F5 into my very simple Silverlight test project, the browser opens:

C:\Users\Anthony.bear2\Documents\Visual Studio 2008\Projects\SilverlightProject1\SilverlightProject1\TestPage.html

When I had expected it to prompt me to set up a website or virtual root and go to something like:

http://localhost:1234/SilverlightProject1/TestPage.html

Stumper. I don’t see any options in the project properties to configure a web app either. Mike Taulty seems to have concluded that you need to create a new Web Site project and link to Silverlight, with some additional copying. Seems error-prone to me. However, this official-looking post from MSFT seems to confirm that this method is indeed state-of-the-art with regard to debugging Silverlight apps via IIS.

To summarize from the above post:

  • Add a website to the solution.
  • Right click on a folder in the website and use the “Add Silverlight link” command to link the output from the Silverlight project to the website. Click Yes to enabling Silverlight debugging from the website.
  • Copy the testpage.htm, js, and silverlight.js to the website or use the asp:xaml control in an aspx page.
  • You should now be able to set the website as the startup project.
  • F5 Should now launch the page in the website in the browser under the debugger and using the web server for the web project.

VS 2005 Debugging Broken on Vista

I’ve been trying to work around this problem for the last few months but the frustration has reached a boiling point.

VS 2005 is a great product — easily the best IDE of the Visual Studio line. Easy to use, customizable, well-integrated with the various tools I use, etc. However, since I’ve installed Vista Business, debugging directly out of VS 2005 has been a nightmare.

First I ran into the “Debugging failed because integrated Windows authentication is not enabled” error. Even when enabling Windows Authentication, I ran into the problem. So moving everything back to the Classic Pipeline worked, but I hated it — why have the new Integrated Pipeline available if you can’t use it?

Then, Microsoft released the hotfix KB 937523. Great? Not really. Now after F5 I get the error “IIS does not list an application that matches the launched URL“. I can debug to a root page, but not a subdirectory page. Irritating.

Another link to the IIS.net forums about this new issue.