I created a VSTO Excel 2003 addin and a setup project. It works perfect in Excel 2003 and Excel 2007.
When I install the addin in Office 2000. I getting the following error...
"The Common Language runtime could not
be loaded... contact
your administrator"
No exception Sad
Since for Office 2000 we need to use the PIA of office 2000. I created the Office 2000 PIA manually and included it in the project and build the project.
The same setup file(office 2000 pia) is working fine in office 2003/2007.
I made the copy local property to true...
Could you please help me what I am missing on this... why it is not working in office 2000...
The only suggestion I can make is to go to the msdn forums...
social.msdn.microsoft.com/Forums/
Related
All VBA projects fail to work, if you use Excel, the VBA project deleted when trying to open the workbook, if it is Access, no application works because it does not find any project.
For what I've had been researched and tested, apparently the reason is the Windows 10 update, I focused exclusively on the Office 2010, seeing macros, security, library references etc, but it seems that Windows is the problem and not the Office itself. This problem appeared 3 days ago, before that everything worked fine.
I would appreciate your help if someone else had the same problem and how you solve it.
I have Windows 10 Home, and I tried with Office 2010 (my original base Office) and then I install Office 2016 hoping to solve it, but nothing works.
Thank you very much in advance.
uninstall and install again Office 2010 with all the features (including VBA).
Macro security fully enabled
VBAProject references ok
Microsoft Visual Basic for Applications install correctly.
Install Office 2016, to try if the problem solved
Reinstall Windows 10 Home 64 to the factory line.
One of my add-ins, Formula Formatter, works well in Office 365. However, one client told me it cannot be loaded in Office Professional Plus 2016.
Does anyone know what may be the reason? Should we do something special in the manifest xml for Office Professional Plus 2016?
In its manifest, Formula Formatter specifies the requirement set ExcelAPI with a minimum version of 1.2. Per the documentation for that requirement set (https://dev.office.com/reference/add-ins/requirement-sets/excel-api-requirement-sets) your customer will need to be running "Version 1601 (Build 6741.2088) or later". Customers that have a non-subscription version of Office won't have that requirement set.
If you remove the requirement set from the manifest, your add-in would be available on Office 2016 but you would need to ensure that your add-in has a good user experience when they are not present.
I made a excel spreadsheet using office 2013 and it works fine. But when i try to open it in office 2010 it will crash when retrieving data.
My configuration: office 2013 - x64
Client: office 2010 - x32
data source: odbc
I have no clue what is wrong,
what have i tried:
if i do click on edit query and run the query it runs but as soon as i hit the button to take the data back to office it will just crash.
Have you tried installing powerpivot for office 2010?
This may give you a cleaner and more powerful solution, adaptable in both versions of Excel
I have a couple of Excel Add ins. If I move to Office 365, will these add ins be available ? Is there any development support(VSTO) for Office 365 ?
I to have been curious about the answer to this, so went looking online. From the following site, I'd say the answer is no. It looks like developing for Office 365 is more along the lines of SharePoint development.
http://blogs.msdn.com/b/donovanf/archive/2011/06/29/office-365-developer-guidance-and-resources.aspx
I have seen advertisements online for products such as this... http://www.ocxt.com/products that look like they could provide a possible solution for taking a vsto application to the web.
I think things have moved on substantially since this question was asked. Microsoft seem to be fully committed to the Add-in approach with Office 2013 and the equivalent VSTO tooling available in VS2012.
The Office Dev Center home page has Office 2013 and VSTO Add-ins written all over it.
This MSDN Blog Post also clearly shows Add-ins are still part of the strategy.
Until the full capabilities of Desktop MS Office are available in a browser, I can't see this situation changing.
If you mean Office 365 installed on client PC then there is no issue with VSTO Add-ins. Our Chem4Word Add-in is using Office 2010 VSTO and happily works with 2010, 2013, 2016, 2019, O365.
If you mean Office 365 on-line then you have to redesign them using the Office 365 Javascript API
I have a site developed in Microsoft Office SharePoint server 2007 and I have installed Microsoft office 2010 on my machine. When I try to access excel file stored in document library. It gives me an error saying that it requires a Windows SharePoint Services compatible application.
It was working fine when I have Microsoft office 2007. So I am confused whether SharePoint is compatible with office 2010 or not...?
Thanks
Sachin
Yes it is compatible and it should work. A number of things could be going on.
The OWSSUPP.DLL may not be registered correctly.
You could register it manually or reinstall
If you have the 64 bit version of office there are some known issues opening data in SharePoint.
http://www.knowsharepoint.com/2010/06/sharepoint-datasheet-view-and-office.html
Windows SharePoint Services Support files may not be installed.
in this case install these through Add/Remove programs. It's in the office tools section of the MS Office application.
If you have some applications that were part of Office 2003 or earlier you may need to uninstall them.