CSLA .NET 3.8.0 Beta 3 availableCSLA .NET 3.8.0 Beta 3 available
Old forum URL: forums.lhotka.net/forums/t/7917.aspx
RockfordLhotka posted on Friday, October 30, 2009
CSLA .NET 3.8.0 Beta 3 is now available for download
Beta 3 includes fixes for some bugs found in Beta 2 (mostly in ViewModelBase and BusyAnimation), and two more significant changes:
- InvokeMethod no longer attempts to manage the attached UI control’s IsEnabled property; this is a breaking change, but was necessary to avoid an otherwise unavoidable memory leak. It wasn’t a good practice anyway, so this implementation is both safer and better.
- There’s a new Csla.Web.Mvc.CslaModelBinder class; it addresses a key issue around the data annotation validation attributes and how their validation information is reported back to the ASP.NET MVC framework. (I know I said Beta 1 was feature-complete, but this was too important to hold back…)
I’ve also continued to update samples, and I think all the C# samples are now updated, as are some of the VB ones. Hopefully I can get the rest of the VB ones updated before final release.
I am still on track to release 3.8.0 in about a week – hopefully Nov 6 or 9.
mbblum replied on Sunday, November 01, 2009
The cslacs project build failed because of a reference to System.Web.MVC. Probably needed for the second bullet about CSLA.Web.Mvc?
Searching MS, it looks like this is the page install link: http://www.microsoft.com/web/gallery/install.aspx?appsxml=&appid=MVC . Is that the correct Install? (FYI to others, it has to install Web Platform Installer before offering to install ASP.NET MVC 1.0.)
If required going forward, reminder to add to ReadMe.
Thanks, mbbmbblum replied on Sunday, November 01, 2009
I went ahead and installed, and both cslacs and cslalightcs projects now build.RockfordLhotka replied on Sunday, November 01, 2009
I'd forgotten that MVC was an extra install... I've added the note to the readme. Fortunately MVC is part of .NET 4.0, so this issue is short-lived.bdbrodie replied on Monday, November 02, 2009
Hi Rocky,
Great work on implementing MVVM!
Looking forward to the release.
Regards,
Ben
RockfordLhotka replied on Monday, November 02, 2009
dmnc replied on Thursday, November 05, 2009
I have played around a bit with the new MVVM stuff and implemented a view model by inheriting from ViewModel. However the dependency properties declared in ViewModelBase are not accessible from XAML:
<local:MyViewModel x:Key="..." Model="..." />
MyViewModel does not contain a property with the name Model.
I wanted to take a peek at the MVVMexperimentWpf sample, but if I open up the DetailPage.xaml or ListPage.xaml then Visual Studio silently crashes right away.
Any ideas what's wrong?
RockfordLhotka replied on Thursday, November 05, 2009
You use the designer? Really? You poor person…
The first thing I do when I install VS is switch the default
editor for .xaml files to the code editor. The visual “designer” is so slow and
crash-prone I can’t see how anyone could live with it.
Now in VS 2010 the designer is much nicer – it is actually
useful – so I have not turned that one off.
dmnc replied on Thursday, November 05, 2009
Actually I'm only using the full XAML view. I've tried on another machine and it doesn't crash.
My main problem still exists. In a fresh C# project everthing works whereas in a fresh VB project the ViewModelBase properties like the Model property refuse to show up in XAML?RockfordLhotka replied on Thursday, November 05, 2009
If you only use the full XAML view you _really_ should switch the default to
the text editor. You still get all the intellisense and coloring, but at
twice the performance...RockfordLhotka replied on Thursday, November 05, 2009
dmnc: In a fresh C# project everthing works whereas in a fresh VB project the ViewModelBase properties like the Model property refuse to show up in XAML?
I have no idea what is happening here.
I can replicate your problem - the Model property shows up in code, but not in XAML in a VB project.
In VS2010 VB works as expected, so this surely sounds like a VB bug in VB 9 or the VB XAML design experience or something.
dmnc replied on Thursday, November 05, 2009
Thanks for the editor tip and for confirming the issue. Good to know that it works in VS 2010.Copyright (c) Marimer LLC