Off the Microsoft stack!

Tag Archives: guidance

For this sprint, I updated the MSDN topic for configuring MOSS so that it includes the manual steps to configure MOSS 2010 for compatibility with TFS 2010 dashboards. In the past, you had to use a blog post or the MOSS configuration tool, if you wanted to make those configurations. To make up for taking so long getting it out there, I pulled together a short video that explains all of the steps.

If you find these videos helpful, I’d love to hear about it in the comments here on the blog or on YouTube. If you have a request for a video, let me know that, too. I’ll do the best I can to get them created and posted. I must say I’m really enjoying creating the videos.

If you want to follow along with the official manual steps, you can find them here. You might also find some of these topics helpful, too:

One of the nice things about Team Foundation Server 2010 upgrade is that it’s so flexible. One of the bad things about Team Foundation Server upgrade is that it’s so flexible.

What does that mean?

If you want, you can skip adding reporting or a SharePoint portal during upgrade. This might be helpful if your team never used reporting or the SharePoint portal prior to upgrade, and you can’t imagine using either of these features with the upgraded project at any time in the future.

But here is the catch: If you do skip adding either of these features during upgrade, you won’t be able to use them with the upgraded project (see the Tip under, “Portal Server and Reporting Upgrade Options”). This means that you can’t create reports from data in the upgraded project and you won’t be able to use a portal. You can add these features after upgrade, but you will not be able to easily get your upgraded projects to work with them.

New projects are a different story. You can use reporting and SharePoint with new projects, even if you don’t add reporting and SharePoint during upgrade.

I’ve heard of a few customers who ran into a problem with their SQL Server or portal during upgrade and thought: I’ll just add it after upgrade. That won’t work. If you know you want to create reports or use a portal with the upgraded project, you must not skip adding them during upgrade.

About three years ago, I started my current job where my main documentation deliverable is a Microsoft Compiled HTML Help file, which is distributed to customers by a page off the Microsoft Download Center. Not long after a new release of the guide went live, I got an email saying the file was corrupt.

Oh, no! I thought. First the President of the United States commutes Scotter Libby’s sentence and now this!

The email contained a screen shot similar to this one:

Fortunately for me, I had colleagues on the team who had been distributing CHM files this way for much longer than me. The file isn’t corrupt, but its ability to render HTML has been purposely disabled. The issue is explained in this KB article and involves a security update that purposely prevents HTML in all compiled help files from rendering, if that file was downloaded from the Internet.

Once you understand the issue, it’s simple to fix:

Download the file to your desktop (or wherever), right-click the file and then click Properties.

Click Unblock.

Now when you open the file, the compiled HTML will render just fine. If only political corruption were as easily resolved!