Obviously we have:
Csla, Csla.Validation, Csla.Core, etc. --> from Csla.dll
Initially the extension project to Csla was named: CompanyName.Csla.
So, there is CompanyName.Csla, CompanyName.Csla.Validation, etc.
This causes an issue when Csla.dll and CompanyName.Csla.dll are included. Intellisense becomes really messed up. Anything beginning with Csla (including references to Csla.Core, Csla.Validation, etc) fail because it's looking for them in the CompanyName.Csla... namespace.
One alternative to this is to alias the namespace - such as using CSLA = Csla, and then using CSLA whenever using Csla.dll classes - which I am not entirely fond of. What is the best practice for this? Is it just being careful with the naming of the extension project and naming it something like CompanyName.Framework or is the best solution something else?
Thanks!
I use the ObjectListView from CSALContrib and Brian simply used the same namespace: Csla.
I was running 1.x and 2.x in parallel for a while so it did not matter.
But I just converted completely to 2.x and removed all references to Csla. I use Csla2 for my namespace. So I had to change Brian's namespace to Csla2 and all is well.
Joe
Copyright (c) Marimer LLC