> started a solution structure following the examples from ".NET
> appears that in order to get good
> "package" structures in C# you need separate projects per solution.
I'm not aware of any such requirement. (I will review your reference
when I get time, tho.) C# has the notion of namespaces, which map
roughly to packages in Java. A noteworthy difference is that unlike
Java packages that enforce a certain directory structure, there is no
such requirement in C#, e.g.:
file IValidator.cs
namespace Jasig.CasClient.Validation
{
public interface IValidator() {...}
}
file IPrincipal.cs
namespace Jasig.CasClient.Authentication
{
public interface IPrincipal() {...}
}
Both of the above files could live in a flat project layout, or could
be organized in subfolders of the project root.
Another problem with multiple projects is that each will create a
separate .NET assembly (DLL), which I believe would unnecessarily
complicate deployment. Decisions about project layout should be
driven more by packaging and deployment considerations than source
code organization.
Two recommendations follow from this:
1. Use brief namespace names.
2. I can see at most three projects in the solution, one for a core
library, possibly another for IIS integration, and possibly a third
for integration testing.
M
--
You are currently subscribed to cas-dev@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
