Late Binding Question

[Siv]

hi,
I am converting an application that writes to an Excel spreadsheet and the
code trips the "option Strict" that I would like on because the parser says
"option Strict On disallows late binding", I am struggling to understand why
I am tripping this error.

This is the code that causes the problems:

XLApp.Goto("Mon thTitleTL") 'Goes to bookmark in sheet
r = XLApp.ActiveCel l.Row 'sets variable r equal
to the row of that cell
c = XLApp.ActiveCel l.Column 'Sets the c variable to
the column of that cell
For n = 0 To 11 'Process the 12 months of
data held in the T7Lines(n) collection
XLApp.Cells(r, c).Formula = T7Lines(n).Text MonthNumber
XLApp.Cells(r + 3, c).formula =
Format(T7Lines( n).RiskPointsTo tal, "0.0")
....
Next n

I don't get a) why this is classed as late binding? and b) what I do to stop
it other than turn off option strict which I don't want to do.

Any help appreciated.

Siv
Martley, Near Worcester, UK.

[Armin Zingler]

"Siv" <g@removethiste xtsivill.comsch rieb

I don't get a) why this is classed as late binding?

Without seeing a variable declaration, it's impossible to see if it's
late bound execution.

and b) what I do
to stop it other than turn off option strict which I don't want to
do.

1. Project -Add reference -COM tab -Add "Microsoft Excel x.y
Object Library"
2. Declare variables, for example, "As Excel.Applicati on"

Then you are bound to the referenced Excel version on the target
machine.
Armin

[Siv]

Armin,
Vars as follows:

In the procedure that the code was taken from:

Dim n as integer = 0
Dim r as integer = 0

The XLApp var is declared at the top of the class as follows:
Private XLApp As XL.Application

At the start of the processing block that calls the procedure I copied here,
I test if XLApp is already open and if not open it:

If IsNothing(XLApp ) Then
XLApp = New XL.Application
End If

I hope this is what you need.

Siv

"Armin Zingler" <az*******@free net.dewrote in message
news:uQ******** ******@TK2MSFTN GP05.phx.gbl...

"Siv" <g@removethiste xtsivill.comsch rieb

>I don't get a) why this is classed as late binding?

Without seeing a variable declaration, it's impossible to see if it's
late bound execution.

>and b) what I do
to stop it other than turn off option strict which I don't want to
do.

1. Project -Add reference -COM tab -Add "Microsoft Excel x.y Object
Library"
2. Declare variables, for example, "As Excel.Applicati on"

Then you are bound to the referenced Excel version on the target
machine.
Armin

[Siv]

Armin,
Vars as follows:

In the procedure that the code was taken from:

Dim n as integer = 0
Dim r as integer = 0

The XLApp var is declared at the top of the class as follows:
Private XLApp As XL.Application

At the start of the processing block that calls the procedure I copied here,
I test if XLApp is already open and if not open it:

If IsNothing(XLApp ) Then
XLApp = New XL.Application
End If

I hope this is what you need.

Siv

"Armin Zingler" <az*******@free net.dewrote in message
news:uQ******** ******@TK2MSFTN GP05.phx.gbl...

"Siv" <g@removethiste xtsivill.comsch rieb

>I don't get a) why this is classed as late binding?

Without seeing a variable declaration, it's impossible to see if it's
late bound execution.

>and b) what I do
to stop it other than turn off option strict which I don't want to
do.

1. Project -Add reference -COM tab -Add "Microsoft Excel x.y Object
Library"
2. Declare variables, for example, "As Excel.Applicati on"

Then you are bound to the referenced Excel version on the target
machine.
Armin

[Siv]

Armin,

I added the Excel reference using the "Microsoft.Offi ce.Interop.Exce l"
reference in the Dot Net tab. Does adding that as a COM object work better
and if so why?

The version of Excel being referenced is 11.0.0.0 version as the client is
using Office 2003.

Siv

"Armin Zingler" <az*******@free net.dewrote in message
news:uQ******** ******@TK2MSFTN GP05.phx.gbl...

"Siv" <g@removethiste xtsivill.comsch rieb

>I don't get a) why this is classed as late binding?

Without seeing a variable declaration, it's impossible to see if it's
late bound execution.

>and b) what I do
to stop it other than turn off option strict which I don't want to
do.

1. Project -Add reference -COM tab -Add "Microsoft Excel x.y Object
Library"
2. Declare variables, for example, "As Excel.Applicati on"

Then you are bound to the referenced Excel version on the target
machine.
Armin

[Siv]

Armin,

I added the Excel reference using the "Microsoft.Offi ce.Interop.Exce l"
reference in the Dot Net tab. Does adding that as a COM object work better
and if so why?

The version of Excel being referenced is 11.0.0.0 version as the client is
using Office 2003.

Siv

"Armin Zingler" <az*******@free net.dewrote in message
news:uQ******** ******@TK2MSFTN GP05.phx.gbl...

"Siv" <g@removethiste xtsivill.comsch rieb

>I don't get a) why this is classed as late binding?

Without seeing a variable declaration, it's impossible to see if it's
late bound execution.

>and b) what I do
to stop it other than turn off option strict which I don't want to
do.

1. Project -Add reference -COM tab -Add "Microsoft Excel x.y Object
Library"
2. Declare variables, for example, "As Excel.Applicati on"

Then you are bound to the referenced Excel version on the target
machine.
Armin

[Siv]

Armin,
Sorry about the multiple posts, Windows Mail jus threw a wobbly and kept
refusing to send outbound then after a restart decided to send all the
attempts before I had chance to delete them.

I wanted to add that the XL reference comes from an "Imports" at the top of
the class:

Imports XL = Microsoft.Offic e.Interop.Excel

Then I do:
Private XLApp as XL.Application at class level.

Hope this makes sense?

Siv

"Armin Zingler" <az*******@free net.dewrote in message
news:uQ******** ******@TK2MSFTN GP05.phx.gbl...

"Siv" <g@removethiste xtsivill.comsch rieb

>I don't get a) why this is classed as late binding?

Without seeing a variable declaration, it's impossible to see if it's
late bound execution.

>and b) what I do
to stop it other than turn off option strict which I don't want to
do.

1. Project -Add reference -COM tab -Add "Microsoft Excel x.y Object
Library"
2. Declare variables, for example, "As Excel.Applicati on"

Then you are bound to the referenced Excel version on the target
machine.
Armin

[Siv]

Armin,
I changed the line:

rng = XLapp.Cells(She etRow, SheetCol)

to

rng = DirectCast(XLAp p.Cells(SheetRo w, SheetCol), XL.Range)

Which the parser is happy with; whether it works when I run it is another
question!

I will now try and figure how I apply that to the

XLApp.Cells(r + 3, c).formula = Format(T7Lines( n).RiskPointsTo tal, "0.0")

Lines??

I have temporarily changed the late binding error as a warning and when I do
that the green wavy line appears under the left side of the argument. I
still don't understand why the compiler thinks this is late bound?? As far
as I can see all the variables are determined so that r+3 and c are known
values? I never did get what all the fuss about late binding is?

Thanks,

Siv
"Armin Zingler" <az*******@free net.dewrote in message
news:ew******** ******@TK2MSFTN GP02.phx.gbl...

"Siv" <g@removethiste xtsivill.comsch rieb

>Armin,

I added the Excel reference using the
"Microsoft.Off ice.Interop.Exc el" reference in the Dot Net tab. Does
adding that as a COM object work better and if so why?

Did you already have that reference before asking, or did you just add
it now? Inferred from your question, I thought you did not have any
reference yet. Obviously the PIAs (primary interop assemblies) are
installed on your machine. In this case, it's the preferred way instead
of the COM reference. The PIAs are taylor-made by the manufacturer of
the COM component (Excel). Otherwise, when setting the COM reference,
the Interop assembly is created by a standardized COM-Import procedure
that possibly doesn't fit 100% perfect and is recreated in every project
and every time you set a reference to the COM component.

Assuming that you have a reference to the assembly, the problem
is probably because the type of the default property of a range object
is "Object". Not every object has a property "Formula". Therefore the
error message. You'll have to cast it to the expected type. I don't know
it by heart; something like

Directcast(XLAp p.Cells(r, c), DestinationType ).Formula ....
Armin

[Siv]

Armin,

This seems to pacify the compiler:
DirectCast(XLAp p.Cells(r, c), XL.Range).Formu la = T7Lines(n).Text MonthNumber

I will see if the program runs as expected after I have corrected all
sections that need amending.

I tried

Siv

"Siv" <g@removethiste xtsivill.comwro te in message
news:C7******** *************** ***********@mic rosoft.com...

Armin,
I changed the line:

rng = XLapp.Cells(She etRow, SheetCol)

to

rng = DirectCast(XLAp p.Cells(SheetRo w, SheetCol), XL.Range)

Which the parser is happy with; whether it works when I run it is another
question!

I will now try and figure how I apply that to the

XLApp.Cells(r + 3, c).formula = Format(T7Lines( n).RiskPointsTo tal, "0.0")

Lines??

I have temporarily changed the late binding error as a warning and when I
do that the green wavy line appears under the left side of the argument.
I still don't understand why the compiler thinks this is late bound?? As
far as I can see all the variables are determined so that r+3 and c are
known values? I never did get what all the fuss about late binding is?

Thanks,

Siv
"Armin Zingler" <az*******@free net.dewrote in message
news:ew******** ******@TK2MSFTN GP02.phx.gbl...

>"Siv" <g@removethiste xtsivill.comsch rieb

>>Armin,

I added the Excel reference using the
"Microsoft.Of fice.Interop.Ex cel" reference in the Dot Net tab. Does
adding that as a COM object work better and if so why?

Did you already have that reference before asking, or did you just add
it now? Inferred from your question, I thought you did not have any
reference yet. Obviously the PIAs (primary interop assemblies) are
installed on your machine. In this case, it's the preferred way instead
of the COM reference. The PIAs are taylor-made by the manufacturer of
the COM component (Excel). Otherwise, when setting the COM reference,
the Interop assembly is created by a standardized COM-Import procedure
that possibly doesn't fit 100% perfect and is recreated in every project
and every time you set a reference to the COM component.

Assuming that you have a reference to the assembly, the problem
is probably because the type of the default property of a range object
is "Object". Not every object has a property "Formula". Therefore the
error message. You'll have to cast it to the expected type. I don't know
it by heart; something like

Directcast(XLA pp.Cells(r, c), DestinationType ).Formula ....
Armin

[Lloyd Sheen]

"Siv" <g@removethiste xtsivill.comwro te in message
news:B3******** *************** ***********@mic rosoft.com...

Armin,

This seems to pacify the compiler:
DirectCast(XLAp p.Cells(r, c), XL.Range).Formu la =
T7Lines(n).Text MonthNumber

I will see if the program runs as expected after I have corrected all
sections that need amending.

I tried

Siv

"Siv" <g@removethiste xtsivill.comwro te in message
news:C7******** *************** ***********@mic rosoft.com...

>Armin,
I changed the line:

rng = XLapp.Cells(She etRow, SheetCol)

to

rng = DirectCast(XLAp p.Cells(SheetRo w, SheetCol), XL.Range)

Which the parser is happy with; whether it works when I run it is another
question!

I will now try and figure how I apply that to the

XLApp.Cells( r + 3, c).formula = Format(T7Lines( n).RiskPointsTo tal, "0.0")

Lines??

I have temporarily changed the late binding error as a warning and when I
do that the green wavy line appears under the left side of the argument.
I still don't understand why the compiler thinks this is late bound?? As
far as I can see all the variables are determined so that r+3 and c are
known values? I never did get what all the fuss about late binding is?

Thanks,

Siv
"Armin Zingler" <az*******@free net.dewrote in message
news:ew******* *******@TK2MSFT NGP02.phx.gbl.. .

>>"Siv" <g@removethiste xtsivill.comsch rieb
Armin,

I added the Excel reference using the
"Microsoft.O ffice.Interop.E xcel" reference in the Dot Net tab. Does
adding that as a COM object work better and if so why?

Did you already have that reference before asking, or did you just add
it now? Inferred from your question, I thought you did not have any
reference yet. Obviously the PIAs (primary interop assemblies) are
installed on your machine. In this case, it's the preferred way instead
of the COM reference. The PIAs are taylor-made by the manufacturer of
the COM component (Excel). Otherwise, when setting the COM reference,
the Interop assembly is created by a standardized COM-Import procedure
that possibly doesn't fit 100% perfect and is recreated in every project
and every time you set a reference to the COM component.

Assuming that you have a reference to the assembly, the problem
is probably because the type of the default property of a range object
is "Object". Not every object has a property "Formula". Therefore the
error message. You'll have to cast it to the expected type. I don't know
it by heart; something like

Directcast(XL App.Cells(r, c), DestinationType ).Formula ....
Armin

You were asking about why late binding is "bad". When you late bind there
is a perfomance penalty to pay for each call. Since the compiler does not
know what type of object is being used until runtime it must each time
determine whether or not the property, function or subroutine is valid for
the target object at runtime. This takes time.

There is also the possiblity that the object at runtime will not support the
call. This will result in an exception which can be trapped using try -
catch but again this is very costly in comparison to an early binding call.

So really two reason not to use late binding if you can. One performance
and second program integrity.

LS