J
Jules
I know that Office XP provides a PIA (Primary Interoperabiltiy
Assembly) so that C# and VB.NET Applications can call into the Office
COM based interfaces.
But programming in C# is a real pain, because the all optional
parameters have to be filled in, resulting in enormous and meaningless
parameters lists ( The PIA/ COM interfaces do not support proper
method overloading) VB.NET is better. When Automating Office
Applications might as well contine to use VBA. The COM exposed
object model is not exactly intuitive.
I was expecting MS to be upgrading all their products to expose proper
..NET (Managed) Interfaces, and not rely upon clumsy Interoperability
mechanisms.
So much for the .NET revolution, it seems as though we are stuck with
COM for a long time yet !
Jules
Assembly) so that C# and VB.NET Applications can call into the Office
COM based interfaces.
But programming in C# is a real pain, because the all optional
parameters have to be filled in, resulting in enormous and meaningless
parameters lists ( The PIA/ COM interfaces do not support proper
method overloading) VB.NET is better. When Automating Office
Applications might as well contine to use VBA. The COM exposed
object model is not exactly intuitive.
I was expecting MS to be upgrading all their products to expose proper
..NET (Managed) Interfaces, and not rely upon clumsy Interoperability
mechanisms.
So much for the .NET revolution, it seems as though we are stuck with
COM for a long time yet !
Jules