I was wondering what is with all of this configuration stuff. In the past I only really used grids to display data. That last time I used Visual Studio it was version 2.0. The way I did it in the past was to create web forms that had blank text boxes that the end-user could fill out and then push a button that would call the datastring connection to the database that was located in the web.config file then use data objects and it then would instantiate class objects that would carry the information to a second tier that had all the class methodologies including calls to stored procedures to pass data to the third tier for the database that would then get the information and insert the data into the database. If the end user needed to delete something then they could then see the data item in the grid, click it which would then do the same aforementiond process. Updating would be done pretty much the same way. There was none of this entity framework LinQ stuff like you have today. It seems to me you are adding more layers of complication and this way is not as fast or as robust as doing it the other way I mentioned. IMO all of that seems like a lot of bother when there was much easier (for me at least) straight forward more
VB-C# codecentric method than having to mess so much with cubersome backend XML stuff by deleting this itemTemplate and modifying that ItemTemplate etc, etc. My question to you is whatever happened to that approach?
I just wondering why it is not being used anymore with the new version of ASP.NET 4.0?