I don't want to turn this into a political/social blog, and I won't devote much space to this sort of thing, but...
You may not agree with me, and that's fine. You may feel that it's appropriate to legislate discrimination, but I do not. I'm hoping that you'll take a moment and view the anti-FMA (Federal Marriage Amendment) video here, and will follow through on making it clear to your legislators that you also would prefer to not legislate discrimination.
In my perfect world, the government would have no part of marriage--I believe that this is a religious union that has nothing to do with the U.S. government--but those of us who believe that the government should be in the business of supporting civil unions different from religious marriage fight a severe uphill battle. In any case, the FMA is a bad start (in my opinion).
If you disagree with me, feel free to post a differing opinion on your blog. If you agree, please take the time to view the video and get involved in defeating this unnecessary amendment. Thanks.
From MSDN Magazine:
Advanced Basics: Setting Word Document Properties the Office 2007 Way
The last time I wrote this column (March 2006), I shared an application that allows you to update all the Microsoft® Word documents in a folder and its subfolders. Each time the application finds a document in the specified path, it updates the document properties to match those you specified in the application. I use this application myself. I often need to change a group of Word documents, setting all the properties to match, and performing this task by hand is a real chore. I'm revisiting this topic with a new version of the application. For information on the prior version, check out my previous column. That column explains the application and discusses its plumbing (which includes Windows® Forms data binding and automation of Microsoft Word 2003).
The original application has some shortcomings. It requires each document to be loaded into Microsoft Word, where the properties are manipulated and the document is saved, and then it moves on. Obviously, the application requires a copy of Word on the local computer. In addition, the application incurs the extra overhead of using COM interop to interact with Microsoft Word, and the inherent security issues involved in using unmanaged code as part of a managed application.
In the March column, I promised to revisit the issue. This time I've taken advantage of technology that is new to the Microsoft Office arena. I've rebuilt the application using the new Open XML file formats that are used by the upcoming release of 2007 Microsoft Office system (formerly code-named Office "12"). As you'll see, the new application allows you to modify the contents of Word documents without a copy of Word and without any COM interop involvement. There are also significant speed improvements. (Read the rest...)