I understand that since Whidbey Beta 2 is a beta version, that what I'm asking is probably not supported, but here goes.

Has anyone had any success with enabling design-time databinding support? I've gone to the Toolbar and added a reference to my collection classes, but nothing shows up under the toolbox. Any ideas? Thanks.

JW

Hmm. When I add a generated code project to a solution and I build that, I get the objects added to my toolbox automatically in beta2. ... Strange.

Otis wrote:

Hmm. When I add a generated code project to a solution and I build that, I get the objects added to my toolbox automatically in beta2. ... Strange.

Hmm. Ok, it works with Winforms, but not with ASP.NET. I wonder why?

junior882 wrote:

Otis wrote:

Hmm. When I add a generated code project to a solution and I build that, I get the objects added to my toolbox automatically in beta2. ... Strange.

Hmm. Ok, it works with Winforms, but not with ASP.NET. I wonder why?

Well, databinding in asp.net always has been a bit of a problem. You need to setup objectdatasource thingies if I recall correctly with aspnet 2.0 though I haven't tried that myself yet, as I barely touched .net 2.0 beta 2

Otis wrote:

junior882 wrote:

Otis wrote:

Hmm. When I add a generated code project to a solution and I build that, I get the objects added to my toolbox automatically in beta2. ... Strange.

Hmm. Ok, it works with Winforms, but not with ASP.NET. I wonder why?

Well, databinding in asp.net always has been a bit of a problem. You need to setup objectdatasource thingies if I recall correctly with aspnet 2.0 though I haven't tried that myself yet, as I barely touched .net 2.0 beta 2

Otis,

Thanks for your time on this. I've been playing with the ObjectDataSource, setting it to a collection class's, GetMulti method. Unfortunately, I can't get it to recognize any of the properties for the collection. That's all I was really looking for....some way to get access to the properties of the collection instead of having to know the column names and manually type them in when selecting the data elements to display in the grid, etc.

Other than that, LLBLGEN works just as awesome as it always has under beta 2. I think it would be cool to add/fix support for ObjectDataSources at some point since it does seem like it could be a pretty big production booster.

Thanks again,

John Walker

junior882 wrote:

Otis wrote:

junior882 wrote:

Otis wrote:

Hmm. When I add a generated code project to a solution and I build that, I get the objects added to my toolbox automatically in beta2. ... Strange.

Hmm. Ok, it works with Winforms, but not with ASP.NET. I wonder why?

Well, databinding in asp.net always has been a bit of a problem. You need to setup objectdatasource thingies if I recall correctly with aspnet 2.0 though I haven't tried that myself yet, as I barely touched .net 2.0 beta 2

Thanks for your time on this. I've been playing with the ObjectDataSource, setting it to a collection class's, GetMulti method. Unfortunately, I can't get it to recognize any of the properties for the collection. That's all I was really looking for....some way to get access to the properties of the collection instead of having to know the column names and manually type them in when selecting the data elements to display in the grid, etc.

I've planned to build a vs.net 2005 version of the runtime code, and will see if I can add the extra code so vs.net 2005 can recognize what's already there. I am a bit surprised though that ASP.NET 2.0 completely ignores .NET 1.x standards like ITypedList, although looking at their trackrecord I'm not that surprised...

Other than that, LLBLGEN works just as awesome as it always has under beta 2. I think it would be cool to add/fix support for ObjectDataSources at some point since it does seem like it could be a pretty big production booster.

I'll see what I can do. Expect something in the next few weeks.