I am trying to convert an old Excel add-in to a new VSTO version. The present add-in reads data from an open Internet Explorer browser.
Since I.E will no longer be supported shortly, I am looking for a solution with an advance developing technology. The above issue is a major point without which this solution ill not be applicable.
Any help with a sample snippet will help.
Related
The web store 'Open In Excel' button does not work for Mac users. Excel indicates that it is downloading some file but then nothing happens. I'm sure expected behavior is that the workbook should open and install the add-in to Excel. Here is a video showing this, on Excel v16.40 (latest version as of this writing):
https://drive.google.com/file/d/1MqlZyqhYe9MfOzJN_sjpFwyPHOn4LuPD/view?usp=sharing
I became aware of this issue because some of our customers have contacted us, asking why the add-in wasn't working. Who knows how many potential customers we have lost because they simply thought the add-in wasn't supported on their system and moved on.
Is this a problem with our add-in code? Is anyone at Microsoft aware of this issue?
There are instructions online for sideloading an addin into Excel for Windows.
However, I get stuck on step 4. Namely, there is no Manage My Add-in's button anywhere within the MY ADD-INS page that I can find.
Does this button still exist somewhere, or are the instructions out of date? If the button is gone, is there any other easy way of side-loading an add-in into Excel?
There are other instructions online for sideloading an add-in, but they are much more complicated and hard to follow.
Thanks for any information!
The page that you linked to is for sideloading in Excel on the web, not Windows. For Excel on Windows, see Sideload Office Add-ins for testing. BTW, its best to work with the help on the learn.microsoft.com domain. The GitHub repo that you linked to is the source files and its harder to find your way around there.
I want to submit an add-in only for Excel Online (no Excel for Mac, no Excel for Windows).
Could anyone tell me if it is possible and how to configure the manifest xml file?
The Office store requires that the add-in works for Mac, Windows and Online with optional iPad support. It is not possible to select only some of the required platform. The same code that works on one platform should also work on the other with the addition effort being in the testing area.
Excel addin which uses Excel API 1.2. Add-in loads fine in Excel 2016 for Windows and Excel online. Save the file from Excel online and open in Excel 2013, addin fails to load in Excel 2013 with following errors:
When loading the Addin published in Store:
APP ERROR We can't load this app because we could not connect to catalog
When sideloading the addin from trusted catalog:
This app could not be started. Close this dialog to ignore the problem or click restart to try again
I know that Excel 2013 does not support Excel API 1.2. Could you please confirm the recommended way to make sure the add-in loads in Excel 2013?
• Should we use runtime checks using isSetSupported method?
• In such cases, how to debug which line of code is failing in Excel 2013 client?
• Is there any logging that can be enabled to troubleshoot such issues in Excel client?
I tried debugging a default add-in created by VS 2015 which uses Excel 1.2 API in Excel 2013. I added the following requirements set to the Manifest:
<Requirements>
<Sets DefaultMinVersion="1.2">
<Set Name="ExcelApi" />
</Sets>
</Requirements>
The addin also fails to load in Excel (15.0.4849.1003) when debugging using VS 2015. It works fine in Excel 2016 client.
I think there are two separate issues here (though there's a good chance that they're related, and the platform is simply giving the wrong error string. If so, let's confirm, and then I can file a bug to have us fix this).
Excel 2013 does not support the "ExcelApi" requirement set, which is a 2016 addition of the host-specific APIs (same goes for "WordApi"). If you specify ExcelApi in the requirements section of the manifest, as you have above, this will always fail to load in Excel 2013 -- by design. Essentially, you're requesting an API set and marking it as "required" for something that Excel 2013 does not support -- so it has no choice but to refuse to run it.
This is where the runtime check (isSetSupported) comes in. Please see my answer at Neat ways to get environment (i.e. Office version) for more details.
I am not sure what you mean by "how to debug which line of code is failing" or troubleshooting techinques. Essentially, any call to an Office 2016 API (anything in the ExcelApi set) from 2013 will result in a runtime failure...
Hope this helps!
I've been working intermittently on an Excel spreadsheet for a customer that does some pretty intense calculations. We implemented a security procedure using VBA... At first the requirements were relatively simple, and the overall lack of security in a spreadsheet was discussed and well understood.
Since then the customer has decided that he would like to have the sheet a bit more secure. Under normal circumstances I would simply disable the developer menu via code. Unfortunately I just recently found out that the customer, and many of his customers, are using Mac Office. (There are some customers that are even using 2008 and they found out the hard way that 2008 stopped supporting VBA)
My question is; is it possible to disable access to the Visual Basic editor in Mac Office in versions Pre 2008, and versions 2011 and after since from the research I've done so far points to a return of VBA support in Mac Office in 2011.
Unfortunately I do not have access to a Mac Office version to even really look through the application and or/test different solutions. In Windows it is possible to right click the VBA project and choose protection from the VBAProject Properties and choose "Lock project for viewing". Does this option exist and is it effective in Mac Office?
Any help/suggestions would be greatly appreciated.
I'm pretty sure you can lock projects in Mac Office the same way you can in Windows. Keep in mind that a project that has been locked in one version of Excel cannot be unlocked with a different version. So, if your customer needs to be able to unlock, they will need to use the same version of Excel you used to lock it.