Data Binding Expression Syntax

[JV]

I just converted a big web project from VB.NET to C# and I got some very
strange runtime errors. Apparently, throughout the ASPX pages, the VB
version of this project used the expression <%#
Container.DataI tem("columnName ") %> inside an <ItemTemplate > tag for
DataGrid. Apparently though this works fine in VB.NET, for some reason C#
chokes on it. I have found that replacing those expressions with <%#
DataBinder.Eval (Container.Data Item, "columnName ")%> makes the errors go
away, but I can't figure out why. It seems to me that the evaluation of
data binding expressions embedded in the ASPX page should work identically
in both languages?

Can anyone explain the arcane rules of this syntax?

[Eliyahu Goldin]

You should typecast Container. In the case of datagrid it will look like

<%# (DataRowView)Co ntainer.DataIte m("columnName ") %>

DataBinder.Eval uses reflection at runtime and, therefore, is much slower.

Eliyahu

"JV" <jo**********@g oisc.com> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..

I just converted a big web project from VB.NET to C# and I got some very
strange runtime errors. Apparently, throughout the ASPX pages, the VB
version of this project used the expression <%#
Container.DataI tem("columnName ") %> inside an <ItemTemplate > tag for
DataGrid. Apparently though this works fine in VB.NET, for some reason C#
chokes on it. I have found that replacing those expressions with <%#
DataBinder.Eval (Container.Data Item, "columnName ")%> makes the errors go
away, but I can't figure out why. It seems to me that the evaluation of
data binding expressions embedded in the ASPX page should work identically
in both languages?

Can anyone explain the arcane rules of this syntax?

[Sharon]

Maybe try:
<%# Container.DataI tem["columnName "] %>

"JV" <jo**********@g oisc.com> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..

I just converted a big web project from VB.NET to C# and I got some very
strange runtime errors. Apparently, throughout the ASPX pages, the VB
version of this project used the expression <%#
Container.DataI tem("columnName ") %> inside an <ItemTemplate > tag for
DataGrid. Apparently though this works fine in VB.NET, for some reason C#
chokes on it. I have found that replacing those expressions with <%#
DataBinder.Eval (Container.Data Item, "columnName ")%> makes the errors go
away, but I can't figure out why. It seems to me that the evaluation of
data binding expressions embedded in the ASPX page should work identically
in both languages?

Can anyone explain the arcane rules of this syntax?

[JV]

Tried that first, got another error.

"Sharon" <sh****@void.nu ll> wrote

Maybe try:
<%# Container.DataI tem["columnName "] %>

"JV" <jo**********@g oisc.com> wrote

I just converted a big web project from VB.NET to C# and I got some very
strange runtime errors. Apparently, throughout the ASPX pages, the VB
version of this project used the expression <%#
Container.DataI tem("columnName ") %> inside an <ItemTemplate > tag for
DataGrid. Apparently though this works fine in VB.NET, for some reason C#
chokes on it. I have found that replacing those expressions with <%#
DataBinder.Eval (Container.Data Item, "columnName ")%> makes the errors go
away, but I can't figure out why. It seems to me that the evaluation of
data binding expressions embedded in the ASPX page should work
identically
in both languages?

Can anyone explain the arcane rules of this syntax?

[JV]

Ah, yes, I didn't look into performance. I did see that I could typecast,
but I haven't seen that done anywhere and it looked a bit clunky, so I went
the other route. Also, this article
(http://msdn.microsoft.com/library/de...sionsyntax.asp)
seems to push the Eval method.

"Eliyahu Goldin" <re************ *@monarchmed.co m> wrote

You should typecast Container. In the case of datagrid it will look like

<%# (DataRowView)Co ntainer.DataIte m("columnName ") %>

DataBinder.Eval uses reflection at runtime and, therefore, is much slower.

Eliyahu

"JV" <jo**********@g oisc.com> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..

I just converted a big web project from VB.NET to C# and I got some very
strange runtime errors. Apparently, throughout the ASPX pages, the VB
version of this project used the expression <%#
Container.DataI tem("columnName ") %> inside an <ItemTemplate > tag for
DataGrid. Apparently though this works fine in VB.NET, for some reason C#
chokes on it. I have found that replacing those expressions with <%#
DataBinder.Eval (Container.Data Item, "columnName ")%> makes the errors go
away, but I can't figure out why. It seems to me that the evaluation of
data binding expressions embedded in the ASPX page should work
identically
in both languages?

Can anyone explain the arcane rules of this syntax?

[Bruce Barker]

C# is morte typesafe than VB as does not support late binding (except thru
the .net reflection api). the expression inside <%# %> must be a valid C$
expression amd return a string. for most binding objects, an object is
returned. aslo if you use an indexer, you must switch from () to []. the
DataBinder.Eval was written for C# to help with handling this and some late
binding issues.

-- bruce (sqlwork.com)


"JV" <jo**********@g oisc.com> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..

I just converted a big web project from VB.NET to C# and I got some very
strange runtime errors. Apparently, throughout the ASPX pages, the VB
version of this project used the expression <%#
Container.DataI tem("columnName ") %> inside an <ItemTemplate > tag for
DataGrid. Apparently though this works fine in VB.NET, for some reason C#
chokes on it. I have found that replacing those expressions with <%#
DataBinder.Eval (Container.Data Item, "columnName ")%> makes the errors go
away, but I can't figure out why. It seems to me that the evaluation of
data binding expressions embedded in the ASPX page should work identically
in both languages?

Can anyone explain the arcane rules of this syntax?

[Cor Ligthert]

Bruce,

In all Net languages is a procedure stated with (). In VBNet is that as well
for a index from a collection or an array where that is in the C languages
[].

Most VBNet programmers have Option Strict On in there IDE by what is dynamic
binding of an object prevented in the code. (Late binding by reflection is
in all languages allowed).

For all the dotNet languages is the code for the Databinder Eval exact equal
when it is done in the ASPX part.

http://msdn.microsoft.com/library/de...evaltopic1.asp

Cor

[JV]

And actually that generates an error as well:

Compiler Error Message: CS0246: The type or namespace name 'DataRowView'
could not be found (are you missing a using directive or an assembly
reference?)

"Eliyahu Goldin" <re************ *@monarchmed.co m> wrote in message
news:%2******** ********@TK2MSF TNGP14.phx.gbl. ..

You should typecast Container. In the case of datagrid it will look like

<%# (DataRowView)Co ntainer.DataIte m("columnName ") %>

DataBinder.Eval uses reflection at runtime and, therefore, is much slower.

Eliyahu

"JV" <jo**********@g oisc.com> wrote in message
news:%2******** ********@tk2msf tngp13.phx.gbl. ..

I just converted a big web project from VB.NET to C# and I got some very
strange runtime errors. Apparently, throughout the ASPX pages, the VB
version of this project used the expression <%#
Container.DataI tem("columnName ") %> inside an <ItemTemplate > tag for
DataGrid. Apparently though this works fine in VB.NET, for some reason C#
chokes on it. I have found that replacing those expressions with <%#
DataBinder.Eval (Container.Data Item, "columnName ")%> makes the errors go
away, but I can't figure out why. It seems to me that the evaluation of
data binding expressions embedded in the ASPX page should work
identically
in both languages?

Can anyone explain the arcane rules of this syntax?

[JV]

Well, I think it's apparent that there is still a lot of confusion about
this, so it is not clearly enough documented.

What doesn't make sense to me is what the VB application works fine with
just <%# Container.DataI tem("someName") %> when the C# one does not. If
that is meant to be array syntax, then one would think that <%#
Container.DataI tem["someName"] %> would work, but it does not.

"Cor Ligthert" <no************ @planet.nl> wrote

Bruce,

In all Net languages is a procedure stated with (). In VBNet is that as
well for a index from a collection or an array where that is in the C
languages [].

Most VBNet programmers have Option Strict On in there IDE by what is
dynamic binding of an object prevented in the code. (Late binding by
reflection is in all languages allowed).

For all the dotNet languages is the code for the Databinder Eval exact
equal when it is done in the ASPX part.

http://msdn.microsoft.com/library/de...evaltopic1.asp

Cor

[Cor Ligthert]

JV,

Just Google and you get this page, in my opinion does it says everthing that
you ask for.

http://weblogs.asp.net/rajbk/archive...20/188868.aspx

I am fighting as well forever with the documentation from the eval on MSDN.
When I would have to tell what are the ten worst documented parts on MSDN.
Then I would surely have the Eval in it..

Cor