vsto namespace interop

Question

1.00/5 (2 votes)

See more:

Hi,

this is a question just asked out of curiosity. if someone could clarify, that'd be appreciated.

i just wonder how the compiler understands that what is implied is microsoft.office.interop.excel namespace when we write somthing like this

VB

dim wb as Excel.Workbook

even if there is no imports statement.

Posted 22-Sep-15 8:46am

ExcelinEfendisi

Add a Solution

Comments

Maciej Los 22-Sep-15 15:24pm

Compiler can understand Excel.Workbook as long as reference to Interop library is active ;)
General Reference (Office Development in Visual Studio)

ExcelinEfendisi 22-Sep-15 17:20pm

but, shouldn't be there a code like "Imports Excel=ms.off.interop.excel"
i cannot see any code like this.

Sergey Alexandrovich Kryukov 22-Sep-15 21:25pm

The problem is not that you don't see something, the problem that you don't show us what you see.
—SA

ExcelinEfendisi 23-Sep-15 9:47am

well, all the sample codes on the net include the code line "Imports Excel=ms.off.interop.excel", which makes "Excel" an alias for the interop namesapce.
but when start a project from scratch, even though i, myself, don't put a code like this and don't see it in any other file in the project, i am able to use the alias. what i am asking is how come this is possible? Is "Excel" default alias or something for the interop namespace?

Sergey Alexandrovich Kryukov 23-Sep-15 10:34am

There are two forms of "Imports" (which, by the way, doesn't "import" anything, it just changes the default naming of assembly-level types), alias and regular, non-alias...
—SA

ExcelinEfendisi 23-Sep-15 11:49am

didn't get a word of it, but anyway, i think i found the answer. in the properties >references, there is a section called Imported Namespaces, i found the "Imports Excel = microsoft.office.interop.excel "
statement over there. so, VS does this job automaticallay for us, which is cool :)

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

ExcelinEfendisi · Answer 1 · 2015-09-23T05:50:00

Solution 1

i think i found the answer. in the properties >references, there is a section called Imported Namespaces, i found the

Imports Excel = microsoft.office.interop.excel
statement over there. so, VS does this job automaticallay for us, which is cool :)

Posted 23-Sep-15 5:50am

ExcelinEfendisi