Hi,

I'm confused by some text contained in the developers help:

In Breaking changes introduced in LLBLGen Pro v3.5 I read the following.

In the section titled 'ORMSupportClasses assembly is now split in two assemblies' it is mentioned that

To perform design-time actions, the datasource controls located in SD.LLBLGen.Pro.ORMSupportClasses.Web.dll have to be added to the toolbox, which makes them available when a webform is opened in VS.NET.

This section is followed by a section titled 'No more design time support for Entity Collection classes.' Added are some instructions on how to use entity collection.

I added the datasource controls by dropping the mentioned dll in the toolbox (Why is this not done automatically during installation?). This seems to work. It allows me to select EntityCollections. When I add a GridView and select the datasource as its data supplier, the columns from the datasource are shown in the grid. (There seem to be some bugs. When I change to source mode, edit something and return to display mode, the control tag seems to be wrong. When I then add a second datasource, a second assembly reference is added to the code.)

Please explain what is ment by 'No more design time support for Entity Collection classes.' What is missing compared to the previous version. Is the design time support limited to web based application? Should I use it?

Best regards,

Jan

JayBee wrote:

Please explain what is ment by 'No more design time support for Entity Collection classes.' What is missing compared to the previous version. Is the design time support limited to web based application? Should I use it?

Hi Jan. The note in the documentation means you can't drag-n-drop an EntityCollection class into a WinForm anymore. But the ASP.Net LLBLGenProDataSource(2) controls are supported as always, you just need to refecence the SD.LLBLGen.Pro.ORMSupportClasses.Web.dll assembly.

For WinForms you can still use them, but not as drag-n-drop them directly, but through BindingSources as explained in the Breaking changes section in the documentation.

For the part you said you have some bugs using LLBLGenProDatasource(2), please elaborate more (i.e. detailed steps to reproduce your problem, LLBLGen runtime library version you are using, etc).

Hi David,

I'm using the latest build, VS2010 sp1, Selfservicing.

When I edit / change something to the sourcecode of an aspx pagefile (i.e. not the cs), and return from source to designmode, the LLBLGEN datasource control gives an error regarding the label.

When I close the aspx and reopen it, it opens in soure mode. When I change to designmode, the error is no longer there.

I think this could be a VS2010 problem. It appears to be buggy.

Yes, there are a number of know buggy issues like that in VS.