VSTO using a document that relies on an XLA
 

I have a spreadsheet which uses an XLA that contains a couple of
methods. When I open the document normally there are no issues. When I
create a new VSTO solution based on that spreadsheet it complains
about linked data, asking me to update.

Now normally I'd expect it to go to the update links dialog, but this
never appears and my XLA method calls are all #NAMEd.

I may try moving the XLA based methods into the workbook's VBA
project, but the reason they're in an XLA is because they're shared by
many projects and copying them would be a maintenance nightmare.

Any ideas what I'm doing wrong? I've never been in a situation where a
VSTO project required an XLA before.

VSTO using a document that relies on an XLA
 

On Jun 6, 2:05*pm, DeveloperX wrote:
I have a spreadsheet which uses an XLA that contains a couple of
methods. When I open the document normally there are no issues. When I
create a new VSTO solution based on that spreadsheet it complains
about linked data, asking me to update.

Now normally I'd expect it to go to the update links dialog, but this
never appears and my XLA method calls are all #NAMEd.

I may try moving the XLA based methods into the workbook's VBA
project, but the reason they're in an XLA is because they're shared by
many projects and copying them would be a maintenance nightmare.

Any ideas what I'm doing wrong? I've never been in a situation where a
VSTO project required an XLA before.

Curiously opening the new copy directly with Excel works as expected,
so I hit run in VS and it seems to work fine, it must just be in the
designer that it doesn't.

Cheers
DevX