BlazorWebFormsComponents

BlazorWebFormsComponents copied to clipboard

AdRotator needs to support the DataBinding features like:

• [ ] DataSource
• [ ] DataMember
• [ ] DataBinding Events
• [x] AlternateTextField
• [x] ImageUrlField
• [x] NavigateUrlField
• [x] OnAdCreated

I can work on this one ...

You got it @hishamco !

@csharpfritz is there ability to edit your first thread so I can check the one that have been done while I'm working on

I finished from the last 4 features, I will create another PR for DataBinding later on ...

Just thinking about DataSource I think we should do similar to what we did when we bound DataTable to GridView. Regarding DataMember I don't think I used in the past so your thought @csharpfritz?

@csharpfritz I start work to make AdRotator a DataBoundCompoment but the issue is both DataSource and DataMember are associate with DataSource controls in ASP.NET, so mark them as Obsolete may a better choice unless we need to bind it with DataTable but this need some efforts to map table columns to AdRotator properties

Your thoughts?

DataSourceID is used with DataSource controls in ASP.NET. DataSource and DataMember work with code-behind and DataBinding. Let's NOT mark those as Obsolete.

Agreed about rolling the same databinding interactions just completed for GridView to the other data bound controls

DataSourceID is used with DataSource controls in ASP.NET.

Oops, just forgot that one ;)

Agreed about rolling the same databinding interactions just completed for GridView to the other data bound controls

Sounds good, but the issue here is based on the convention to map the AdRotator properties