Databases
StackOverflow2013
Postsdbo
POWord 2003 plug-in installation on Server 2003
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWord 2003 plug-in installation on Server 2003
    text
    copied!<p>I've had someone else's pile of stuff handed to me. Among these items is a Word 2003 add-in (VSTO 2005 SE, .NET 2.0) that reportedly had been working fine in 2007, but our deployment environment calls for 2003. It installs apparently fine for Office 2003 -- no errors, shows up in add/remove -- but the toolbar is unavailable within Word itself.</p> <p>Supposedly this works fine in someone's test environment, but I've never seen it working in our common dev environment. We have a setup/deploy project with both a MSI and setup.exe. (I tried packing stuff in CABs just in case, I've tried it with prereqs indepdently installed, no apparent difference.)</p> <p>The MSI, the setup.exe, right-click installing the setup/deploy project in Visual Studio, none of these methods report an error -- but none of these methods succeed in showing the toolbar in Word 2003 on Server 2003 either. However, if I point Visual Studio at winword.exe for debugging and start the project, the add-in button shows up. It continues showing up on later, independent client startups. It remains available as a toolbar until I explicitly remove it via add/remove or right-click uninstall or running the MSI and removing.</p> <p>So now I'm at a loss -- what is happening by running in debug that isn't happening during a typical setup/deploy installation?</p> <p>EDIT: ok, updates. Created a clean VSTO 2005 add-in for Word 2003, new add-in name, clean slate. The same behavior is experienced with a naked project, virgin registry, on both Server 2003 and XP Pro. I'm a local admin on XP, I'm a domain admin on the 2003 box.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload