Holy crap...looks like I may have just fixed the bug I shelved in May...this could be cool... ...tired...but stoked! It sucks that you cant return a type from a web service that derives from WebControl...to support the composite rendering paradigm...but then again it will be more efficient on the wire which aside from disk access is the greatest bottleneck. Bottom line, there are so many options in ASP.NET that it is unlikely that anyone will choose the correct design pattern without some gyrations...when it comes to writing composite databound controls. Template functionality is still in the works...but Im guessing the rendering will work fine once I adapt it to my state based control collection. The pain was getting my datasource to populate...based on using the DataSourceID and NOT having to write code in Page_Load to make a service call and then perform a DataBind. Your control should FIRST be able to work with a DataSourceID (are you listening MSDN?) and THEN be able to work with data sources...unless were teaching people crappy design patterns. Linq to SQL may cut it in the land of COSMOS and SCOPE, but not in the real world. :-o The way MSDN is written you are forced to meander through a discussion on rendered controls, which dont apply, because the only correct data source is the ObjectDataSource if you want to consume web services...and you do, because thats the correct design pattern. SOooo, thank you MSDN, for the exhaustive lesson in control writing. Im pretty sure were tracking again. Debugging serialization issues is fun! Not
Posted on: Wed, 10 Sep 2014 11:42:23 +0000
Trending Topics
Recently Viewed Topics
© 2015