Hi, > -----Mensaje original----- > De: [email protected] [mailto:mono-vb- > [email protected]] En nombre de Quandary > Enviado el: martes, 01 de junio de 2010 22:52 > Para: [email protected] > Asunto: [mono-vb] Contributing Microsoft Sync Framework > > Hi, question: > > I'd like to implement the Microsoft.Synchronization.Files Namespace and > subnamespace in managed code for mono/Linux. > (http://www.microsoft.com/downloads/details.aspx?FamilyID=89adbb1e- > 53ff-41b5-ba17-8e43a2e66254&displaylang=en) > > As of June 7th, 2010, I'll be in the Swiss Army for the (compulsory) 3 > weeks repetition course bs each year. > So if I mangage to slip away unnoticed for most of the time, as I > mostly do, I'll have 3 weeks time to implement it. > > Probably, quite a part of the Sync framework would follow in the > process. > > So... I read the (thy shall not reverse-engineer part of the) > contribute page, but I have some questions: > > 0. I assume I don't have to change "Microsoft" in > Microsoft.Synchronization to something else because of trademark issues ?
No, don't change it. It would make your code incompatible with MS' code. > 1. Shall I implement it in VB.NET or in C# ? Does it matter ? Whatever you're more comfortable with (though have in mind that our VB compiler only supports VB8, while the C# compiler supports the most recent C# features). > 2. Once completed, where do I upload it? (svn? write access? Submit to someone?) My advice would be to use a free/public hosting service (such as github.com). Once done, you can send the information to our mailing lists for review, comments, etc. > 3. Since I'll implement first what I need, what do I do with methods > that I do declare already, but that are not yet implement ? Throw an > exception ? You can either not write the method declaration at all, or throw NotImplementedExceptions. Generally the former is preferred, though the latter might be used if it won't compile otherwise. > 4. What license has it to be under ? Basically, can I choose BSD/LGPL ? MIT/X11 is preferred, though it's really your choice (we do have LGPL code too). > 5. Is there a quick way to extract properties/types/inherits/overloaded > functions/procedures info ? No, unfortunately not. We generally use MSDN. > 6. I assume I'll have to write a makefile, not supply a project, right ? A compilable project file (either MonoDevelop or VS) is perfectly fine. > Unit test, too ? Yes please :) You should actually write unit tests *first*, then write code. Have in mind that if you don't have unit tests, nobody will dare touch your code since they'd have a hard time knowing if they regressed something. Rolf > > > Kind regards > _______________________________________________ > Mono-vb mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/mono-vb _______________________________________________ Mono-vb mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-vb
