and using CSLA 3.0.x or 3.5.
After moving a couple of projects from VS2005 to VS2008, I learned that so much of the C# 3.0 features are just "syntax sugar" that the C# 3.0/3.5 compiler will compile into valid IL code - even when your projects target is the .NET 2.0 Framework.
So move your .NET 2.0 projects to VS2008 - and you can use a lot of the new C# syntax such as:
In projects that target .NET 2.0!!! For the first 6 bullets please see these posts:
http://www.danielmoth.com/Blog/2007/05/using-c-30-from-net-20.html
http://www.danielmoth.com/Blog/2007/05/using-extension-methods-in-fx-20.html
and for LINQ to Objects se this one (open source and free use)
http://www.albahari.com/nutshell/linqbridge.html
So what I would like to see is CSLA 3.5 (for VS2008) and targeting .NET 2.0, 3.0, 3.5 thereby giving developers the possibility to use the same snippets and templates for all targets (and the new property declaration in CSLA 3.5). I am NOT proposing to make CSLA 3.5 compile in VS2005 - rather have "CSLA 3.5 for VS2008" and support all .NET version targets in VS2008.
I did modify CSLA 3.5 to compile for .NET 2.0 in VS2008 and it is not much work (< 1 hr) and basically what you need to do is:
That way we would have access to all the new property declarations and have a much easier upgrade path to newer version of the .Net framework.
Hopefully we might have CSLA 3.5 compiled for .NET 2.0 and .NET 3.5 - and have VS2008 pick the right version based on the projects target.
What is your idea on this folks?
/jonny
There were also several incompatibilities between .NET 2.0 and 3.0 that were solved with compiler directives in CSLA .NET 3.0. I would expect those same issues to exist in 3.5, though I removed the related compiler directives because I did not plan for CSLA 3.5 to support .NET 2.0 or 3.0.
I am open to the idea, but don't have time to pursue and test the changes in C# and VB and the two ProjectTracker implementations.
If you are willing to make the changes and test them in all four code bases (CSLA/ProjectTracker in C#/VB), I can send you the CSLA .NET contributor agreement for you to sign.
I should qualify that though - in that I'll only proceed with this if there is fairly broad support for the idea across the community. Obviously this would radically broaden my support/testing surface area, which is not good for me or the community.
Also, nothing can be allowed to interfere with Expert 2008 Business Objects or the CSLA Light/CSLA .NET 3.6 project. I'm presupposing that the changes you suggest are truly minor and would not impact those efforts.
They wouldn't affect the book, because it is being written against 3.5.x - and this would certainly be rolled into 3.6.
But it could impact CSLA Light, which is part of the reason for there being a 3.6. The other motivations for 3.6 being:
In short, I'm in the middle of several big initiatives that involve more than just me. The scheduling isn't terribly flexible, and anything that would alter the scope or introduce risk can't be allowed.
However, if there is broad community support for .NET 2.0/3.0 support, and someone willing to do the dev and testing work in all four code bases, and there's a high level of confidence that it won't negatively impact 3.6, then I'll consider it.
> But based on the response here it does not seem to
be much
> support/requirements for having CSLA 3.5 available in
>VS2008 projects that target .Net 2.0.
I don’t know – give it time and let’s see
if other people chime in with comments.
Rocky
I plan to move to VS 2008, CSLA 3.5 and .Net 3.5 at the same time.
So I would not be interested in this.
Joe
Hi Rocky,
just saw your email and i am a little confused, you list the following items in 3.6
Actually number 1 and number 4 ... are high on my list!, can you confirm the new book is going to cover these? ... From what i understand these features are for 3.6 .... but is the book being targeted at 3.5?? ....
MVC and entity framework is something i have been looking forward to integrate with CSLA ... i really didn't want to start downloading patches almost immediatly i.e. PRINT BOOK 2008 and then a pdf to learn the mvc and entity bits..
Any info you can offer on this would be really helpful and hopefully putting my mind a rest :-)
Thanks
Ian
The Expert 2008 Business Objects book will target CSLA .NET 3.6 - which is really 3.5 with server-side support for CSLA Light clients and some minor changes for .NET 3.5 SP1.
At the moment my plan for ADO.NET EF support primarily centers around creating an EF version of Csla.Data.ConnectionManager. I may do more, but EF is quite controversial and I'm not interested in putting a lot of work into supporting it until there's broader enthusiasm in the market for it.
It is important to realize that CSLA works with ASP.NET MVC now, today. There's absolutely nothing I have to do to make them play together - they work together very nicely! However, it may be that I can create some helper methods/controls/tools around View creation. If I get time I'll reseach that sort of thing, but it isn't a real high priority, because the status quo is not bad at all.
The new book will not cover ASP.NET MVC. That will likely be an ebook following the Apress book. My current plan is to have three interface chapters: WPF, Web Forms and WCF services.
It is most likely the case that the data access in the book will use LINQ to SQL, though I may switch to EF - though what I'd like to do is show both (space and time permitting).
Thanks rocky for the confirmation...
Best regards
Copyright (c) Marimer LLC