Does anyone know if there is a way to make an Excel 2003 Document Level Customization work with Excel 2010? When I try to execute this document level customization built on Excel 2003 and VSTO 2005 SE, I get the following error.
"The assembly * could not be found at or could not be loaded.
You can still edit and save the document. Contact your administrator or the author of this document for further assistance."
Any help would be appriciated.
Just to share with people what I've learned thus far.
Office 2010, specifically in this case Excel 2010, has 64bit compatibility issues with Document Level customizations and I think Add-Ins when executing solutions built on Excel 2003 files. This appears to be an issue more specifically with Visual Studio Tools For Office SE (VSTO) where the OTKLoader.dll, being 32 bit, can't be loaded by Excel 2010 64bit version.
Our specific test was to take an Excel 2003 Document Level customization built by Visual Studio 2008, and install it on a Windows 7 64 bit machine running Office 2010 64 bit. The error received is the error as stated in my original question.
We then took a Windows 7 64 bit machine running Office 2010 32 bit and installed the Office Business Application. The OBA, the documen level customization, executed without error.
You'll probably want to reference the following article from Microsoft.
"Compatibility Between the 32-bit and 64-bit Versions of Office 2010"
http://msdn.microsoft.com/en-us/library/ee691831.aspx
I personally haven't made it through the article completely, but there's enough descriptive text and some explict statements that lead me to believe that Office 2003 customizations, currently, are not compatible with Office 2010's 64 bit version.
Hope that helps someone out there. This was a real pain to sort out.
Note the options we're presenting at this time are to:
A: Only allow 32 bit versions of Office 2010.
B: All Office / Excel 2003 Document Level Customizations must be upgraded, at a minimum, to Excel 2007 solutions.
No you cant, because interop/vsto library you reference has to be different.
Excel 2003 works on VSTO 2005 SE whereas Excel 2010 needs VSTO 2010 library.
VSTO 2005 doesnt work with Excel 2010 and VSTO 2010 doesnot works Excel 2003.
To expand on your findings, Rob, yes, that is correct (you can). I believe the other contributor has made a mistake.
For 32-bit versions of Office, it will work (and it does, so you have found), but it will not work for 64-bit editions of Office. Microsoft clearly states this compatibility restriction (well, as a footnote at least).
See the MSDN article Running Solutions in Different Versions of Microsoft Office.
Under section "Running Office Solutions Created By Using Previous Versions of Visual Studio", you will see in the chart in the last row that using VSTO 2005 SE with a project template targeted for Office 2003 will run on Microsoft Office 2003, Microsoft Office 2007, and Microsoft Office 2010 (32-bit only).
It goes on further to say that you will be required to install the Visual Studio 2005 Tools for Office Second Edition runtime on the client's PC.
Your options that you described are correct. Those should be the only options that you have.
Related
I have a job involving old versions of VBA/Access code I'm tasked with fixing. To my utter dismay, the only version of Microsoft Office Developer Edition Tools I can find to fix this company's problems with their pre Office 2010 Access VBA coded screens is an Office 97 version, which is a vald license of the Microsoft Office 97 Developer Edition Tools. My question is this: supposing I get there and the guy has it coded in Office 2003. Am I going to have to go out on the web and try to find an old Developer Tools for 2003 just to do the work? Same thing if its 2007 I find in use. Basically, I need to know whether I can even do dev work on Office 2003 or 2007 or even 2010 without a developers licence, like we had to in the old days, or whether I will be able to edit & fix code issues in the older versions if the company I go to does not have the developers licence versions appropriate for the work in these older versions of Office. I know for a fact that, until the versions like Office 2013, 2016, and 365, you needed a dev licence that cost extra money but you can develop right out of the box on the newer ones. But that begs the question of what I will need to do the work in on of the version from the wayback machine, such as 2000, 2003, or 2007. Thats what I need an answer to.
I recently installed the Office 2016 32 bit edition on my Windows 10 Enterprise OS.
I had a Story Board Add-In with PowerPoint - Office 2013, which now does not work.
I can see the Add-In but when I click any of its menu items, I get this message:
TF86001: Team Foundation was unable to load the Office Add-In. This
may be caused by a Team Foundation Client installation problem or lack
of .Net programmability Support in the Office Application.
For more information, see the following Microsoft website:
http://go.microsoft.com/fwlink/?LinkId=220459.
So far I have tried the following steps:
- Reinstalled Office
- Repaired Visual Studio 2015 Enterprise Edition
- Reinstalled "Microsoft Visual Studio 2010 Tools for Office Runtime (x64)" from https://www.microsoft.com/en-us/download/confirmation.aspx?id=48217
My suspicion is that since I have a 32 bit version of Office 2016 on my 64 bit OS, I would need a corresponding 32 bit version of Visual Studio Tools for Office. I was able to download the 32 bit edition of the software but it was blocked from being installed by the OS.
Any suggestions? Hate that storyboard no longer works :-(
Finally found the solution.
As I suspected, I had to first remove all 32 bit editions of Office, including Office Pro, Visio & SharePoint Designer.
Then I installed Office 64 bit edition.
Went into File, Options, Add-Ins, Manage COM Addins.
Added "Team Foundation Add-in" and bingo the Storyboard menu came back
Click on "Storyboard Shapes" now works perfectly!
Some Explanation
It worked inb the Office 2013 32 bit version because Visual Studio Tools for Office allowed a 32 bit install. Since I installed the new version, VSTO ONLY allows the 64 version to be installed, i.e. it auto-detects your processor in the one installer file. Hence everything now has to be the 64 bit edition.
Is it posssible to write outlook 2007 add-in using visual studio 2013 in C#. Thanks for help.
According to Microsoft, the latest version of Visual Studio that can create an addin for Office 2007 is Visual Studio 2010.
If you want to develop an Office 2010 addin etc., you can use Visual Studio 2010 or Visual Studio 2012.
If you want to develop an Office 2013 addin etc., you can only use Visual Studio 2013.
Office Development and Visual Studio
This probably a bit late, but just for future reference: Running Solutions in Different Versions of Microsoft Office
There's no out of the box template for Office 2007 in Visual Studio 2013, but the addin will run fine in Office 2007.
Your project will have the Object Model for Office 2013 so while you can use it in previous versions of Office, you need to be careful not to call methods that aren't available in the earlier versions. For example in Outlook 2013 there is an inline reply so if you try to call that method in Outlook 2007 it will throw an exception.
If you're just looking to use the newer Visual Studio IDE for Office 2007 development then you can remove the 2013 Office references and add the 2007 references and you won't see any new methods as outlined above.
Edit: Not that you'd want to do this, but if you wanted to use the newer object model from 2007 without pulling in the interop library for 2013 you can actually call those newer methods dynamically and specify non existing delegate types by using Delegate.CreateDelegate, if anything it's pretty neat.
On my development PC, I uninstalled Office 2007 and installed Office 2010.
I have a VS 2010 Solution that has several Excel 2007 templates (projects).
When I open the Solution, VS wants to "upgrade" the project (to Office 2010). I cancelled out of that and in the VS options, I turned off "Upgrade to latest version of Office".
Now, the solution opens fine, but the Excel 2007 template projects will not load or open. All the clients that run this appication have Office 2007 intalled, so I need to be able to continue to develop this application and target Office 2007.
Can anyone tell me how to do that? (I downloaded and installed the Office 2007 PIA...)
Thanks!
As a rule I always suggest running the version of office on your development machine that you are targeting, otherwise you loose F5 support and things often don't work as they should.
Another point is that if you do upgrade to Office 2010, the add-in will still work on 2007, as long as you do not access any of the 2010 API's. So technically if you upgrade the project to 2010, then remove the reference to Microsoft.Office.Interop.Excel v14 and add v12, that will restrict you to office 2007 API's, and you shouldn't have a problem.
Just give it a go, upgrade the project, then try install it into Office 2007, it should work fine. If not, just undo/revert your local changes.
I think your problem is VSTO, VSTO 3.5 was office 2007, vsto 4 comes with VS2010 and is Office 2010.
You might check on what versions of VSTO are currently installed and make sure you've got the right ones.
I am struggling to apply an existing 32bit COM addin to 64bit Microsoft Word 2010.
To make the addin visible to Word, I have used the dllsurrogate-method, as it described here.
The problem is that now addin caused some strange exception when tries to add its toolbar and menu to office's. I cannot figure out, what it is, it seems, that the command bar reference became not valid in unpredicable moments.
Can anyone explain this?
Note, that everething is fine when I use the same addin under 32bit Microsoft Word 2010 and more old versions of Ms Office.
32-bit add-ins are not supported on 64-bit. Microsoft recommends to use the 32-bit version of Office unless you run into the memory limitations of a 32-bit process which is only likely to happen if you need to deal with extremely large spreadsheets:
The recommendations for which edition of Office 2010 to install are as follows:
If users in your organization depend on existing extensions to Office, such as ActiveX controls, third-party add-ins, in-house solutions built on previous versions of Office, or 32-bit versions of programs that interface directly with Office, we recommend that you install 32-bit Office 2010 (the default installation) on computers that are running both 32-bit and 64-bit supported Windows operating systems.
If some users in your organization are Excel expert users who work with Excel spreadsheets that are larger than 2 gigabytes (GB), they can install the 64-bit edition of Office 2010. In addition, if you have in-house solution developers, we recommend that those developers have access to the 64-bit edition of Office 2010 so that they can test and update your in-house solutions on the 64-bit edition of Office 2010.
If you need to go with the 64-bit version because of the memory limitations you have the following options:
If you have the source code, you can generate a 64-bit version yourself,
You can contact the vendor for an updated version,
You can search for an alternative solution.