IIS.net

Community Links 10/11/2008: URL Rewrite, ASP.NET, Extensibility, Diagnostics, WordPress

bills — Sun, 12 Oct 2008 05:01:14 GMT

Here are a few cool links I found today while catching up on my IIS reading:

URL Rewrite

In case you missed it, the IIS7 URL Rewrite extension is now licensed for production use in its final beta release. Deploy it today and get all the benefits from one of the most powerful IIS7 features around. Use it to clean up URLs, provide extension-less URLs, fix canonicalization issues with your site to improve search ranking, redirect incoming users and much, much more. This latest URL Rewrite release includes all new IIS Manager support for creating rewrite rules using templates, rule testing and more. Speaking of the URL Rewrite extension, check out these community links:

CarlosAg wrote a really awesome post on how to make your IIS7 site search engine friendly (SEO) with IIS7 URL Rewriter. Barry Wise, who has written a lot about SEO, did a follow-up post on the topic for IIS
Scott Hanselman writes about URL Rewriter as well on how he uses it to improve canonicalization including a scenario with ASP.NET MVC to remove trailing backslashes.
One of the powerful new features of this URL Rewrite release is the support for URL Rewrite templates. Check out Daniel’s post on how to extend the URL Rewrite Template support
RuslanY posted a walkthrough video of the URL Rewrite extension in action.
If you’re looking for a URL rewrite solution for IIS5/6/7, check out Helicon Tech’s isapiRewrite solution

ASP.NET

The ASP.NET team announced MVC Preview 5 of the new ASP.NET MVC Framework. Download the link on codeplex.
Also in the news, jQuery will now ship with with Visual Studio! This makes adding slick browser animations to ASP.NET applications a cinch.
ScottGu links to a bunch of related community links on the MVC and jQuery news in his recent blog post.
I’ve seen a lot of ASP.NET developers use wildcard script-mapping with IIS 6.0. As they move to IIS7, questions pop-up about whether *scriptmap is still supported, and how it relates to the new IIS7 integrated pipeline which allows .NET modules and handlers to run natively inside IIS’ core HTTP processing engine. RuslanY wrote an excellent article on this topic titled, wildcard script mapping and IIS 7 integrated pipeline

Misc

Tobin posted the source code up on codeplex for his very popular IIS7 logging UI which he released for Vista RTM (Vista SP1 now includes logging UI support by default). This is a good example of how to build UI extensions for IIS Manager
Tess at DezEnd.org wrote an in-depth post on how to diagnose performance issues using Failed Request Tracing and AppCmd.

TrainSignalTraining wrote a nice tutorial series on how to install WordPress on IIS7 in two parts (part 1, part2)

ASP.NET 2.0 x64 – You may get HTTP 400 Bad Request or Error as mentioned in KB 932552 or 826437

rakkimk — Sat, 11 Oct 2008 02:24:32 GMT

I’m sure you already know about this fix for ASP.NET which fixes an issue of “not a valid path” exception, and this fix for ASP.NET 1.1 for the same reason. If you receive this error now on your application, you might not need to apply the hotfix because your ASP.NET version might be higher than the one available with this hotfix, so verify the DLL versions before even requesting the hotfix from Microsoft.

So, after installing the hotfix, you should do the below registry changes (not sure if the hotfix does this automatically – I haven’t tested this):

DWORD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\VerificationCompatibility = 1

as mentioned in the KB article 932552. But, you might see that this doesn’t work if you run the application pool under 32-bit mode on a x64 Windows Server 2003 or 2008. That’s just because, the ASP.NET reads this key from a different location as below:

DWORD HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ASP.NET\VerificationCompatibility = 1

I’m sure you doesn’t want me to explain why ASP.NET reads from this location instead of above. If you want, please drop a note.

In IIS 7.0, you would get the below error message while running under Integrated mode:

“HTTP Error 400.0 - Bad Request
ASP.NET detected invalid characters in the URL”

Hope this helps!

.rm

PHP and IIS – A Deeper Dive

stjacobs — Sat, 11 Oct 2008 00:30:00 GMT

Contents

PHP and IIS – A Deeper Dive.

PHP and IIS – A Deeper Dive

This article takes a deeper dive into the way PHP works with Windows and IIS7. There are some great articles on IIS.Net in the Learn section that cover getting PHP set up and working. This article is going to focus more on the things you need to know as a developer and user of PHP applications on Windows.

Which PHP to get?

At the time this article was written, the current 5.x version of PHP was 5.2.6. We have worked with a number of PHP applications running on IIS with this version, and we have had good results. It is likely that any current version in the 5.x tree will work with the notes below.

There are two builds for each PHP version. One is thread safe, and one isn’t, referred to as the Non Thread Safe (NTS) version. The thread safe version is designed for environments where the web server core can keep the PHP engine in memory, running multiple treads of execution for different web requests simultaneously. The architecture of IIS and the FastCGI extension provide an isolation model that keeps requests separate, removing the need for a thread safe version. The NTS doesn’t have any of the code that allows PHP to manage multiple threads. As a result, you will see a performance improvement on IIS when using the NTS version as compared to the tread safe version.

Installation

There are two main ways that people get PHP installed on their Windows systems. They either download the Windows Installer, or the Windows Zip file from http://www.php.net/downloads.php. Either of those methods will get PHP working, but both of them have some extra steps that are needed to make PHP work really well.

Windows Installer version

The Windows Installer version does a good job of getting a complete PHP environment up and running. However, the installation of Extensions can be a little confusing. The default is to not install any extensions, which will adversely affect the usefulness of your PHP install. Alternately, you could tell the installer to install all of the extensions, which will leave you with an unstable system as some of the extensions will conflict with others.

Zip Installation

If you use the ZIP installation, follow the instructions in http://learn.iis.net/page.aspx/246/using-fastcgi-to-host-php-applications-on-iis-70/ . One of the most important steps missing from that article, is changing the “extension_dir” variable in the php.ini file. This version installs many of the extensions that are available for the Installer version. However, none of them are enabled until their entries in the php.ini file are set up. I’ll cover this later in the article where I talk about the php.ini file.

PHP Settings

PHP is a very versatile language and environment, with a number of powerful features to meet the needs of many different types of applications. There are dozens of extensions, and hundreds of configuration options in the base PHP installation packages. This article focuses on the needs of common Open Source PHP applications. Although these applications are diverse, there are a certain set of extensions and settings common to all of them which make them run better on a Windows environment.

Extensions

You need to take some time and figure out which extensions you need to have to get your application running, and limit the installed extensions to just those. For a typical open source application install, I make sure the following extensions are installed:

Database Extensions – Most open source applications that use MySQL use either the php_mysql or the php_mysqli extensions. If you are doing new development work, either of those would be fine. Or, you may want to consider using the PDO versions of the MySQL driver, as the extra layer of abstraction gives you a richer set of Object Database functionality and controls. If you are using either SQL or SQL Express as your engine, I would grab the php_mssql extension for open source applications. If you are doing new development, for open source, or otherwise, I would strongly recommend using the PDO version of the SQL driver, available soon from the Microsoft SQL website.
Image Handling – Many of the open source applications that allow you to work with images make use of the GD2 extension – php_gd2. This extension has a number of good basic image manipulation APIs. Some applications use the ImageMagick application and libraries, available from http://imagemagick.org/script/index.php. There is also the php_exif library for working with the extended information that modern digital cameras store within the images.
Internationalization and Localization – The two most used extensions for i18n and l10n are php_mbstring (Multi-Byte String) and php_gettext (Native Language Support). Many of the open source applications use one or both of these. For new development, you should look at these and decide if you want to use their functionality.
Web Services Extensions – There are a few web service options out there. You should choose the ones you want to use based on the services you want to create or interact with. In the PHP world, the SOAP extension is widely used. The XML-RPC extension is often used in conjunction with SOAP and other services.

The php.ini file

The php.ini file tells PHP how to configure itself, and how to work with the environment that it runs in. Here are a number of settings for the php.ini file that help PHP work better with Windows. Some of these are optional. There are many other directives that may be relevant to your environment. The best way to learn more about them is to read the php.ini file installed with PHP, and to look at the PHP documentation.

Required:

extension_dir = <PATH TO EXTENSIONS> - The extension_dir needs to point to the directory where your PHP extensions are stored. The path can be fully qualified (i.e. “C:\PHP\ext”) or relative (i.e. “.\ext”). Extensions that you specify lower in the php.ini file need to be located in the extension_dir. If the extensions specified are not in the extension_dir, then PHP will throw a warning message at the start of script execution, and often the application you are running will throw errors because of the missing functionality.
extension = xxxxxx.dll – For each extension you wish to enable, you need a corresponding “extension=” directive that tells PHP which extensions in the extension_dir to load at startup time.
log_errors=On – Another place that PHP errors can go is through the PHP error logging facility. This can be used to send errors to a file, or to a service (i.e. syslog) and works with the error_log directive below. When running under IIS, you need to have log_errors enabled, with a valid error_log. If you don’t, FastCGI considers any startup messages (which may just be benign) as an error condition which generates an HTTP 500 return error code to the browser.
error_log=<path_to_error_log_file” – The error_log needs to specify the fully qualified, or relative path to the file where you want to store the PHP error log. This file needs to be writable for the IIS service. The most common places for this file are in various TEMP directories. I usually use “C:\inetpub\temp\php-errors.log” for this. That puts the log in a place that IIS can use, and also keeps it close to where I’m running or developing my PHP applications.
cgi.force_redirect = 0 – This directive is required for running under IIS. It is a directory security facility required by many other web servers. However, enabling it under IIS will cause the PHP engine to fail on Windows.
cgi.fix_pathinfo = 1 – This lets PHP access real path info following the CGI Spec. The IIS FastCGI implementation needs this set.
fastcgi.impersonate = 1 - FastCGI under IIS supports the ability to impersonate security tokens of the calling client. This allows IIS to define the security context that the request runs under.
fastcgi.logging = 0 - FastCGI logging should be disabled on IIS. If it is left enabled, then any messages of any class are treated by FastCGI as error conditions which will cause IIS to generate an HTTP 500 exception.

Optional:

· max_execution_time=## - This directive tells PHP the maximum amount of time that it can spend executing any given script. This is one of many places where a time limit can be placed on request execution time. The default for this is 30 seconds. If you are running applications which may need more time to process batch operations (i.e. Gallery2 loading multiple images from a remote location), you can increase this as much as you need to. From a practical perspective, going higher than 300 is not advised, as there will often be other places in the connection that refuse to go longer.
· memory_limit=###M – The amount of memory available for the PHP process, in Megabytes. The default is 128, which is fine for most PHP applications. Some of the more complex ones might need more. I usually run with 256M available on a 4GB of RAM system.
· display_errors=Off - This directive tells PHP whether to include any error messages in the stream that it returns to the Web server. If this is set to “On”, then PHP will send whichever classes of errors that you define with the error_reporting directive back to IIS as part of the error stream. Many of the Open Source applications bypass error reporting by executing commands prefaced with ‘@’. This allows the applications to control error handling.
· Mail functions – PHP is configured by default to send outbound mail through an SMTP server located on the web server’s box. Most Windows installations will usually have the Web and Mail servers on separate systems. There is a section in the php.ini (detailed below) which you need to update if you want PHP applications to be able to send e-mail.

Running PHP on Windows

There are a few aspects of running PHP applications on Windows that are different from running PHP on another platform. This section concentrates on those differences, and how you need to work with them.

Interacting with IIS 7 via FastCGI

The addition of FastCGI to IIS has brought about significant performance improvements to PHP apps running on Windows. Configuring it to work with PHP is relatively straightforward. The basics can be found in the article Using FastCGI to Host PHP Applications on IIS 7.0.

Another way of configuring FastCGI is using the IIS Administration Pack, available from http://www.iis.net/downloads/default.aspx?tabid=34&i=1683&g=6. With the Admin Pack, it is easier to tune your FastCGI environment. The setting that you are most likely to need changing is the ActivityTimeout, which defaults to 30 seconds. If you double click on the FastCGI Settings icon from the IIS Manager, and then double click on the application path for PHP displayed there, you will see the window below. Just click on the text you want to change, and type in the new value.

File Security

As with any web server, PHP requires IIS to be able to read the script and other files required for an application. For many PHP applications, PHP will require IIS to be able to write files into directories (i.e. a cache), or modify files (i.e. a configuration file). Make sure you evaluate what files and directories that your application will need to write to, and set up appropriate permissions.

Execution Time

In the early days of web application development, a bug in your application could cause a Web server to cycle indefinitely trying to process a request that would never complete. To address this, developers have added execution time caps into most levels of the Web request infrastructure. In a typical application environment, you will be able to adjust this timeout in a number of locations, each of which control the maximum execution time for the section of the request owned. The relevant locations and configure information for a typical PHP on IIS scenario are listed below

Web server request time
FastCGI ActivityTimeout – covered in the FastCGI section above
PHP max execution time – covered in the php.ini section above
MySQL request execution time

Php.ini Examples

Here is an excerpt from a php.ini file that covers the settings discussed above. It’s not a complete php.ini file, so don’t just drop it in as one. However, if you put this at the end of a php.ini file, the values here will take precedence over the ones found previously.

max_execution_time = 60    
memory_limit = 256M     
display_errors = Off     
log_errors = On     
error_log="C:\inetpub\Temp\php-error.log"     
cgi.force_redirect=0     
cgi.fix_pathinfo=1     
fastcgi.impersonate=1     
fastcgi.logging=0     
[mail function]     
; For Win32 only.     
SMTP = mail.example.com     
smtp_port = 25     
sendmail_from = stjacobs@microsoft.com     
extension_dir = “.\ext”     
extension=php_curl.dll     
extension=php_gd2.dll     
extension=php_gettext.dll     
extension=php_mbstring.dll     
extension=php_mssql.dll     
extension=php_mysql.dll     
extension=php_mysqli.dll     
extension=php_pdo.dll     
extension=php_pdo_mssql.dll     
extension=php_pdo_mysql.dll     
extension=php_soap.dll     
extension=php_xmlrpc.dll     
extension=php_xsl.dll     
extension=php_smtp.dll     
extension=php_exif.dl

XPerf: A CPU Sampler

ASP.NET Debugging : IIS — Fri, 10 Oct 2008 10:00:00 GMT

Seema just had a great about using XPerf to troubleshoot CPU issues when using Silverlight. This can also be used in the same way to troubleshoot ASP.NET or IIS. What can XPerf tell you? Seema answers that question, it can find out: Is my Read More......(read more)

ASP.NET MVC and the new IIS7 Rewrite Module

Scott Hanselman's Computer Zen - IIS — Fri, 10 Oct 2008 09:23:08 GMT

Last year I noticed that there were 11 ways to get to my blog. Literally 11 different URLs and it wasn't helping me my ranking in the search engines. I wrote about this in detail and how I used ISAPI_Rewrite to fix it up . Fast forward to this year and Read More......(read more)

Microsoft Web Platform Installer Beta

rakkimk — Wed, 08 Oct 2008 01:11:50 GMT

If you are a web deployment guru, and looking to reduce your burden of downloading lot of software, configuring them and if you didn’t check Bills’ blog earlier, you better do check it right now.

The new ‘Microsoft Web Platform Installer Beta’ gives you an easy way of configuring the ASP.NET/IIS stack along with tools needed for development all in one go.

1. Select the IIS components you need to install

2. Select the tools, .NET SP

3. Download and Installation

You can get it from here. Happy Deployment (with less hassles)!

.rm

Where to download and buy IIS7 and Windows 2008

bills — Mon, 06 Oct 2008 15:14:00 GMT

I've heard several people ask where to buy IIS7 and Windows 2008. First, if you want to download and try before you buy, Microsoft has made Windows 2008 trial editions available, with just a few clicks and a live ID you can download them today.

If you are looking for the lowest cost, fully-featured Web server for the internet, look no further than Windows Web Server 2008, which is the enhanced version of Windows server specifically built for internet Web sites. It supports the full hardware specs of Standard Server (4 proc and 32GB RAM), has the full IIS7 Web Server feature-set, supports SharePoint and Windows Media Services, and even allows for local SQL Server installs to support Web applications. To compare it to other Windows 2008 editions, go here.

If you are ready to buy, Windows Web Server 2008 is available for purchase online and through all of the major OEMs. If you are a do-it-yourself kind of guy, check out NewEgg's listing for an OEM license here for $349, or purchase the full retail copy on Amazon for $429.

Once you've got Windows 2008 Web server installed on your PC/server, be sure to download the Microsoft Web Platform Installer to help you get IIS7, ASP.NET, SQL Server and even Visual Web Developer Express installed quickly!

The world of Syndication: Atom 1.0 vs. RSS 2.0?

vsood — Mon, 06 Oct 2008 00:39:57 GMT

Syndication has become and inseparable part of the internet. There are two major syndication formats that exist today – RSS 2.0 (Really Simple Syndication) and Atom 1.0 (Atom Syndication Format). While they achieve the same end result, there are differences. This post attempts to enable you to decide which is more suited to your publishing.

RSS 2.0 is a frozen specification copyrighted by Harvard and Atom 1.0 is a specified in RFC4287. Atom came about as a result of pursuit to fix shortcoming of RSS since RSS was a frozen format. The table below lists the differences in the two specifications/standards:

	Atom 1.0	RSS 2.0	Who wins?
Content Model	Allows text, escaped HTML, well-formed XHTML, XML, base-64 encoded binary or pointer to web content outside the feed.	Text or Escaped HTML	This is a major advantage for Atom, writing escaped HTML affects the readability of RSS feeds
Partial Content	Has separate `<summary>` or `<content>` tags.	Has a `<description>` field. This could contain complete content or just synopsis but has no way of identifying what it contains.	This is another win for Atom, helps you have a synopsis and complete view inside a feed reader
Auto Discovery	Uses the MIME Type `application/atom+xml` which is registered with IANA. In addition the feed has a self link to enable auto subscription in readers	The MIME Type `application/rss+xml` is often used but not recognized by IANA	Having a registered MIME Type and auto subscription really helps discovery. Another Atom win.
Format Flexibility	Atom syndication format allows entries linking to the feed or standalone entries	RSS only recognizes a `<rss>` document.	This is also an Atom win, having standalone entries enables scenarios like linking to entries only.
Extensibility	Atom defines a well-defined structure to extend the default namespace and has specific guidelines on readers should interpret these.	RSS has to fixed namespace, however you could include external XML namespaces.	Atom has a slight advantage here as external namespaces extensions in RSS are not easily discoverable. In Atom’s case these extensions have a corresponding namespace tag
Languages	Atom uses xml:lang for language specificity	RSS has a separate `<language>` tag for language specificity	No one.
Encryption	Atom allows the option to encrypt entries using XML Encryption or XML Digital Signature. In addition the feed could be encrypted entire feed using standard web encryption techniques	RSS only allows encrypting using standard web encryption techniques.	Atom has extra level of encryption possible.
Adoption	Most sites that publish both RSS and Atom feeds.	Most sites that publish both RSS and Atom feeds.	RSS has an advantage of being the first mover, the term RSS has become synonymous with syndication.
Modularity	All elements part of Atom’s namespace can be used outside Atom’s context due to way it was designed	RSS elements cannot be used outside the context of RSS	This has proved to be the one of the major factors of Atom’s popularity and its used in data interactions like those enabled by Google GData

As you might have realized that Atom has considerable benefits over RSS. More and more services online are using Atom as more than just a feed format. Google’s GData and Microsoft’s Project Astoria are great examples and testimonies of Atom 1.0’s strengths as a format. They extend its namespace and harness the capabilities of Atom Publishing Protocol to pass data between their services.

While, I was writing, I realized that I was still publishing an RSS 2.0 feed for my blog (default supported by Drupal). I switched it to Atom 1.0. Have you? My recommendation to you would be switch to Atom as your base feed. Having said that, RSS is still very popular and consumed by many, it is good to retain your RSS feed too. Atom preserves most aspects of RSS so a simple transform (e,g, using XSLT) should be able to help you create and RSS feed from the Atom one.

If you know more examples that demonstrate Atom / RSS’s strength please post your comments below. I would love to hear from you.

Additional Reading:

While I was writing this post, I found RSS20AndAtom10Compared very useful
Atom on Wikipedia
RSS on Wikipedia
RFC 4287 – Atom Syndication Format
RFC 5023 – Atom Publishing

Web Platform Installer: Trying to make it easier to setup for web development

Scott Hanselman's Computer Zen - IIS — Fri, 03 Oct 2008 21:29:40 GMT

There's a renewed focus, in my opinion, to make things easier to find around The Big Blue Monster . I'm working with a bunch of folks on a more official version of http://www.smallestdotnet and some changes around making the .NET Framework easier to find Read More......(read more)

IIS logging UI module sample added to CodePlex

TobinTitus — Fri, 03 Oct 2008 19:21:00 GMT

For those of you that remember that far back, I released a sample that also filled a need for Windows Vista. Since the original version of Windows Vista did not ship with a user interface for managing logging, and we needed samples of how to build UI modules available to the public, I released the Logging UI module. For some time, I've been hosting that downloadable release on my private web site (tobint.com). As I plan to make some major changes to my personal site over the next few months, I wanted to make sure the release was still reliably available. That said, I've now added the source code to CodePlex.

You may find the project at http://www.codeplex.com/iis70loggingui .

I have worked with our source asset management team and made this available under the <a href="http://www.codeplex.com/iis70loggingui/license">MS-PL</a>. I hope that this makes the download reliably available. I'm looking forward to developing more samples that I will also be releasing in the same manner.

IIS7 – Enabling Custom Error Pages

rakkimk — Fri, 03 Oct 2008 18:36:08 GMT

As the title sounds, here I’m going to discuss a very simple feature of IIS7 which has one additional step to keep in mind compared to that you do in the previous versions of IIS (5, 5.1, 6). Let’s take an example of configuring a redirect for a page to HTTPS if it is browsed on HTTP. There are a lot of ways doing this HTTP to HTTPS redirection, where using custom error pages is one of them.

If you force HTTPS to be used in your website, error 403.4 would be returned to the browser. By default detailed error message (403.4) won’t be sent to the browser, but just 403. However, you can enable detailed error messages. Now, we need to configure our error page so that it redirects the requests to HTTPS. You can do it by following this KB article which was written for IIS 5, and 6, but holds good for IIS 7.0 as well.

Just adding an entry would enable this rule functioning, but if you try to test from your local server itself which most of the people would do after configuring this, you would see it doesn’t redirect you to the URL mentioned, and it gives you the same 403.4 error page.

That’s because of IIS 7.0 by default doesn’t send the custom error pages to a local request, but the detailed errors. So, you need to configure IIS to do a custom error message even if it is browsed from the server. But, you can ignore following below if you doesn’t care if the site redirects from the server (which is true for any customer facing website). Click on “Edit Feature Settings, and then choose “Custom error pages”, and click on OK.

So, take away from this post is “don’t try to test the custom error pages from the server itself after configuring it, since they are by default disabled for any local request”.

.rm

Fast Download and Install of Microsoft's Web Stack: IIS7, ASP.NET, SQL Express, Visual Web Developer, and more...

bills — Fri, 03 Oct 2008 17:04:00 GMT

Let's face it, getting Microsoft's Web server, framework and tools installed is much more painful than it should be. Visit 10 different web sites, download a dozen different packages, install them one at a time, and maybe in a few hours you are ready to get started. And then once you've got the stack installed, staying up to date and discovering new extensions is even more difficult. Wouldn't it be nice if you could just go to one place and get the whole stack, and stay up to date?

Introducing Microsoft's Web Platform Installer: a one stop shop for downloading and installing the Microsoft Web Stack including IIS, ASP.NET, SQL Server, Visual Web Developer, all of the current IIS Extensions and more! Once installed, this tool automatically discovers new additions and updates to the platform, keeping you up to date.

Install Today: Download the tool on the new http://microsoft.com/web site here and give it a try. Post any questions or problems to the Web PI forum.

ASP.NET Tip: When to use which Session Server

ASP.NET Debugging : IIS — Fri, 03 Oct 2008 10:00:00 GMT

There are 3 different ways you can store session in an ASP.NET application: InProc (default mode) State Server SQL Server InProc means we store the data in the same process (in memory) on the web server, in the worker process. This has some distinct Read More......(read more)

AppCmd 80070057 errors when configuring site-level settings

Robert McMurray's Blog [MSFT] — Thu, 02 Oct 2008 17:20:00 GMT

I had an interesting question from a coworker who was trying to use AppCmd to set the site-level SSL options for an FTP site. This should have been straightforward, and the syntax that he gave me looked correct: appcmd.exe set config -section:system.applicationHost/sites -[name='Default FTP Site'].ftpServer.security.ssl.controlChannelPolicy:SslAllow /commit:apphost That being said, whenever he or I ran the command we received the following cryptic error from AppCmd: Failed to process input: The parameter...(read more)

Microsoft Web Platform Installer Beta Released

CarlosAg Blog — Thu, 02 Oct 2008 11:00:00 GMT

Today we are releasing a new Web Site at http://www.microsoft.com/web/ where users can get a one stop shop for learning about the Microsoft Web Platform. This is part of a bigger effort to make it easier to get started with building and running Web Applications on Windows and IIS. As part of this a new tool called the Web Platform Installer Beta is also being released to help you getting started installing and getting all the software that you need from a single place without having to hunt around...(read more)