As CSLA moves forward and is built to work with Silverlight 5, I worry a bit (maybe needlessly) as there is a nasty little rumor going around that suggests Silverlight 5 is IE only. I don't believe they would do that as it goes against the principles of Silverlight in my opinion, but if they do - we simply can't move to Silverlight 5.
I'd suspect many would be in the same camp.
What is the implications for those of us trying to keep up with the latest versions of CSLA / would we still be able to build the latest CSLAs against SL 4?
I don't know the truth of this rumor one way or another.
SL5 adds some new features/capabilities over SL4. Many of them bring more .NET parity, meaning I can remove #if statements to bring some SL code more in line with .NET code - unifying the code base. These changes to the Csla project shouldn't be all that substantial.
SL5 also adds some features/capabilities in the XAML side of things - UI focused. This impacts the Csla.Xaml project for SL, and in most cases also brings things more in line with .NET/WPF (like having a data context changed event). Some of these changes might result in more substantial changes to controls like PropertyStatus.
Once we change the 4.3 code to build using the SL5 features, that code won't build for SL4 any longer - kind of by definition.
Any idea what the eta is on the next release of CSLA for SL5? Do you know if simply compiling v 4.2.2 against SL5 will run properly?
Any idea what the eta is on the next release of CSLA for SL5? Do you know if simply compiling v 4.2.2 against SL5 will run properly?
My limited use of 4.2 with SL5 has revealed no issues. There could be some I haven't encountered, but all the basic functionality is fine.
I don't expect 4.3 to be a radical departure - the changes I anticipate are mostly removal of #if SILVERLIGHT statements where SL5 has caught up with .NET 4 in certain feature areas. And maybe some Csla.Xaml changes to use things like DataContextChanged if I have time.
In reality, the biggest change is probably Sergey's changes to serialization, with major improvements in terms of byte size reduction. Major enough to mean compression probably won't be necessary for any but the most extreme scenarios.
I expect 4.3 will be feature complete by mid-Feb, and released by mid-March.
Because 4.2 appears to work fine in SL5, I don't feel tremendous time pressure, so I want to allow time for other wish list items to get done as people's schedule permits.
This is the minimum system specs for SL5:
http://www.microsoft.com/getsilverlight/locale/en-us/html/installation-win-SL5.html
According to this table Firefox, Safari and Chrome are still supported as well as Mac os.
The SL4 spec for comparison is here: http://www.microsoft.com/getsilverlight/locale/en-us/html/installation-win-SL4.html
Copyright (c) Marimer LLC