Wednesday, October 18, 2006
Re: SpCore
Today we started refactoring our core business library for .Net aka SpCore. Remember SpCore is our equivalent of MsCorLib? We are targeting a .Net coding thats a few crazy lines of codes; better/worse than Python :).
Well we did achieve some: Yanked out the Enumeration classes that no one has been using, created an Imaging namespace and dropped the imaging and scanning classes under sub namespaces of this. We did create a Text namespace too. Sweet that unit test library we just added.
Tunde created a 2.0 version of SpCore. Only the solution file carries a different name i.e. Spcore2.0. The assemblies share names with the 1.1 version. versioning will be controlled with version numbers in the assemblyinfo.cs file and the .Net 2.0 branch will carry 2.x.x versiuoning while we continue developing the 1.1 branch simultaneosly.
Todos
Team reconvenes next week Wednesday to submit status. Codes should have been committed to source control before then.
Well we did achieve some: Yanked out the Enumeration classes that no one has been using, created an Imaging namespace and dropped the imaging and scanning classes under sub namespaces of this. We did create a Text namespace too. Sweet that unit test library we just added.
Tunde created a 2.0 version of SpCore. Only the solution file carries a different name i.e. Spcore2.0. The assemblies share names with the 1.1 version. versioning will be controlled with version numbers in the assemblyinfo.cs file and the .Net 2.0 branch will carry 2.x.x versiuoning while we continue developing the 1.1 branch simultaneosly.
Todos
- Sese includes a validation library into SpCore solution.
- Stan includes an encryption library
- Unit tests for lib functions, assigned to Keni, Gbenga, akin
- SpCore2.0 for .Net 2.0; solution created by Tunde.
Team reconvenes next week Wednesday to submit status. Codes should have been committed to source control before then.
# posted by Unknown @ 3:24 AM 
