In theory there is no issue to have two references to your
libraries, where each one references Csla. The issue is though that those
two libariries will reference different versions of Csla. I do not think
you would want to do this. So, if you are staying on 3.0, then you are
OK. Otherwise I would recommend upgrading your first project to 3.5.
Sergey Barskiy
Principal Consultant
office: 678.405.0687 |
mobile: 404.388.1899
Microsoft Worldwide Partner of the Year | Custom
Development Solutions, Technical Innovation
From: reagan123
[mailto:cslanet@lhotka.net]
Sent: Monday, October 06, 2008 3:38 PM
To: Sergey Barskiy
Subject: [CSLA .NET] One Project... Reference 2 Library Projects?
Currently I have a Windows application that is using a
library of business objects using CSLA 3.0.4.
We are about to start a new project in WPF that will have it's own library of
business objects as well, but it will need access to some of the objects from
the other project.
What is the best approach to this?
Is there an issue with having one project reference 2 CSLA libraries or should
I just add a seperate namespace to the existing library project?
Any guidance greatly appreciated!
Not really. I think you only need one principal object for
two libraries.
Sergey Barskiy
Principal Consultant
office: 678.405.0687 |
mobile: 404.388.1899
Microsoft Worldwide Partner of the Year | Custom
Development Solutions, Technical Innovation
From: reagan123
[mailto:cslanet@lhotka.net]
Sent: Monday, October 06, 2008 5:13 PM
To: Sergey Barskiy
Subject: Re: [CSLA .NET] RE: One Project... Reference 2 Library
Projects?
Thanks for the reply... My other concern has to so with
which library would be in charge of Identity/Principal.
Would I have to call the login on each library so that my authorization
rules work or what?
Thanks for the insight so far :)
Copyright (c) Marimer LLC