<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/486/Amazon-Simple-Storage-Service-Amazon-S3-Development-Tools.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=486</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=486&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Amazon Simple Storage Service (Amazon S3) Development Tools</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/486/Amazon-Simple-Storage-Service-Amazon-S3-Development-Tools.aspx</link><description>Getting started with Amazon Simple Storage Service (Amazon S3) is pretty easy. Especially if you use some of the available tools to hit the ground running. Obviously, one of the first things you are going to want to do is upload some files to your buckets. The C# Library and Code for Amazon S3 on Codeplex makes this a very painless and straightforward process. The library download also comes with both a Windows Form and Console Application sample so getting up to speed quickly is easy. Once you have more than a few files on your S3 instance you are going to need a convenient way to browse them. Once again, there are already several tools available to make this easy. If you are a Firefox user you may be interested in the S3Fox Organizer Firefox Add-on which is a Firefox Add-on to allow administration of your S3 instance. If you are not a Firefox user or prefer a standalone application manage your S3 instance then I would recommend the CloudBerry S3 Explorer. Using the above tools moving your CDN needs to Amazon Simple Storage Service can be pretty painless.</description><dc:creator>Scott Schecter</dc:creator><pubDate>Sun, 16 Aug 2009 23:43:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:486</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/468/FeedBurner-Maximum-Feed-Size-512k.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=468</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=468&amp;PortalID=2&amp;TabID=411</trackback:ping><title>FeedBurner Maximum Feed Size 512k</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/468/FeedBurner-Maximum-Feed-Size-512k.aspx</link><description>The other day I noticed that an RSS feed that is aggregated/published with FeedBurner was not showing new posts that we had added to the blog. Well first I noticed they were not showing up in a client that was consuming them but I digress. After disabling FeedBurner integration on the blog the posts were in the original RSS so the issue had to be on FeedBurner’s side. After digging around a bit in our control panels FeedBulletin it became clear that the max feed size limitation was the issue. The issue occurred largely because of two elements. Firstly, we had recently added a lot of image heavy posts to this blog. Each of these images was displayed inline at the original size in an attempt to make them more readable. Unfortunately, this also had the unintended effect of adding a lot of size to our feed. The second contributing factor was that we were showing the last 25 posts in our feed. Displaying so many posts also made the total size of our feed much larger that we had anticipated. The fix was a very easy one, simply turn down the number of items you are showing in total on your feed and use a good syntax highlighting plugin for Windows Live Writer when blogging code.</description><dc:creator>Scott Schecter</dc:creator><pubDate>Sun, 19 Jul 2009 23:15:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:468</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/433/DotNetNuke-MSBuild-Tasks.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=433</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=433&amp;PortalID=2&amp;TabID=411</trackback:ping><title>DotNetNuke MSBuild Tasks</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/433/DotNetNuke-MSBuild-Tasks.aspx</link><description>After upgrading CruiseControl.NET earlier this month, I thought about how it might be beneficial to remove our dependency here on nAnt. Don’t get me wrong, nAnt has been a great little utility that has helped me and our team (including the DotNetNuke Core itself) for many years now. However, it certainly has presented new problems in my move to 64 bit computing and it certainly isn’t getting the attention it once did. On the other hand, MSBuild was utilized by nAnt to do the actual building so why not remove what is essentially an extra piece of the puzzle.   Well, today in the DotNetNuke Forums I saw a post that pointed to a CodePlex project that contains some tasks. I haven’t spent much time with it yet, but I did notice it has an installer which really just puts a new folder and a DLL in your MSBuild folder. For those of you that are using a tool such as CCNet, remember this will need to not only be installed on your local development machines but also on the server itself. In addition, you will need to have the MSBuild Tasks project installed on those same machines (the developers and the servers). I have a feeling that I will be reviewing this over the weekend and will have much more to write about next week.</description><dc:creator>Chris Paterra</dc:creator><pubDate>Fri, 01 May 2009 21:19:38 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:433</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/414/Developers-Moving-to-64-bit-Vista-Workstations.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=414</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=414&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Developers: Moving to 64 bit Vista Workstations</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/414/Developers-Moving-to-64-bit-Vista-Workstations.aspx</link><description>Recently I decided to buy a new workstation to use at home, one that I would build myself. When deciding what I was going to purchase I wrote down a list of needs typically like I do requirements for a project I am proposing.</description><dc:creator>Chris Paterra</dc:creator><pubDate>Wed, 15 Apr 2009 15:11:48 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:414</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/238/DotNetNuke-HTML-Providers.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=238</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=238&amp;PortalID=2&amp;TabID=411</trackback:ping><title>DotNetNuke HTML Providers</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/238/DotNetNuke-HTML-Providers.aspx</link><description>A recent forum post on the DotNetNuke site had me thinking about the available DotNetNuke HTML Providers. Many people use DotNetNuke for their web site framework because, like me, they don't want to re-invent the wheel. Thousands of hours have been spent on the framework's development, not to mention the thousands of hours of development time spent on providers, skin objects, modules, etc. I have no idea exactly how many hours I have spent developing the forums module but I would say its multiple thousands of hours over a few years.</description><dc:creator>Chris Paterra</dc:creator><pubDate>Sat, 25 Oct 2008 22:24:00 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:238</guid></item><item><comments>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/203/Setting-up-NAnt.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=203</wfw:commentRss><trackback:ping>http://www.apptheory.com/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=203&amp;PortalID=2&amp;TabID=411</trackback:ping><title>Setting up NAnt</title><link>http://www.apptheory.com/DotNetNuke/articleType/ArticleView/articleId/203/Setting-up-NAnt.aspx</link><description>Here at AppTheory we often build custom modules for clients and deliver them source code when completing a project. After we handoff the code, I often receive many questions about how to automatically package installable modules as we do so customers can have their own developers make changes and deploy them without requiring interaction from AppTheory. To do this, we not only handoff the code we also provide the customer with custom build files we use. Even if you are not an AppTheory customer, you may find this article useful as several DotNetNuke core modules also use nAnt for packaging such as the core Forum module. Please note that if you are an AppTheory customer, one thing that you should keep in mind is that we distribute multiple build files that depend on one another. Because of this, paths are an important thing to keep in mind and we will email you details specific to our environment but all other items discussed here still pertain to you.</description><dc:creator>Chris Paterra</dc:creator><pubDate>Wed, 24 Sep 2008 18:56:18 GMT</pubDate><guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:203</guid></item></channel></rss>