<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/"><channel><title>AppTheory</title><link>http://www.apptheory.com</link><description>RSS feeds for AppTheory</description><ttl>60</ttl><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/544/DotNetNuke-And-The-Elusive-lsquoCannot-redirect-after-HTTP-headers-have-been-sentrsquo.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=544</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=544&amp;PortalID=2&amp;TabID=411</trackback:ping><title>DotNetNuke And The Elusive &amp;lsquo;Cannot redirect after HTTP headers have been sent.&amp;rsquo;</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/544/DotNetNuke-And-The-Elusive-lsquoCannot-redirect-after-HTTP-headers-have-been-sentrsquo.aspx</link><description>Today I went to log into a clients staging site and received the following error ‘Cannot redirect after HTTP headers have been sent.’ from the YSOD (Yellow Screen Of Death). </description><dc:creator>Scott Schecter</dc:creator><pubDate>Sun, 06 Dec 2009 20:43:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:544</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/542/IIS-FTP-Failed-to-retrieve-directory-listing.aspx#Comments</comments><slash:comments>3</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=542</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=542&amp;PortalID=2&amp;TabID=411</trackback:ping><title>IIS FTP Failed to retrieve directory listing</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/542/IIS-FTP-Failed-to-retrieve-directory-listing.aspx</link><description>Upon trying to ftp some files up to a newly provisioned server I was experiencing some sporadic behavior.</description><dc:creator>Scott Schecter</dc:creator><pubDate>Sun, 29 Nov 2009 22:09:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:542</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/541/Microsoft-Services-vs-Google-Apps-Premium.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=541</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=541&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Microsoft Services vs. Google Apps Premium</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/541/Microsoft-Services-vs-Google-Apps-Premium.aspx</link><description>I am currently looking into the possibility of using a hosted email environment.  AppTheory has used an internal Exchange server for mail since the company started.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 20 Nov 2009 21:28:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:541</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/540/Home-From-OpenForce.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=540</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=540&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Home From OpenForce</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/540/Home-From-OpenForce.aspx</link><description>As most of you who read this know, AppTheory had a booth at OpenForce ‘09 last week in Las Vegas where we handed out flyers and discussed DotNetNuke with anyone who stopped by and wanted to chat. Surprisingly, there were many people who had tons of questions.</description><dc:creator>Chris Paterra</dc:creator><pubDate>Fri, 20 Nov 2009 20:40:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:540</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/535/AppTheory-wins-the-DotNetNuke-Best-Ecommerce-Site.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=535</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=535&amp;PortalID=2&amp;TabID=411</trackback:ping><title>AppTheory wins the DotNetNuke Best Ecommerce Site</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/535/AppTheory-wins-the-DotNetNuke-Best-Ecommerce-Site.aspx</link><description>AppTheory won the DotNetNuke Open Force 2009 Community Choice Award for Best Ecommerce Site!</description><dc:creator>bryan andrews</dc:creator><pubDate>Wed, 18 Nov 2009 16:35:16 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:535</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/539/The-request-signature-we-calculated-does-not-match-the-signature-you-provided-Check-your-key-and-signing-method-when-uploading-to-Amazon-S3.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=539</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=539&amp;PortalID=2&amp;TabID=411</trackback:ping><title>'The request signature we calculated does not match the signature you provided. Check your key and signing method' -- when uploading to Amazon S3 </title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/539/The-request-signature-we-calculated-does-not-match-the-signature-you-provided-Check-your-key-and-signing-method-when-uploading-to-Amazon-S3.aspx</link><description>You may remember in one of my previous posts I recommended the Affirma ThreeSharp library for interacting with your Amazon S3 storage system.</description><dc:creator>Scott Schecter</dc:creator><pubDate>Mon, 16 Nov 2009 00:32:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:539</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/532/Scaling-Out-DotNetNuke-Professional-on-Amazon-EC2.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=532</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=532&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Scaling Out DotNetNuke Professional on Amazon EC2</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/532/Scaling-Out-DotNetNuke-Professional-on-Amazon-EC2.aspx</link><description>Amazon Web Services (AWS) is a set of cloud based infrastructure web services that are offered to developers and companies.  These services provide expandable and flexible infrastructure to user.  The are several parts to the cloud infrastructure. Amazon Elastic Compute Cloud (Amazon EC2) is a web service that provides compute capacity in the cloud. This compute capacity is provided by Amazon Machine Instances (AMIs).  The machine instances can provide cloud based virtual servers with windows and *nix based operating systems.</description><dc:creator>Max Schneider</dc:creator><pubDate>Tue, 10 Nov 2009 02:21:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:532</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/534/Extracting-DotNetNuke-User-Information-With-SQL.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=534</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=534&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Extracting DotNetNuke User Information With SQL</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/534/Extracting-DotNetNuke-User-Information-With-SQL.aspx</link><description>It is not uncommon to have a client request a list of site users in a particular role. You can obviously get this information from the DotNetNuke user interface but its very easy to get this directly from the tables in SQL Management Studio and then export to a CSV or Excel file for easy distribution. Below is an example of finding all users for a particular portal.</description><dc:creator>Scott Schecter</dc:creator><pubDate>Sun, 08 Nov 2009 22:29:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:534</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/531/New-Telerik-Release.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=531</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=531&amp;PortalID=2&amp;TabID=411</trackback:ping><title>New Telerik Release</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/531/New-Telerik-Release.aspx</link><description>Telerik released their updated set of components for Q3 2009 the today. One of the things I find great about this release is their Visual Style Builder is now capable of producing detailed skins for all of their controls now. If you haven’t heard about the Style Builder, it basically allows you to redesign the user interface of the Telerik controls without having to write a single line of code or HTML code. To checkout the Visual Style Builder, follow this link to create your own set of custom Telerik control skins: http://stylebuilder.telerik.com/. New controls which are included in the release that may appeal to DotNetNuke developers is their new SiteMap control (which allows you to render from the google xml sitemap created by DNN, if you so desire), RadRating control, RadListView (basically a data list replacement), A new skin for all controls, Suite control installer now permits upgrading (instead of a completely re-install) and some performance enhancements. Also worth mentioning is it looks like they are getting about a 30% performance gain by removing some generic reflection use that was done in all controls previously vs. Telerik releases of the past.   You can read the full details for this release here:http://www.telerik.com/products/aspnet-ajax/whats-new.aspx</description><dc:creator>Chris Paterra</dc:creator><pubDate>Wed, 04 Nov 2009 22:01:04 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:531</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/530/A-Reminder-to-Vote.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=530</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=530&amp;PortalID=2&amp;TabID=411</trackback:ping><title>A Reminder to Vote!</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/530/A-Reminder-to-Vote.aspx</link><description>Today is the last day to vote for us at the OpenForce Community Choice Awards.</description><dc:creator>Ryan Wofford</dc:creator><pubDate>Wed, 04 Nov 2009 15:33:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:530</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/528/DotNetNuke-lsquoIs-Web-Farmrsquo-Changes.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=528</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=528&amp;PortalID=2&amp;TabID=411</trackback:ping><title>DotNetNuke &amp;lsquo;Is Web Farm&amp;rsquo; Changes</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/528/DotNetNuke-lsquoIs-Web-Farmrsquo-Changes.aspx</link><description>I was on one of our client sites this week and under Host Settings I noticed something odd. I saw that the “Is Web Farm” setting was set to true, the reason this is odd is because I know this particular install is NOT on a web farm as the setting says (shown in the screen shot below). So my next logical step was to jump over to the web.config for the install and turn this off.      Well, as I opened up the web.config and located the “EnableWebFarmSupport” in the appSettings section it was already set to false. At this point, I was puzzled so I decided to reach out to Charles Nurse as I knew DNN Corp. had created a new caching provider offered with DotNetNuke Professional Edition. While this install was using CE, I suspected that the new provider for PE could have required changes in the core itself. Here is what he had to say:  “In 5.1 we modified the “IsWebFarm” detection to detect if there are more than one server in the WebServers table.” Well, it just so happens this particular client we recently upgraded them to 5.1.x from a 4.9.x install which explains why I haven’t noticed this before (as for why we have more than one server in the WebServers table, that is for another blog). Continuing my conversation with Charles, he also informed me of some more details and changes to come. I think it is best to highlight those with a quick bullet list.     In 5.2 this is modified again.    In 5.1.x (All versions, all editions), the setting in the web.config means nothing.    The File Based Caching Provider (shipped with CE and PE) will be switched to, again, rely on the setting in the web.config.    The Web Request Provider (the one with PE only) will continue to rely on the WebServers table (ie. auto detection).    Thanks to Charles Nurse who saved me some discovery time!</description><dc:creator>Chris Paterra</dc:creator><pubDate>Mon, 02 Nov 2009 04:56:33 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:528</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/529/Bubbling-Up-An-Unhandled-Exception-From-Assembly-to-Windows-Service-Causes-Service-Stop-With-No-Logging.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=529</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=529&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Bubbling Up An Unhandled Exception From Assembly to Windows Service Causes Service Stop With No Logging</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/529/Bubbling-Up-An-Unhandled-Exception-From-Assembly-to-Windows-Service-Causes-Service-Stop-With-No-Logging.aspx</link><description>This one was very tricky to track down. We have a windows service that uses an assembly to transcode video files and upload them to a CDN. All of the logging of course takes place in the windows service. In our component the constructors of both the transcode and upload classes take a file full path as a parameter. We do a File.Exists() and if the file does not exist we throw an exception. Normally this is ideal as if an valid object cannot be created with the state given we want to know about it sooner rather than later. In our windows service we instantiate and perform the work of the upload or transcode objects within a for loop that has a try catch. In a non windows service the exception bubbled up will happily be caught and the iteration continues. However, it appears in a windows service it simply stops the iteration at that point. The service is not stopped in the Administrative Tools &gt; Services MMC applet, nor is any information logged to the event viewer.</description><dc:creator>Scott Schecter</dc:creator><pubDate>Mon, 02 Nov 2009 01:53:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:529</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/527/You-spin-me-right-roundhellip.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=527</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=527&amp;PortalID=2&amp;TabID=411</trackback:ping><title>You spin me right round&amp;hellip;</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/527/You-spin-me-right-roundhellip.aspx</link><description>Are you paying your agency to update your flash files on your site? If so, you could be getting taken...</description><dc:creator>Ryan Wofford</dc:creator><pubDate>Fri, 30 Oct 2009 20:23:07 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:527</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/526/Be-Careful-Applying-Permissions-between-Security-Groups-on-AWS-EC2.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=526</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=526&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Be Careful Applying Permissions between Security Groups on AWS EC2</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/526/Be-Careful-Applying-Permissions-between-Security-Groups-on-AWS-EC2.aspx</link><description>I have noticed that a couple of tutorials have gone into the basics for setting up DNN on AWS with two separate instances.  One instance is the frontend web server and the other instance is a backend SQL server. Two security groups are created one for the Web server (WebGroup) and one for the SQL server (SQLGroup). This is a common setup that we have performed many times at AppTheory.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 30 Oct 2009 19:38:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:526</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/524/AppTheory-at-Open-Force-lsquo09-Vegas.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=524</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=524&amp;PortalID=2&amp;TabID=411</trackback:ping><title>AppTheory at Open Force &amp;lsquo;09 - Vegas</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/524/AppTheory-at-Open-Force-lsquo09-Vegas.aspx</link><description>AppTheory will be at The DotNetNuke Open Force event again this year as an exhibitor. Come visit our booth!</description><dc:creator>bryan andrews</dc:creator><pubDate>Mon, 26 Oct 2009 16:17:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:524</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/523/DotNetNuke-Gold-Partner.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=523</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=523&amp;PortalID=2&amp;TabID=411</trackback:ping><title>DotNetNuke Gold Partner</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/523/DotNetNuke-Gold-Partner.aspx</link><description>AppTheory has joined the newly formed DotNetNuke Partner program at the Gold Level and is now an official reseller of the DotNetNuke Professional Product.</description><dc:creator>bryan andrews</dc:creator><pubDate>Mon, 26 Oct 2009 16:07:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:523</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/522/DotNetNuke-SSL-Wild-Card-Certificates.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=522</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=522&amp;PortalID=2&amp;TabID=411</trackback:ping><title>DotNetNuke, SSL, Wild Card Certificates</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/522/DotNetNuke-SSL-Wild-Card-Certificates.aspx</link><description>In a previous blog I discussed how DotNetNuke can enforce SSL at the page level. Well, going a bit further into the SSL world within DotNetNuke uncovered a few more notes worth keeping in mind. First, you can utilize wild cart certificates using the built in DotNetNuke SSL implementation. To do this, go to Admin –&amp;gt; Set Settings (as host) and locate the SSL section and expand it. What you will see is similar to the screen shot below. You then need to set the SSL URL (the domain the certificate, standard or wildcard, is attached to).      Setting the SSL URL will route all SSL requests to that domain (in the example, www.dnnforums.com). Setting the Standard URL will route all non-SSL requests to the domain (in the example, www.dnnforums.net). Now, the good news here is that with this setup, all my http requests get routed to my .net domain and all https requests get routed to my .com domain. After testing, I have verified it works fine and properly routes domains based on http and https. However, there is one slight issue here. It appears that when doing this the core took only the anonymous use case in here. What that means, if your domains are different you are going to be prompted for a login after a switch depending on which domain you are on (of course, this only matters if the domains are different like our example here). Hopefully, the core can be altered to add a cookie for this domain as well during the login process. </description><dc:creator>Chris Paterra</dc:creator><pubDate>Mon, 26 Oct 2009 14:49:08 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:522</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/525/Internet-Explorer-8-lsquoThe-XML-page-cannot-be-displayedrsquo-When-Rendering-Image-From-HttpHandler.aspx#Comments</comments><slash:comments>2</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=525</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=525&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Internet Explorer 8 &amp;lsquo;The XML page cannot be displayed&amp;rsquo; When Rendering Image From HttpHandler</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/525/Internet-Explorer-8-lsquoThe-XML-page-cannot-be-displayedrsquo-When-Rendering-Image-From-HttpHandler.aspx</link><description>Recently we noticed an issue on a clients site where images being rendered from an HttpHandler would display the following browser error in Internet Explorer 8 ONLY. 



The XML page cannot be displayed

Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.


--------------------------------------------------------------------------------

An invalid character was found in text content. Error processing resource 'http://www.mydomain.com/mypagename.aspx'. Line...



The image was rendered as expected in every other major browser we tested (e.g. Firefox, Chrome, Safari, etc). I did a quick code review and upon cursory inspection I did not notice anything out of sorts. Since this issue only occurred when the images where rendered via the HttpHandler and it only occurred in Internet Explorer my gut told me it was something in the response object content type that was not quite right. This is usually the kind of issue that takes quite a bit of time to track down and is very difficult to debug, but I guess I lucked out on this one. The issue was the Internet Media Type for the jpeg image format. Allow me to illustrate further, we had a switch that set a string variable ‘format’ based upon the image format.</description><dc:creator>Scott Schecter</dc:creator><pubDate>Sun, 25 Oct 2009 18:40:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:525</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/520/DotNetNuke-Telerik-amp-Ajax.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=520</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=520&amp;PortalID=2&amp;TabID=411</trackback:ping><title>DotNetNuke, Telerik &amp;amp; Ajax</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/520/DotNetNuke-Telerik-amp-Ajax.aspx</link><description>If you have worked with Telerik you are probably familiar with the “RadAjax” component which is a part of the ASP.NET Controls suite from them. Generally, you throw a RadAjaxManager on your page/control and you are pretty much set to have full Ajax functionality in your application. From here you can include/exclude controls and add a loading panel that can be shared by all panels on the page. Finally, you code your application pretty much like before, adding business logic in Page Load and button click events, and poof you have a full ajaxified application. While this works pretty much the same in any DotNetNuke module, it is important to do two things in your module otherwise you may not get the results you expect. The first is to set the SupportsPartialRendering equal to true. If just starting, this is done from the module definition for the specific control. Otherwise, it is done from a node in your dnn manifest file for your module. Next, the other thing you need to do is on Page_Init of your control you need to place a script manager on the page (if Ajax is installed). You can do this using the following code:    1: If DotNetNuke.Framework.AJAX.IsInstalled Then   2:     DotNetNuke.Framework.AJAX.RegisterScriptManager()   3: End IfOR:   1: if (DotNetNuke.Framework.AJAX.IsInstalled) {   2:     DotNetNuke.Framework.AJAX.RegisterScriptManager();   3: }</description><dc:creator>Chris Paterra</dc:creator><pubDate>Mon, 19 Oct 2009 14:47:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:520</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/519/Auto-Scaling-and-Elastic-Load-Balancing-with-Amazon-Elastic-Cloud-Computing.aspx#Comments</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=519</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=519&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Auto Scaling and Elastic Load Balancing with Amazon Elastic Cloud Computing</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/519/Auto-Scaling-and-Elastic-Load-Balancing-with-Amazon-Elastic-Cloud-Computing.aspx</link><description>Last week I talked about how AppTheory uses Amazon CloudWatch to help monitor our DNN instances on AWS EC2. CloudWatch also allows AWS EC2 users to enable Auto Scaling. Auto Scaling allows for the seamless scaling of Amazon EC2 instances “during demand spikes to maintain performance.”  Auto Scaling also allows for an application to gracefully scale down “during demand lulls to minimize costs.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 16 Oct 2009 21:40:43 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:519</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/518/How-can-DNN-promote-sustainability.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=518</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=518&amp;PortalID=2&amp;TabID=411</trackback:ping><title>How can DNN promote sustainability?</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/518/How-can-DNN-promote-sustainability.aspx</link><description>Can a website save the world?</description><dc:creator>Ryan Wofford</dc:creator><pubDate>Fri, 16 Oct 2009 17:29:04 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:518</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/517/CloudWatch-on-Amazon-Elastic-Cloud-Computing.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=517</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=517&amp;PortalID=2&amp;TabID=411</trackback:ping><title>CloudWatch on Amazon Elastic Cloud Computing</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/517/CloudWatch-on-Amazon-Elastic-Cloud-Computing.aspx</link><description>One of the tools that I have been using for quick monitoring of the DNN web and SQL instances AppTheory manages at AWS is CloudWatch. CloudWatch is a monitoring system much like the taskmgr on your server that lets you see a quickly monitor your instances CPU, Disk Reads/Writes, In/out network traffic.</description><dc:creator>Max Schneider</dc:creator><pubDate>Fri, 09 Oct 2009 19:39:16 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:517</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/516/A-Call-to-Action.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=516</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=516&amp;PortalID=2&amp;TabID=411</trackback:ping><title>A Call to Action</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/516/A-Call-to-Action.aspx</link><description>Are you drawing customers toward an action?</description><dc:creator>Ryan Wofford</dc:creator><pubDate>Thu, 08 Oct 2009 18:36:32 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:516</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/515/My-DotNetNuke-Core-Upgrade-Process-Simplified.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=515</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=515&amp;PortalID=2&amp;TabID=411</trackback:ping><title>My DotNetNuke Core Upgrade Process (Simplified)</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/515/My-DotNetNuke-Core-Upgrade-Process-Simplified.aspx</link><description>The first step in my process of testing a DotNetNuke upgrade is to get a duplicate copy of the site you are going to upgrade. This involves taking a copy of the file system, as well as the database and restoring them as&amp;#160; a new site. I always use the same names for the directory/virtual directory and database except I add “TEST_” as a prefix to clearly identify it. After I get everything copied, I then setup my new IIS virtual web server and assign it some new host headers (ie. test.domain.com) and make sure I have a nice robots.txt in the directory that blocks everything (. The next step is to add a portal alias directory into my PortalAlias table on in my database. Once we have this and the connection string in the web.config has been updated, we are ready to test the copied site to make sure everything is working PRIOR to attempting the upgrade (This is a minor but important detail I find most people overlook). Once I have the site loaded and I can login once as host I make sure my control panel is set to the core one (as sometimes we @ AppTheory use our own custom version) because sometimes this changes and will cause immediate errors after the upgrade and you can only fix directly in db, so take care of it now if you remember.   One final thing before starting my upgrade, I generally take a backup of my new TEST_ database as well as my new TEST_ directory. This ensures that if my upgrade fails I can quickly roll back and save myself the time it would take to repeat the steps in the first paragraph. To continue, I download the appropriate upgrade package of DotNetNuke and unzip it onto the server. I then grab the release.config and use Beyond Compare to compare it to my copied web.config to see if anything has changed. If anything is different, I merge the changes and save the file as my new web.config for my TEST site. I then copy all files from the Upgrade package over top of my TEST site making sure to replace existing files and that I also replace the web.config with my merged one from the previous step. Now I call up my test URL in my browser and let the process begin. Once the installation finishes, save a copy of success/failure messages (especially if there is a failure) so you can reference it later. Remember, if you have SqlDataProvider install issues you can find those in your siteroot\Providers\DataProviders\SqlDataProvider folder. At this point, all you have left to do is update your modules, providers and any third party controls (so long as you didn’t have other install issues) and do lots of testing. </description><dc:creator>Chris Paterra</dc:creator><pubDate>Wed, 07 Oct 2009 20:44:28 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:515</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/514/MyListBasedControlItemsFindByValue-is-Case-Sensitive.aspx#Comments</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=411&amp;ModuleID=1002&amp;ArticleID=514</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=514&amp;PortalID=2&amp;TabID=411</trackback:ping><title>MyListBasedControl.Items.FindByValue is Case Sensitive</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/514/MyListBasedControlItemsFindByValue-is-Case-Sensitive.aspx</link><description>I had this one bite me the other day so I thought it would make a good blog post this week. I had the need to check a list based control’s items (in this case a drop down list) to see if a value was present or not. All my testing worked fine, however when pushed to production using the event log I was able to tell that it was not finding the value as I expected it to. My test data was all lower cased while production data had a mix. Doh! It was an easy enough fix and I bet I remember this next time; but hopefully it saves you some cycles.</description><dc:creator>Scott Schecter</dc:creator><pubDate>Sun, 04 Oct 2009 22:51:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:514</guid></item></channel></rss>