Источник:
http://axdevposts.blogspot.com/2008/...blem-with.html
==============
If you're using CLR interoperability to access external logic, you can perform construct objectes two possible ways:
1. Add
Reference and then construct needed object
Microsoft.Office.Interop.Outlook._Apllication appl = new Microsoft.Office.Interop.Outlook.ApllicationClass();
2. Also you can use
CLRObject appl = new CLRObject("Microsoft.Office.Interop.Outlook.ApllicationClass") ;
Using th first approach you're strictly tied to certain version of assembly. So, for instance, if user doesn't have Office 2007, assembly reference in DAX 4.0 will not be compiled, since certain 12th version is specified on it. So to be sure user will not receive this problem it's preferable to use second approach. How ever then you don't have an option to use .NET intelisence.
I'm looking forward fixing this issue in DAX 2009
Источник:
http://axdevposts.blogspot.com/2008/...blem-with.html