A quick way to host the ASP.NET runtime with ASP.NET 2.0

Posted by: Rick Strahls WebLog, on 24 Mar 2006 | View original

  In ASP.NET 2.0 runtime hosting there is a change in recommended objects that are used to get an instance of the ASP.NET runtime fired up. Specificially it looks like the preferred way to host the runtime is by using an ApplicationManager object to instantiate the runtime as opposed to using the ApplicationHost object.   ApplicationManager is actually an object that sits ontop of all running ASP.NET AppDomains and can do things like shut them all down or check for idle status. But other...

Advertisement
The leading UI suite for ASP.NET - Telerik radControls
Outstanding performance. Full ASP.NET AJAX support. Nearly codeless development.

Similar Posts

  • Moving ASPNETDB.mdf (SQL Express) to a hosted production environment. more
  • Share login and other state between ASP.NET and classic ASP - level 300 more
  • ASP.NET Podcast Show #31 - Paul on WSE3 more
  • My life as a web developer more
  • Circular File References and Other ASP.NET 2.0 / VS 2005 Conversion Issues more
  • Memory Growth in BizTalk Messaging more
  • Interesting bug in Saxon.NET/Mono/OSX usage more
  • Wondering where the latest build is more
  • Memory Growth in BizTalk Messaging more
  • A Special Promotion for ASP.NET DotNetNuke forum users @ ResellerChoice.com more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD