Map2Excel for Excel 2016 and MindManager 2016
First, apologies for slow responses to blog comments and emails. The MindManager world has been pretty quiet for the past few years and I’m not using it as intensively, so there is a bit of activation energy to catch up on emails and to dive back into Visual Studio to tweak things. Thank you to those who have purchased the add-in.
I had a user interested in using the Map2Excel add-in with Excel 2016, so I bit the bullet and upgraded my system via Office365 to Excel 2016, and recompiled Map2Excel with the Office 2016 libraries.
I don’t know to what extent this install is backward compatible with previous versions of Excel. For now it is identical to previous versions in terms of functionality and bug fixes so go ahead and use earlier installs if needed.
Ian Sutherland said,
October 26, 2016 @ 10:28 am
I have mindmanager 2016 and Excel 2010. Any chance that this will work for that combination?
It is not worth my while upgrading Office right now, just to get this export.
ActivityOwner said,
October 27, 2016 @ 6:01 am
Hi Ian — I am not sure if this build would work with Excel 2010. It might. Give it a try. There is a trial period. I can keep multiple versions of MindManager on my machine but only one version of Excel, so it isn’t straight forward for me to create all the possible MM-Excel combinations, but I can look into it if there is a strong need from someone.
Travis Carnahan said,
January 29, 2017 @ 10:55 am
Can anyone confirm that Map2Excel for MindManager 2016 works with Excel 2010?
ActivityOwner said,
January 29, 2017 @ 1:13 pm
Haven’t had any negative reports. Initially I expected it would only work with latest 2016 Excel I’m compiling it based on, but seems to be backward compatible. You should be able to test it.
Having trouble getting MindManager 2012 to work with 2016.
Travis Carnahan said,
January 29, 2017 @ 2:38 pm
Thanks! I attempted to download MindReader for MindManager 2016 and got a message the file could not be located.
ActivityOwner said,
January 29, 2017 @ 3:14 pm
Hi Travis — sorry about that. Link is fixed now.