1

I have inherited an application built using the Microsoft Office Information Bridge Framework 1.6. My task is to make this application work with Office 2010.

I am testing this on a computer with the Office 2010 beta installed, including .NET programmability support for all features. When I try to install IBF 1.6, the installer won't complete, giving me the message: 

The following prerequisite components cannot be found:
.NET Programmability Support for Microsoft Office Word 2003
.NET Programmability Support for Microsoft Office Excel 2003
.NET Programmability Support for Microsoft Office Outlook 2003
.NET Programmability Support for Microsoft Office InfoPath 2003 SP1
Please install the necessary components and run Microsoft Office Information Bridge Framework installation again. 

However, it appears that if I first install Office 2007 on the computer, install IBF, and then upgrade to Office 2010, my application does work. 

Is IBF supposed to work with Office 2010? If so, is there a way to make the installer complete on a computer with Office 2010 installed? Or, is this just an issue with the Office beta that will be resolved in the final release? Or, will there be a hotfix to IBF to make it work with Office 2010, similar to how there was a hotfix to make it work with Office 2007?

I have already asked this question on a couple Microsoft forums, including the Office Information Bridge newsgroup, which has pretty much zero traffic, and the Microsoft Office 2010 Beta forum, but haven't gotten an answer yet. I'm hoping some other developers have the same issue and have had better luck, or maybe have ideas about what Microsoft forums might be better places to look for answers.

Thanks,
Amy

Amy T
  • 608
  • 8
  • 14
  • For what it's worth, I can now say this isn't "just a beta issue." Now that the Office 2010 RTM is available on MSDN, I have also tried the above steps with it and had the same issue. – Amy T Apr 26 '10 at 13:15
  • What's the url for this IBF? When you say "inherited" do you mean you've got all the source code? – CoderDennis Apr 26 '10 at 14:02
  • I mean that I have the source code for the application that uses IBF, not that I have the IBF source code. It's difficult to find good IBF URLs. Here's one, http://msdn.microsoft.com/en-us/library/aa167870(office.11).aspx, mostly containing broken links. I can't find anywhere on MS to download it anymore. It seems like MS released it in 2004 with much hype. Then it disappeared within a year or two, with a brief resurgence of articles when Office 2007 came out and there was an IBF hotfix to make it work with 2007. But maybe I'm just not looking in the right places to find it. – Amy T Apr 27 '10 at 09:05

2 Answers2

0

I am not familiar with the Information Bridge Framework, but if it is just a set of .NET DLLs, then you don't need to install it to get your app working. Just copy those DLLs into the same directory as your app's executable files.

The installer probably places the assemblies in the GAC, but you don't need that in order for your app to find them as long as they are .NET assemblies.

Edit: Wow, for something that old that was written for pre Office 2007, I'd say your best option would be refactoring your app to eliminate the dependency on IBF. A lot changed with Office 2007, so even if you could get it to work, it probably won't fit with the new paradigms and design of Office 2007 or 2010. Without diving too deep into the docs for IBF, it sounds like InfoPath might be current equivalent, but I don't really know either system well enough to say for sure.

Another course for finding a solution would be to identify the Microsoft Developer Evangelist for you area. I've had good success with asking questions of the DE here in the Dallas, TX area. When he doesn't know the answer, he can ask the right people within Microsoft and generally finds the answer. If you've exhausted your online search, that may be the best route.

CoderDennis
  • 13,642
  • 9
  • 69
  • 105
  • Good point. It looks like the installer does a bit more than just a set of DLLs, though. There are registry entries and custom actions. The end result of the install includes a new configuration app for it in the Windows Administrative Tools menu group and an add-in registered in Word. So far, rather than build a new installer, I'm wondering if I can just muck with the part of the current MSI that checks for Office PIAs. But I'd rather not end up tampering with MSI files that Microsoft created and released if there's any other solution. – Amy T Apr 27 '10 at 09:10
  • In response the the Edit: Lol. Yep, I'm all for rebuilding the app to remove the IBF dependency, but that's not what the business wants to hear, because that will take a bit of time. Since the IBF hotfix that MS put out for 2007 does make our app work with 2007, they just want me to find some similar magic for 2010. And it is tantalizingly close to working, since it seems only to be the IBF installer that's the problem. If we trick the Office 2010 machine into getting it all installed, the app and IBF work just fine. Great idea about talking to an evangelist, tho, will do that. – Amy T Apr 28 '10 at 08:35
  • After going through MSDN support, the answer I finally got from MS was that Office 2010 does not support IBF and we will need to rewrite our application not to use it. – Amy T Nov 03 '10 at 09:02
0

We (Windward Reports) have a number of customers that migrated from IBF to Windward because of the dropped support for IBF. I don't know IBF at all so I can't speak to what parts we match, but the feedack we have received is we do what it does and a lot more.

David Thielen
  • 28,723
  • 34
  • 119
  • 193