That’s excellent news!

Thanks!

No, you can install only one Office version. By MS design. So, Add-in Express will install your add-in for installed Office :)

BTW. On TechNet there is an interesting post about Office 2010 x64 – http://blogs.technet.com/office2010/archive/2010/02/23/understanding-64-bit-office.aspx

We will publish our regions (ADXOlFormsManager) redesigned for Office 2010 in beta 1. In general, beta 1 will include complete functionality compatible with all Office 2010 features. Have a look at http://www.add-in-express.com/creating-addins-blog/2010/03/05/visual-studio-2010-office2010/

That is all good news. I’m a bit unclear on where the bits we really need to test as soon as possible some into the schedule. We make use of AddinExpress.OL.ADXOlFormsManager and in particular ADXOlFormsCollectionItems to render some custom panes in Outlook for aour application. This is actually the only functionality that does not work fine right now in Outlook 2010. Where does that fit into the release schedule? Will it be available in the Beta 1 or Beta 2 or does that fall into “New Outlook regions designer” which is scheduled for the final release?

Thanks.

> Now that Microsoft has announced RTM in May will you be bringing forward the plans you currently have in place for 2010 releases?

Yes, of course.

> Also, will premium customers have access to early beta’s or code which can be used to verify current applications will run on 2010 as expected (obviously without support from you guys!)?

Yes, of course. Beta 1, beta 2 and builds at your request will be available for all our premium and professional subscribers.

Now that Microsoft has announced RTM in May will you be bringing forward the plans you currently have in place for 2010 releases? Also, will premium customers have access to early beta’s or code which can be used to verify current applications will run on 2010 as expected (obviously without support from you guys!)?

http://blogs.msdn.com/sharepoint/archive/2010/03/05/sharepoint-2010-office-2010-launch.aspx

Thanks,

Aaron.

I hope things are well with just like it is with me :)

That looks like an excellent solution to me so I’m really looking forward to use the next version.

Kind regards,
Dennis

Glad to hear from you :-)

We gave a dry run to development and deployment on our Add-in Express for IE (there are also two versions of IE, 32- and 64-bit) – one project and one setup project. The latter includes two loaders (32-bit and 64-bit) and installs / registers your add-in automatically depending on installed Office. As for the add-in project, it is compiled for any CPU. So, the only thing you need to do is to write bit-neutral code if you use WinAPI tricks or the like (the core of Add-in Express is redesigned bit-neutral).

Because we will face a scenario where both 32-bit and 64-bit version of Excel will be used within corporates it rase a question how Add-in Express .NET/VSTO will handle projects; will we be able to develop solutions in one project for both versions as well having to setups projects in one? The alternative is to work with two solutions side-by-side which is always a less good situation.

Any clients that will rush into 64-bit may put them in a less good position. For instance interacting with MDBs (i.e. “Access” databasaes) on a 64-bit platform will require a 64-bit driver. At present it’s not available. My point is that it will be better for us all if we all move slowly to the 64-bit.

Yes, I agree that corporates may move to Office 2010 from the 2003 versions. All inidications among my clients point to that direction as it fit in to their LCC-models. The same can probably be said about moving from XP to Windows 7.

Anyway, keep up the good work!

Kind regards,
Dennis gards,
Dennis