DavidThi808

Hi;

I am trying to figure out the KB908002 bootstrapper and have a couple of questions. This is all based on the download at http://support.microsoft.com/default.aspx/kb/908002

  1. This includes the files for both KB908002 and KB907417 - correct
  2. This puts the two msi and one exe file in the bootstrapper - there is no way to have it download them only if needed - correct
    1. If there is a way to have them downloaded only if needed - how do we do that Granted they are only 1/2 a meg but all the various hotfixes, PIAs, etc that are sometimes needed add up.
  3. The product.xml can be used to add this using GenerateBootstrapper in a MSBuild project - correct
    1. Is there anything special if it is used this way instead of through Visual Studio's setup project. (We use the MSBuild GenerateBootstrapper and WIX instead of the Visual Studio setup project system.)
  4. It appears that these three programs are always run and they then determine if they need to do anything - correct
    1. Is there a set of install conditions so they are not even run if it is Word 2003 and it has the service pack that includes these fixes. Or it is Word 2007 which already has these too

thanks - dave




Re: Visual Studio Tools for Office KB908002 bootstrapper questions

OmegaMan

Dave your post covers many grounds. I see you have used the forums extensively but here are some of the problems to answering this...

The link given specifies multiple different issues which most people are unaware of and subsequently limits the audience, such as myself, who could answer the issue by doing an in-depth comparisons between knowledge base issues.

IMHO - Its best to limit a post to one specific technical question to gather the most responses. Provide an example code or a scenario which needs to be solved. Then at the bottom of the post mention that you have researched it and am including the kb/support doc links and why. Good luck.





Re: Visual Studio Tools for Office KB908002 bootstrapper questions

Martin Sawicki - MSFT

Sorry you're having trouble. Let me try to address your points briefly and hopefully in a helpful manner:

Answer to #1: Yes

Answer to #2: The only component out of the three that are in the KB908002 bootstrapper that can be donloaded separately is the otkloadr.exe from KB907417 (which is exactly the same thing that's in KB908002, as you've probably figured out). The other two components are:

- extensibility.dll installer - and indeed there is no other distribution mechanism for it

- the "regkey" msi - all that this one does is set a single reg key. I don't know what problem you're trying to solve exactly, but if you're looking for a way to not have to include this particular MSI in your setup, then you could just write that regkey directly yourself in your own setup. The regkey is: HKEY_CLASSES_ROOT\Interface\{000C0601-0000-0000-C000-000000000046}. That's all.

Answer #3: You'd have to try it. I don't know. We've never tested that.

Answer #4: The lack of install checks is somewhat intentional. The matrix of all the different combinations of the exact conditions that could be checked for in order to avoid installing this or that component of the download was so complex, we figured it's better to just blindly install all of them always, and have the indiviudal patches (the extensibility.dll patch and the otkloadr patch) figure it out for themselves. I know it;'s not elegant and does some redundant stuff, but at least we know there isn't a situation where it doesn't work even though it should.

BTW - Word 2007 shouldn't generally need this (well, except for the extensibilty component.) KB908002 was meant for Word2003 and earlier.

But to step back a bit for a moment - the bigger story is that Shared Addins aren't exactly the recommended way to do .NEt development for Office anymore. My advice (or VSTO's advice in general) would be to start looking into switching to VSTO-based add-ins. One of the big reasons for VSTO 2005 SE, and especially its support foir Office 2003 addins, was exactly to provide developers with a increasingly better alternative. I know many folks perceive Shared Addins as flexible and version resilient, but are actually many undesirable issues with Shared Addins (the need for extensibility.dll and now these odd registry settings) and that we are making that approach to programming Office obsolete. VSTO addins is the strategic way forward. SE is an important step in that direction, and VSTO Orcas ("v3") will be even more about that.

Hope this helps.





Re: Visual Studio Tools for Office KB908002 bootstrapper questions

DavidThi808

Martin Sawicki - MSFT wrote:
But to step back a bit for a moment - the bigger story is that Shared Addins aren't exactly the recommended way to do .NEt development for Office anymore. My advice (or VSTO's advice in general) would be to start looking into switching to VSTO-based add-ins. One of the big reasons for VSTO 2005 SE, and especially its support foir Office 2003 addins, was exactly to provide developers with a increasingly better alternative. I know many folks perceive Shared Addins as flexible and version resilient, but are actually many undesirable issues with Shared Addins (the need for extensibility.dll and now these odd registry settings) and that we are making that approach to programming Office obsolete. VSTO addins is the strategic way forward. SE is an important step in that direction, and VSTO Orcas ("v3") will be even more about that.

Hi;

There are a couple of problems with using VSTO:

  1. We need to run on Word 2000 and later and VSTO as I understand it is Word 2003 and later.
  2. VSTO requires an associated template and that template must have an absolute location on the disk. This won't work for a commercial software product.
  3. No one has been successful creating a VSTO based product for general use - see http://msdn.microsoft.com/newsgroups/managed/default.aspx dg=microsoft.public.office.developer.com.add_ins&mid=e8029795-4b2a-4c53-9d90-5672f34920bb
  4. When I last tried VSTO (granted, the Word 2003 version) it was very fragile. All kinds of random bugs.

thanks - dave