Error to use Chinese in ExcelFunction attribution

Dec 16, 2012 at 12:03 PM
Edited Dec 16, 2012 at 12:09 PM

Is the ExcelFunction attribution can only support English?

For example:


<ExcelFunction(Description:="返回section中包含value的文本")> _

will result in a fatal error when using Application.RegisterXLL in an xla file, but in English successed.

Dec 16, 2012 at 5:37 PM


What version of Excel are you using?

You can only use other languages under Excel 2007 and later.


Dec 17, 2012 at 7:13 AM

Thanks a lot.

Unfortunately, I've to test it under both 2003 and 2010 :-(

Dec 17, 2012 at 8:05 AM
Edited Dec 17, 2012 at 8:06 AM

OK - I expect Excel 2003 to just put in the replacement character '?' instead of the Chinese characters.

If you find that it actually crashes under Excel 2003 when using the latest version of Excel-DNA (from here: ), please let me know.


Dec 18, 2012 at 1:20 AM
Edited Dec 18, 2012 at 1:22 AM

I just recompiled it to .Net 4.0 after downloading your latest code, and then successed!

The Chinese characters are now displaying exactly under Excel 2003, no '?', no crash~

Thanks for your conscientious helping!

Dec 18, 2012 at 2:59 AM
Edited Dec 18, 2012 at 3:01 AM

I'm sorry, but occasionally it still failed in loading xll, and display an "Assert Failure" dialog:

Expression:[mscorlib recursive resource lookup bug]
Description: Infinite recursion during resource lookup within mscorlib. This may be a bug in mscorlib, or potentially in certain extensibility points such as assembly resolve events or Culture names. Resource name: Arg_AccessViolationException

Is there anyway to solve it?

Dec 21, 2012 at 9:39 AM

If you are able to make a small add-in (preferably just a .dna file) which reproduces this problem, you can paste here or email it to me and I would be happy to have a closer look.


Dec 22, 2012 at 12:04 AM
Edited Dec 22, 2012 at 12:05 AM

Hi Govert,

I created a simple solution to reproduce this problem and packed it into a .7z file. How can I send it to you? I cannnot find out your email address.


With further test, it seemed that the problem only appears in folder "c:\Users\Administrator\AppData\Roaming\Microsoft\AddIns\" where released files are deployed.

In contrast, it successed in path "bin\Release\".

(My test environment: Windows 7 + SP1, Excel 2003 + SP3, .Net 4.0.30319)


Best regards

Dec 22, 2012 at 8:10 AM


My email address is

I'm away for a few days, but can look at it next week.

Do you have a different set of files in the two folders? Maybe there is a different version of another .dll in the one place that is not in the other?


Jan 15, 2013 at 7:33 AM

Hi Govert,

I've already send you an email from at 2012-12-24. Have you received it?


Jan 15, 2013 at 12:28 PM


No - I didn't receive an email from you.