Posted 23 Apr 2005
Link to this post
"Still, our grid has been Black-Box tested and it is fully operational. We can only guess what you mean by saying 'Does not seem to accept datasources', but the grid binds quite well with any kind of DataSource, even to such as AccessDataSource, available only in Whidbey. In other words our tests so far show that r.a.d.grid is .NET 2.0 ready. "
Ok. Tried once more. This is what I have done on 2 seperate machines:
1. Installed VS2005.beta.2. No earlier VS had ever been installed on the machines.
2. Made a new website. Added a sql2005 DB via the menus. Made a small table. Populated it with some testdata.
3. Downloaded rad.grid in zipped version. Added it to the toolbox, and copied the bin and rad.controls dir to the website folder root.
4. Dragged the rad.grid to the default.aspx page. Dragged the table to default.aspx page (this also creates a std ms grid that show the table columns ok, and run ok).
5. Went to the rad.grid's tasks.
6. Tried to click on rad.grid format. This link does nothing. Its inert.
7. Now, clicked on the last link, the property builder, which opens a window.
8. Clicked on general settings, and choose the datasource that corresponds to the new table/db I just made above. The dropdowns are empty btw.
9. Clicks ok on the property builder. I notice that the rad.grid columns does not reflect being bound to my table. The columnsnames are still column0, column1, etc. Btw, the MS grid shows the correct columnnames.
10. Runs the site. I only see the MS Grid.
Now, I tried variation of the above. You know, removing the MS grid, dragging the rad.grid *after* the table, and so on. But the result is the same.
I interpret the results as if the rad.grid is not compatible with the vs2005 designer even though its compatible with asp.net v2 - or - I'm just not doing it right.
Oh, and this is not meant as a critique. I fullly appreciate that vs2005 has just been released and one cannot expect software of this complexity, should work on a new platform, straight out of the box.
VS2005 is however the focus of my attention, which is why I try to get a feeling for the scope of issues confronting early projects on this technology. In that regard, Telerik is ahead of the curve ;-)