Effective Xml Part 5: Something went really wrong OutOfMemoryException and StackOverflowException thrown when using XslCompiledTransform

Posted by: XmlTeams WebLog, on 27 Sep 2011 | View original | Bookmarked: 0 time(s)

So, your application is crashing and it is crashing in the bad way. After spending hours of debugging and trying different things you figured out that this is this Xslt stylesheet that causes all the problems. How come? XslCompiledTransform is a compiler. Its a bit different from C# or VB.NET compilers because it runs at runtime but the result of the compilation is basically the same IL (Intermediate Language) code. One of disadvantages of running compilation at runtime is that compilation issues...

Advertisement
Free Agile Project Management Tool from Telerik
TeamPulse Community Edition helps your team effectively capture requirements, manage project plans, assign and track work, and most importantly, be continually connected with each other.
Category: XML | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 252 | Hits: 10

Similar Posts

  • WCF and segmented WSDL Files = Problems more
  • XML Schema Facets more
  • Processing XML in .NET: Antipatterns more
  • A Quick Wilson.XmlDbClient Sample more
  • AJAX caching problem more
  • High-performance XML (V): Increase performance on message-based web services by avoiding XmlDocument creation when using XmlSerializer more
  • Introducing the XMLTextReader more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | 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