Hi there,

I am using adapter with subclasses. After generating the code I can add all relevant components to the toolbox of VS and do the binding. I observe two issues which i cannot understand: - When choosing the DataSource every entity I added appears twice in the dropdown list - When I open the winform in design modus the EntityFactoryToUse screen appears and I have to click cancel twice in order for it to disappear. I tried searching the forum for some hint and wasn't sucessful.

Any help would be appreciated

Best regards,

Eugene

PS A happy customer!!!!!

Forgut to mention that I am using the archive I downloaded after purchase (a few hours ago) with the subClass template.

eugene wrote:

Hi there,

I am using adapter with subclasses. After generating the code I can add all relevant components to the toolbox of VS and do the binding. I observe two issues which i cannot understand: - When choosing the DataSource every entity I added appears twice in the dropdown list

I also don't know why this is the case. Microsoft hasn't replied to my question on this, example code which should illustrate this feature also does the same thing, I think it's something with visual studio. It doesn't matter much, either name you pick works.

• When I open the winform in design modus the EntityFactoryToUse screen appears and I have to click cancel twice in order for it to disappear. I tried searching the forum for some hint and wasn't sucessful.

Hmm... That's strange. So you created a form, you dragged an EntityCollection instance on the form, you closed the form designer, you reopened the form's designer and you got again the designer for teh entity collection opened? (I ask this as it is a pain to try to mimic every possible scenario to find a bug with this databinding stuff unfortunately).

I restarted VS and then double clicked on the Form in the project explorer and the Factory-selection screen appeared. The screen disappers if I click cancel and the code written is not affected. So it is more of an nuisance than a real issue.

Best regards and thank you for your prompt reply!

Hmm, ok thanks for the feedback, I'll try to reproduce it here. Apparently I have to store some values somewhere that the object is 'added' to a form. The people who cooked up this design time stuff really had no clue whatsoever. Why do I have to keep track of all this if it is so obvious... Oh well...

Ok, reproduced. I'll check it out.

I show the selector when the Initialize method is called, and I check if the entity factory to use is null or not, if null, I show the selector. Of course, visual studio creates an empty object, THEN calls the initialize method and THEN deserializes back the set factory. I.o.w.: the selector should he shown at another time, but the only way to do that is by using a ToolItem object which is a facade and dragged from teh toolbox onto the form, creates the proper component and shows teh selector for the first time.

Problem is though... the type to create is not known to the toolitem, as far as I know, so if you add a derived entity collection class to the toolbox, it will not know that type. I'll try to find out if I can somehow retrieve that type and then I can fix it properly.

Ok, I fixed it! The toolbox item class thingy knew the base type after all. I don't know if it works in all scenario's so I'll release a hotfix for the runtime libraries to try it out first. Just recompile against this hotfix should do it. I'm not sure if you've to re-add the collection to the form).

Hotfix coming right up.

(edit) OK, the hotfix is live. Please let me know if this fixes your issue, and if you run into migration problems with the new hotfix.

Dear Otis,

I downloaded the hotfix and i no longer see the selection window upon opening the Winform Thank you for your effort.

Best regrads

Dear Otis,

My reply was incomplete, I am unable to do any migration tests since this is my first test with the designtime data bindig.

Greetings

eugene wrote:

Dear Otis,

My reply was incomplete, I am unable to do any migration tests since this is my first test with the designtime data bindig.

Greetings

That's ok, your feedback was already great. I'll move it into the installer later today.

Hi Otis,

you said that you'll move the changes (regarding the designtime behaviour of the EntityCollection) on the runtime into the installer. Today I downloaded the installer and the date it reflects is Monday, 22. November 2004. Are these changes included in the installer? I already have LLBLGen Pro running on my computer, so I don't want to install and reinstall in order to find this out.

Best regards

Not yet, as some oracle bugfixes are still in testing, and it's not that convenient to have a new installer every 2 or 3 days .