*first what i have to say:
its first time for me to face an ILMerge problem(Like some other posters? realy???)
i need 1-2 day(s) to reproduce the problem because i have no experience with ILMerge - at all.
its a kind of magic. my current idea is ILMerge works in another AppDomain and the NetOffice enumerators are not ready to handle this for self-initializing. in other words: your Intialize() call is in your appdomain works well but ILMerge works in his own AppDomain and the first enumerator doesnt works because NetOffice miss the self-initializing check here. as possible hot fix and error trace for me: please try to call a foo[!] Application method or property before . (the methods and properties initialize the NetOffice.Core in his AppDomain but may the self-check is missing for enumerators possible bug)
(nice to know: did you use Office from multiple threads?)
*Sebastian
its first time for me to face an ILMerge problem(Like some other posters? realy???)
i need 1-2 day(s) to reproduce the problem because i have no experience with ILMerge - at all.
its a kind of magic. my current idea is ILMerge works in another AppDomain and the NetOffice enumerators are not ready to handle this for self-initializing. in other words: your Intialize() call is in your appdomain works well but ILMerge works in his own AppDomain and the first enumerator doesnt works because NetOffice miss the self-initializing check here. as possible hot fix and error trace for me: please try to call a foo[!] Application method or property before . (the methods and properties initialize the NetOffice.Core in his AppDomain but may the self-check is missing for enumerators possible bug)
(nice to know: did you use Office from multiple threads?)
*Sebastian