I'm not the kind of guy that rides the newest techonology wave just because it's the newest. I prefer to step on solid ground. Interestingly enough, many of my coworkers (almost all in fact) think the opposite: "You are always looking for new stuff. Why should we change the way we do things? Just because this is a new way? If tomorrow there is an even newer way to do things, we should redo everything once over and over? No way! Show me something that is working."
"If Silverlight is the future. Let's give it a try. Then I can show them something that is working and convince them to change" I said to myself.
So using CSLA.NET and Silverlight was the goal. I never used Silverlight before. My projects are all WinForms mostly because of the superior user experience. And faster design time. And easier debugging. And... you name it.
I checked out svn://svn.lhotka.net/csla/core/trunk/Samples/CslaLight and tried build some samples. I gave up after the first 2 or 3 samples. All had build problems: missing references, stuff that moved to other namespaces, etc. I was never sure if I was using the right DLL or the wrong Silverlight version or ...
The samples should build on Silverlight 3. There is a Silverlight 3 SDk and a Silverlight 3 toolkit. But some samples use stuff that is on the Silverlight 2 toolkit. Confusing enough. Should I also use the Silverlight 2 SDK? Or do I need some stuff from Silverlight 1 SDK?
I found out that this is a common problem with Silverlight. It's not stable and developers aren't available to port applications to the latest Silverlight version, not until Microsoft stabilizes the project and makes it "a technology".
There are 15 C# samples. Please tell me if you know of some samples that only need updated Silverlight 3 stuff:
Your problem is that you grabbed /core/trunk - which is the rapidly changing 4.0 version of CSLA .NET that targets SL4 (or will when we're done).
If you want something reasonably stable, and that targets SL3, get the 3.8.2 samples or pull from the 3.8.x branch in svn.
I fectched the suggested sources, give them a try and report back.
Copyright (c) Marimer LLC