wayne wrote:
Hi FB
I know you are always so busy and we always keep asking for new features - but i was wondering if you had any plan to develop visual Library that wrapps the underlying generated DL classes?
Now the question is why and where would i use this? I am thinking in areas where i use visual control - grids and reporting. I always had this feeling that a visual LLBLGen control would be nice - so you could configure it at design time and connect it to grid.- but you don't want one for every DAL Object!!
If there was only a way to make design time databinding work I'd be very happy. All attempts have failed, I even sent code to Microsoft, they promissed to look at it a couple of times but never did. I heared from other people who also had to work with the gore details of design time databinding that it is simply broken, even for datasets (works ok in 2, 3 levels of hierarchies, goes bezerk when the hierarchy is 10 or higher as it seems). So the only thing I could conclude was that I have to wait till 2005 and the new interfaces which will offer design time support.
This is for self serv of course.
What i am talking about is Componenent that uses the Adapter Pattern to wrap a selected DAL Collection. - But how would you know which class to wrap?
I thought about it and came up with the following - You will drop this component on Design area - have a property in the inspector where you select an enum matching the name of the collection \ TypedList object in the DL - there after the visual component will use a simple factory to create an instance of the object being represented by the enum.
It is only an idea...what do you think? Will such a thing be usefull?
It will not work, as there is no way I could get the objects to work in the grid designers, where you select the datasource for a grid. It did work for some situations though, but failed miserably when 2 entities had a m:n relation so they point to eachother. Because the VS.NET 2003 ide is so crappy it only throws errors like "the specified method is not supported" at you, without telling you which method, where and why nor is there 1 line of documentation to get you started (not even in the vsip sdk) so I'm pretty much out of options. There is 0.0 documentation on this, so I can start writing some component which at design time fakes properties and what have you so you can make designers think they bind to some datasource, but that's not easy code, and I have no clue how to debug that, what to implement to get it working etc... After 3 weeks of trying I gave up. It's not good for your heart to keep trying to get that kind of code working without any documentation, I can tell you that
.