Bill Coan

Has anyone tried to follow along with the new article on "Deploying Visual Studio 2005 Tools for Office Second Edition Solutions Using Windows Installer (Part 1 of 2)"
The article is here:

About half-way through Part 1, the following instructions appear, leaving me perplexed:
Preparing the Office Component Check
Compile the Office component checker sample for the primary interop assemblies redistributable packages
Important:
If you are using VSTO 2005 SE in conjunction with VSTO 2005, ensure that you have installed both the .NET Framework 2.0 software development kit (SDK) and the Windows SDK.
Here's my question: Which Windows SDK should I install I'm running VSTO 2005 SE with VSTO 2005 on WinXPSP2. I assume that I should install a Windows SDK specific to WinXPSP2, but I can't figure out what file that would be I can find Platform SDKs for Vista and WinServer 2003. Should I be looking for a "Platform SDK" for WinXPSP2 Or should I be looking for a "Windows SDK" as listed in the article Where can I find the SDK

--
Bill Coan
billcoan@wordsite.com


Re: Visual Studio Tools for Office Deploying Visual Studio 2005 Tools for Office Second Edition Solutions Using Windows Installer (Part 1 of 2)

Douglas H. Troy

You should be able to just download the current (latest) Windows Server 2003 Platform SDK from here:

(adding correct link):

http://www.microsoft.com/downloads/details.aspx FamilyId=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en

(incorrect link originally posted):

http://www.microsoft.com/downloads/details.aspx FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en

 






Re: Visual Studio Tools for Office Deploying Visual Studio 2005 Tools for Office Second Edition Solutions Using Windows Installer (Part 1 of 2)

Bill Coan

Douglas,

Thanks for this helpful reply. I will go ahead and install the Windows Server 2003 Platform SDK. I have to admit that I never would have guessed that that's the package being referred to in the article. I appreciate your help.





Re: Visual Studio Tools for Office Deploying Visual Studio 2005 Tools for Office Second Edition Solutions Using Windows Installer (Part 1 of 2)

Douglas H. Troy

Bill,

Yes I agree, they really need to clear that up, and/or provide direct links to the appropriate download locations.

Since I do a lot of C++ development, that is the only reason I knew the answer to the question ... but even still, I had to read that section a couple times to even understand what it was they were trying to get us to do, exactly.






Re: Visual Studio Tools for Office Deploying Visual Studio 2005 Tools for Office Second Edition Solutions Using Windows Installer (Part 1 of 2)

Bill Coan

Thanks, Douglas, that makes me feel a little better. I had assumed that everyone else knew exactly what the article was referring to, and that my own background as an Office vba developer was the problem.

BTW, do you know if there is any reason to use the older SDK that you referenced as opposed to the one found here, which seems to be newer

http://www.microsoft.com/downloads/details.aspx FamilyId=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en





Re: Visual Studio Tools for Office Deploying Visual Studio 2005 Tools for Office Second Edition Solutions Using Windows Installer (Part 1 of 2)

Douglas H. Troy

Gad. No, use the newer one for certain ... the link I provided you was what the MSDN coughed up when I searched ...

Go figure.

... and on that note, think I'm going to run my SDK Update Check and make sure I have the latest and greatest files myself...

[Edit]

going back and re-reading the notes on the page I linked to, it clearly says (in bold) "This is old" ... which I obviously missed ... I should probably get more coffee.






Re: Visual Studio Tools for Office Deploying Visual Studio 2005 Tools for Office Second Edition Solutions Using Windows Installer (Part 1 of 2)

Bill Coan

Douglas,

Guess what Darryn's article has now been updated with a specific link to the Windows Vista SDK!

Unfortunately, I'm using VSTO2005SE on a WinXPSP2 machine, since that is the only machine I have that has Office 2003 installed on it. So I went ahead and downloaded the WinServer2003 SDK.

Alas, when I tried to compile the ComponentCheck.cpp file, I got a message saying the compiler couldn't locate the windows.h header file.

Never one to be discouraged, I went ahead and downloaded the WinVista SDK and installed it on my WinVista machine and then I was able to compile ComponentCheck.cpp just fine. Then I copied the resulting executable to my WinXPSP2 machine, and so I hope I'm all set as far as that goes.

Since you're a C++ guy, perhaps you can help me understand what the compiler did in response to the following command line:

cl.exe /Oxs /MT /GS ComponentCheck.cpp advapi32.lib

I figured out some switches:

/Oxs maximum optimizations, favor code space

/GS enable security checks

But I couldn't figure out /MT and I couldn't figure out advapi32.lib. Any idea what those items do





Re: Visual Studio Tools for Office Deploying Visual Studio 2005 Tools for Office Second Edition Solutions Using Windows Installer (Part 1 of 2)

Douglas H. Troy

/MT is the multi-threading command-line switch

advapi32.lib is linking that LIB with the executable (this contains APIs for things like the registry)

As for the compiler not finding the windows.h file, if the web installer didn't properly path to the SDK includes directory, that would be a problem; the Windows.h file is a standard includes file (in other words, it's not specifically a "Vista" header).

I've downloaded the samples project and will move it over to my VSTO SE dev machine for a look-see. If the project has a make file, there's an easier way to compile it ...

I'll let know.






Re: Visual Studio Tools for Office Deploying Visual Studio 2005 Tools for Office Second Edition Solutions Using Windows Installer (Part 1 of 2)

Douglas H. Troy

w00t! Magically updating links!

Thanks (to the person that corrected them)






Re: Visual Studio Tools for Office Deploying Visual Studio 2005 Tools for Office Second Edition Solutions Using Windows Installer (Part 1 of 2)

Bill Coan

Douglas,

Thanks for these insights. Since you're such a great help, let me lean on you for two additional related questions:

1. When I compile on my Vista machine, can I trust that the links between my executable and advapi32.lib will be valid on a WinXP machine Or is there some chance that the winVista version of the library will have some different entry points (Am I making any sense )

2. Why does MS make us compile our own copy of ComponentCheck.exe Why not provide that as part of the download Do they want the executable to carry a signature of where it was compiled Is it a licensing thing It seems like it would have saved everyone a lot of trouble if the executable could have been downloaded, instead of the cpp source file.