In a previous post, I mentioned how the new Technology Toolbox home page highlights the most recent blog posts from Subtext. In this post, I'll show you how easy this feature was to develop -- thanks to the Entity Framework and LINQ.
In my previous post, I described the PowerShell script used to rebuild the Development environment for TechnologyToolbox.com on a daily basis. This post explains the subtleties of running the script -- or, more generally, any PowerShell script -- using the Windows Task Scheduler...
In this post, I describe the PowerShell script used to rebuild the Development and Test environments for TechnologyToolbox.com. From a high-level perspective, the script deletes the IIS website (if it exists), creates a new website (including the corresponding application pool), and then copies the files for the main site as well as the Subtext files for the /blog application...
In this post, I'll show you how I quickly restore the Production database for TechnologyToolbox.com to the corresponding Development and Test environments...
While I don't expect many people will need to migrate blog posts from Telligent to Subtext, I do believe it is valuable to provide a walkthrough of how I typically approach a "content migration scenario" -- since I frequently encounter this kind of requirement when working with enterprise customers...
While creating the new TechnologyToolbox.com site, one of my first tasks was to define the structure of the HTML for the blog pages. I briefly considered using my old MSDN blog as a reference. However, I quickly dismissed that option after viewing my MSDN blog home page with CSS disabled...
This morning I discovered that Feedburner wasn't showing the blog post I created last Thursday. No error was displayed. Rather the RSS feed simply made it look like...
In my previous post, I described how I typically create a "static HTML prototype" for an ASP.NET or SharePoint Web application. By working directly in HTML at the beginning, I can rapidly define the structure of the content and subsequently create the corresponding CSS rules to style the pages...
Regardless of the platform a website will eventually run on (e.g. ASP.NET or SharePoint), I typically recommend creating a static HTML prototype to demonstrate key features, illustrate various design alternatives (e.g. different page layouts, color schemes, etc.), and gather feedback...
Once I settled on using Subtext as the blogging solution for the Technology Toolbox site, I turned my attention to working on the other areas of the site...