Project files organising

[Raschmann]

As it becomes harder for orientation between project files seems its time to group files into folders. Sugested folder are;

Exceptions Extensions Metadata Command Binding Message Helpers

[albinsunnanbo]

I think it is a good idea. The Tests project is also a good candidate. The other projects are still small enough. I propose that you update namespaces in the files to reflect folder location.

File moves on this scale are however a recipe for merge hell. We need to schedule such reorganization carefully to not collide with other major ongoing work.

[AndersAbel]

I agree that it's a good idea. Building upon the suggestion I outlined in #94 (which I have now closed as a duplicate to this one) and Jozef's suggestion above I suggest the following namespaces under Kentor.AuthServices:

• SAML2P: The classes for the messages in the SAML2P protocol.
• Metadata: The metadata classes, including the serializier.
• WebSSO: The command, commandresult and binding classes. These are specific to the WebSSO SAML2 profile.
• HttpModule: The SAML2AuthenticationModule is moved to an own namespace, in an own assembly. Would allow the core Kentor.AuthServices library to no longer reference system.web.
• Helpers: Other internal classes that are not part of the public API. No public classes allowed here.

Getting the namespaces/folders cleaned up is an important step towards a stable 1.0.0 release. After that we can't move things around any more without breaking compatibility (and moving to 2.0.0).

[AndersAbel]

Discussed with @Raschmann and @albinsunnanbo. Some suggestions from that conversation:

• Add a Security.Cryptography namespace for signature handling and helpers (if they are public).
• Put the exceptions in a separate namespace.

[AndersAbel]

I've now pushed an implementation of this to https://github.com/AndersAbel/authservices/tree/142Namespaces, but I'm waiting with the merge until some planned pull requests are merged.