-
Same here. As soon as the page loaded, my eyes would go right to the blog posts and forum posts to see what was new.
-
Although I intend to use CSLA 4.5 on .NET 4.5, I think this is great news for those targetting .NET 4.
-
Couldn't the methods just return the non-generic Task? I believe you can await on that as well. Even though it looks funky in code: await dp.Fetch();
-
What if a new attribute was introduced, very similar to the RunLocal attribute, maybe RunLocalAsync? This could cause new DataPortal (and related) classes to be instantiated which are async/await aware so it doesn't break backward compatibility. The desire to use async/await on the "server" side really only applies when you are running
-
For what its worth, we are using full .NET and would certainly benefit from Task based support throughout CSLA. The data portal sure is getting messy as I read in another post ( http://forums.lhotka.net/forums/t/11428.aspx ). Perhaps it has come to the point of needing separate a separate .dll for each dataportal/platform. It seems that the 'noise'
-
In CSLA 4.5.1 (alpha) is it safe (or would it have the expected behavior) if you used await from within DataPortal_Fetch or DataPortal_Update/etc? In my particular case, the business objects retrieve and store all their data from a WCF service, in a service-oriented architecture (NOT using WCF data portal). It has been recommended to call WCF service
-
I agree as well "CSLA.NET for Silverlight" is the best name so far. Like the others, for a long time I believed CSLA Light was a subset of the framework.
-
I think that a book on using the framework with plenty of scenarios and examples (more than what ProjectTracker demonstrates currently) is far more valuable than the book(s) on the design/creation of the framework itself. I think it is safe to say that everyone here actually consumes/uses the framework, but only very few will actually look under the
-
haha, yeah i can imagine. im not using it for direct grid editing but certainly that would be unacceptable. perhaps as an enhancement you could make an overload of ApplyFilter which takes no parameters and just re-executes DoFilter using the current/existing _filterBy and _filter values.
-
I am using a FilteredBindingList that wraps an EditableRootListBase and I have a custom filter method which checks a date property of the business object for DateTime.MinValue (in effect, a blank date). So objects with a blank date should be INcluded in the filtered list, and when there is a date there, the item should be excluded from the list. This