I'm hoping that I'll be able to use my old 3.0.5 objects with the new Csla.Wpf components. Will these objects inevitably need to be brought up to Csla 3.5 before Wpf can implement them?
I tried a test app and ran into the following error:
Could not load file or assembly 'Csla, Version=3.0.5.0, Culture=neutral, PublicKeyToken=93be5fdc093e4c30' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) Error at object 'ReferralSubmission' in markup file 'WpfTest;component/wpftestwindow.xaml' Line 8 Position 25.
.NET can only load one instance of an assembly into memory at a time. So you can't load two different versions of x.dll into the same application at the same time. This is true for all assemblies, including Csla.dll.
If you want to use two different versions of Csla.dll in the same program, you'll need to rename one of them to be Csla-other.dll (or something) and change its root namespace to something else (not Csla) to avoid naming collisions.
You are probably better off bringing your code up to the latest version of CSLA .NET.
Btw, the really cool WPF controls are in 3.6, not 3.5 (PropertyStatus, ObjectStatus, etc).
Thanks Rcoky,
sorry for the 3.6 newb question. We're only considering implementing Wpf right now and I haven't even started reading the newer Csla book yet. Thanks again for the help, very useful.
WPF is a lot more fun in 3.6 with the new controls –
especially PropertyStatus, but also with the new per-type authorization and
related support in ObjectStatus.
Rocky
From: decius
[mailto:cslanet@lhotka.net]
Sent: Monday, December 08, 2008 12:08 PM
To: rocky@lhotka.net
Subject: Re: [CSLA .NET] Csla 3.0.5 objects with wpf
Thanks Rcoky,
sorry for the 3.6 newb question. We're only considering implementing
Wpf right now and I haven't even started reading the newer Csla book yet.
Thanks again for the help, very useful.
Copyright (c) Marimer LLC