Do you want to place it under the current code? If you want it purely in
sandbox, I'd recommend the /sandbox
-Scott
On Mon, Mar 9, 2009 at 5:53 PM, William G. Thompson, Jr.
<wgt...@gmail.com>wrote:
> hmm...does it make svn sense to create a new folder
> cas-clients/dotnet-client/sandbox?
>
> Bill
>
>
> On Mon, Mar 9, 2009 at 4:31 PM, Scott Battaglia
> <scott.battag...@gmail.com> wrote:
> > Any suggestions for the directory name (it has to go under
> cas-clients/). I
> > think we already have a dotnet one.
> >
> > -Scott
> >
> >
> > On Mon, Mar 9, 2009 at 2:34 PM, William G. Thompson, Jr. <
> wgt...@gmail.com>
> > wrote:
> >>
> >> On Mon, Mar 9, 2009 at 10:47 AM, Marvin Addison
> >> <marvin.addi...@gmail.com> wrote:
> >> >> 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.:
> >>
> >> True, but the way accessibility modifiers work if you want to
> >> encapsulate "package" level functionality you need them to be in
> >> different assemblies (internal modifier). Accessibility and
> >> namespace are totally independent within an assembly, right?
> >>
> >> If we were going to map java package visibility design to the port,
> >> we'd need separate assemblies. Perhaps the package/assembly
> >> visibility doesn't matter that much since the code base is relatively
> >> small. Facilitating developer understanding of the code base via
> >> logical organization is as important to me as easy deployment. Maybe
> >> this is achieved by mapping Java packages to C# namespaces in the same
> >> assembly arranged via folders.
> >>
> >> Keeping alignment with the Java package structure (at least for
> >> namespace) should aid in the port, and help with on going maintenance
> >> and for those brave souls jumping from one to the other.
> >>
> >> Bill
> >>
> >> >
> >> > 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:
> >> > wgt...@gmail.com
> >> > To unsubscribe, change settings or access archives, see
> >> > http://www.ja-sig.org/wiki/display/JSG/cas-dev
> >> >
> >>
> >> --
> >> You are currently subscribed to cas-dev@lists.jasig.org as:
> >> scott.battag...@gmail.com
> >> To unsubscribe, change settings or access archives, see
> >> http://www.ja-sig.org/wiki/display/JSG/cas-dev
> >
> > --
> > You are currently subscribed to cas-dev@lists.jasig.org as:
> wgt...@gmail.com
> > To unsubscribe, change settings or access archives, see
> > http://www.ja-sig.org/wiki/display/JSG/cas-dev
>
> --
> You are currently subscribed to cas-dev@lists.jasig.org as:
> scott.battag...@gmail.com
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-dev
>
--
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
