Comments on: Properly utilizing XslCompiledTransform http://www.mattberther.com/2009/02/27/properly-utilizing-xslcompiledtransform/ Agile Manager and Occasional Code Monkey Sun, 21 Feb 2010 22:01:35 +0000 http://wordpress.org/?v=2.8.5 hourly 1 By: Matt Berther http://www.mattberther.com/2009/02/27/properly-utilizing-xslcompiledtransform/comment-page-1/#comment-166466 Matt Berther Mon, 02 Mar 2009 16:08:04 +0000 http://www.mattberther.com/?p=1071#comment-166466 @kyle: Our applications use Castle Windsor for dependency injection, so that is how we're using that. It's default lifecycle works perfectly for this type of thing. If you're not using an IoC container, defining it in your application class and then using it that way would work as well. @kyle: Our applications use Castle Windsor for dependency injection, so that is how we’re using that. It’s default lifecycle works perfectly for this type of thing. If you’re not using an IoC container, defining it in your application class and then using it that way would work as well.

]]> By: Kyle http://www.mattberther.com/2009/02/27/properly-utilizing-xslcompiledtransform/comment-page-1/#comment-166465 Kyle Mon, 02 Mar 2009 15:28:16 +0000 http://www.mattberther.com/?p=1071#comment-166465 Thank you for sharing this tip. How are you creating an instance of CachedXslTransformLoader so that it is available everywhere it is needed? For instance, we use XSL heavily to handle website navigation and would want this object to be available to all requests, site-wide. Options I've considered include marking the Dictionary as static but that seems like a bad idea because it'll make it available server wide, not site-wide (which could have negative affects on a shared host). Another option might be to define an instance in the Application_OnStart method and then pass that in as a dependency to the method(s) we use for xml/xsl processing. Thoughts? Thank you for sharing this tip. How are you creating an instance of CachedXslTransformLoader so that it is available everywhere it is needed? For instance, we use XSL heavily to handle website navigation and would want this object to be available to all requests, site-wide.

Options I’ve considered include marking the Dictionary as static but that seems like a bad idea because it’ll make it available server wide, not site-wide (which could have negative affects on a shared host).

Another option might be to define an instance in the Application_OnStart method and then pass that in as a dependency to the method(s) we use for xml/xsl processing.

Thoughts?

]]>