Instanciating an interface + Excel.Application

Sign in to answer this question.

• GU

  Guest User15y agoPosted Apr 4, 2011, 9:25 AM

  Accepted answer

  Although the Object Browser displays Application interfaces for the Microsoft Word and Microsoft Excel PIAs, it does not directly expose Application classes for Word and Excel. However, when you use the Application interface to instantiate an Application object, the common language runtime internally uses the Application class.
  
  http://msdn.microsoft.com/en-us/library/ms247302%28v=office.11%29.aspx
  
  
• 

  Vulpes15y agoPosted Apr 5, 2011, 6:20 AM

  No problem, Sam.

  
  

  I think it's a good question because most developers faced with Office interop just copy boilerplate code without worrying too much how it works.

  
  

  The problem now is remembering what the answer was if it comes up again :) 
• 

  Sam Hobbs15y agoPosted Apr 4, 2011, 10:52 PM

  I apologize. I did not understand the question. Probably my biggest mistake was assuming that the question is a beginner question; it is not.
  
  I deleted my message that was my second reply.
  
• 

  Vulpes15y agoPosted Apr 4, 2011, 7:36 PM

  I meant that the line which the OP gave won't work without the namespace alias which he said he'd put in.
  
  It would, of course, work if he used fully qualified names throughout.
• 

  Vulpes15y agoPosted Apr 4, 2011, 7:15 PM

  The OP said that "Excel" was an alias for a namespace so that line is certain to exist in his code and won't work without it.
  
  I also used it in my sample program for decompiling with .NET Reflector.
• 

  Sam Hobbs15y agoPosted Apr 4, 2011, 6:41 PM

  Are you sure there is not a line such as:
  
  using Excel = Microsoft.Office.Interop.Excel;
  
  Somewhere in the soruce code? If there is such a line, try commenting it out to see what happens.
• DR

  David Rougier15y agoPosted Apr 4, 2011, 4:27 PM

  Thank you for providing me information. The mechanism is clearer to me now.
• GU

  Guest User15y agoPosted Apr 4, 2011, 10:58 AM

  So that's how it does it.
  
  Thanks Vulpes!
  
• 

  Vulpes15y agoPosted Apr 4, 2011, 10:36 AM

  That's a useful link which John's dug out.
  
  
  The only place I've seen this previously was in an obscure book I have on Office interop.
  
  
  The Application class is well and truly hidden and the Object Browser is unable to show it, probably because it can't cope with both an interface and a class, which are within the same namespace, having the same name!  However, if you look at this line:
  
  
    Excel.Application oXl = new Excel.Application();
  
  
  with Redgate Reflector, then it decompiles back to this line:
  
  
    Application application1 = (Application) Activator.CreateInstance(Type.GetTypeFromCLSID(new Guid("00024500-0000-0000-C000-000000000046")));
  
  
  proving that the Application object is created behind the scenes using its CLSID and then cast back to the Application interface. So evidently the C# compiler is somehow able to sort out what's needed.