I'm working on version 2.1.4 of the framework. Well, to be fair, xal has done most of the work thus far ![Smile [:)]](/emoticons/emotion-1.gif)
But I've put a test version on the download page.
The focus, at the moment, is on CslaDataSource. Andres has tracked down a new approach to getting the type information in the designer, and it appears to be much better than the previous scheme. It now provides support for VS 2005 SP1 with web projects, and also allows the use of business classes from the App_Code directory or the web project, which is nice for demos anyway.
I also have a lead on getting the control working when added as a new data source from a grid or details control. That's not in the test build yet, but I"m hopeful that a solution is close.
So if you have the time and interest, please download 2.1.4 and give the new CslaDataSource a go. Post here with any issues you run into.
I have made a newer test version of 2.1.4 (C# only) available for download at www.lhotka.net/cslanet/download.aspx. If you have the time, please download this and try it in your web development - let me know if you encounter any issues.
This test version includes my attempt to allow the control to be added through the "new data source" option from within the GridView and DetailsView controls. This does not work properly, but at least it is more stable than the 2.1.3 code. The issue I'm now facing with this is that Visual Studio is somehow loading the new control into a separate appdomain from the actual page designer, which is causing the failure. A solution is not available at this time, and other people (such as the author of LLBLgen) have likewise been unable to resolve the issue... I am beginning to think it may not be worth my time to continue trying to solve it.
This test version also includes a configuration window for CslaDataSource. You can now click the control's Configure link to more easily specify the type name of your business class. Along with this change, the AssemblyTypeName property is no longer used. I am leaving it on the control to avoid breaking existing ASPX pages, but it is now totally ignored by the control.
I think it's gonna woik.
I have not dared install SP1 again, having previously installed - uninstalled - reinstalled and finally uninstalled, but in the short time that I have been using 2.1.4, some of the inevitable and frequent "assembly not found" errors, which had almost become as expected as the snow in Minnesota in February, appear to have disappeared. Fantastic.
Thanks Rocky, and thanks Andres
Jav
I did notice one problem. I have been using Petar's ActiveObjects. Now, I am getting an error complaining about the OnSerialized, OnDeserialized methods in some of the ActiveObjects whenever the code is getting an object. Since I don't use any of those methods, it was simple enough to just comment those out - which took care of the problem.
Jav
Is this at runtime or design time?
None of the runtime behaviors have changed – all the
changes are in the design time behaviors of the control.
Rocky
From: Jav
[mailto:cslanet@lhotka.net]
Sent: Thursday, February 15, 2007 9:55 PM
To: rocky@lhotka.net
Subject: Re: [CSLA .NET] CSLA .NET 2.1.4 available for testing
I did notice one problem. I have been using Petar's
ActiveObjects. Now, I am getting an error complaining about the
OnSerialized, OnDeserialized methods in some of the ActiveObjects whenever the
code is getting an object. Since I don't use any of those methods, it was
simple enough to just comment those out - which took care of the problem.
Jav
I've now put a VB version of 2.1.4 online too - equivalent to the C# version, so it includes the configuration dialog, along with the other changes.
My Microsoft contact has indicated that the issue I've been fighting with adding a new data source control from a grid or details control is almost certainly a bug in Visual Studio. The author of LLBLgen has run into the same issue, and he chose to just live with it. I guess I will too - at least until VS gets fixed.
Rocky,
The problem with Petar's code occured at runtime. Unfortunately I did not write down the error message - which appeared to be quite consistant. I will be out of town till Monday, but I can do the test again then. I am using the latest version that Petar has made available on his site.
Jav
Copyright (c) Marimer LLC