Welcome to Microsoft .NET Framework 3.0 Community (NetFx3)

The .NET Framework is Microsoft's managed code programming model for building applications that have visually stunning user experiences, seamless and secure communication, and the ability to model a range of business processes.

Learn More...

WF Community Bloggers

Browse by Tags

All Tags » ASP.NET   (RSS)

  • Early spring cleaning

    So I was cleaning out my desk and found something that I would have blogged about had I had a blog when it happened :) People tend to think of me as a BizTalk guy - but before that I was really an ASP and then ASP.NET guy. On one of the early ASP.NET mailing lists Scott Guthrie challenged us to write an application that hosted ASP.NET outside of IIS (this of course if now all documented - but it wasn't at the time). I was the first (or one of the first) people to do this (the only thing I remember is having to use PInvoke and LoadLibrary to load the aspnet_isapi.dll into the process for stuff to work) and he sent me a hat (which I still have somewhere) and a signed .NET Framework CD. Fun days. Also funny that my next post will likely be able hosting ASP.NET outside of IIS. Check out my BizTalk R2 Training . Read More...
  • Using WCF WebHttpBinding and WebGet with nicer Urls

    I've been playing with the REST support in .NET 3.5. I'm really enjoying the programming model, but I am not enjoying the .svc file extension in my URLs (I'm not the only person I know who has felt this way for quite some time). IMO (from what little I know about the REST style) URLs shouldn't have things like extensions in them (or preferably not). So with they way WCF endpoint hosting in IIS works (obviously if I am hosting a webHttpBinding in a non-IIS host I can totally control the URLs, but I am writing a REST API to something where I plan to be hosting inside of IIS). This would end up being my url: http://host/albumn.svc/instance/ and I want: http://host/albumn/instance/ The .svc extension in the URL doesn't seem opaque to me. I tried modifying the HttpHandler element for the svc file - but that didn't work for various reasons. So I ended up writing a simple HttpModule to do URL re-writing (using HttpContext.RewritePath). I didn't really want any config relating to URLs - so this module assumes you are serving up only REST based URLs from a web application. If you were going to use it and serve up other handlers (like aspx files etc) it would need to be modified. Here is the module code: public class RestModule : IHttpModule { public void Dispose() { } public void Init(HttpApplication app) { app.BeginRequest += delegate { HttpContext ctx = HttpContext.Current; string path = ctx.Request.AppRelativeCurrentExecutionFilePath; int i = path.IndexOf(' / ', 2); if (i>0) { string Read More...
  • ASP.NET 2.0 Localization

    Source: Scott Guthrie's Blog Some resources on the new localization features for ASP.NET 2.0: Localization in ASP.NET 2.0 - by Wei-Meng Lee - 08/08/2005 ASP.NET 2.0 Localization Features: A Fresh Approach to Localizing Web Applications - by Michèle Leroux Bustamante, IDesign Inc, October 2004 [Updated April 2006] Localization in ASP.NET 2.0 - by Bilal Haidar - 05 May 2006 Read More...

Copyright © 2007 Microsoft Corporation. All Rights Reserved. | Terms of Use | Privacy Statement | Contact Us