<?xml-stylesheet type="text/xsl" href="https://uat.community.rws.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Poor man&amp;#39;s profiling of a DXA.NET Web Application</title><link>/product-groups/tridion/tridion-sites/b/blog-posts/posts/poor-mans-profiling-of-a-dxa-dotnet-web-application</link><description>If you&amp;#39;re encountering performance issues with your Web Application, one of the first things you should be doing is finding the hot spots : what are the places in code where a lot of time is spent and why? Hopefully, you will uncover an inefficiency which</description><dc:language>en-US</dc:language><generator>Telligent Community 12 Non-Production</generator><item><title>RE: Poor man&amp;#39;s profiling of a DXA.NET Web Application</title><link>https://uat.community.rws.com/product-groups/tridion/tridion-sites/b/blog-posts/posts/poor-mans-profiling-of-a-dxa-dotnet-web-application</link><pubDate>Mon, 16 Jul 2018 12:56:51 GMT</pubDate><guid isPermaLink="false">10acfa76-f078-475b-a7ef-fc5b3e8d2934:0939589f-c952-4d47-9a1a-adafa16b1b8d</guid><dc:creator>Mark Saunders</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Great debugging approach Rick - thanks for sharing!!&lt;/p&gt;
&lt;img src="https://uat.community.rws.com/aggbug?PostID=7855&amp;AppID=230&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>