[Mono-dev] Linq to Sql Start

Marek Safar marek.safar at seznam.cz
Thu Sep 20 06:06:36 EDT 2007

Hi Kevin,
> Hey! I've started to get going on some of the System.Data.Linq work,
> at the moment, there's not much in terms of real code to show, but
> some initial unit tests (my first ever, sorry they're so incomplete)
> and API updates (Get the public API more in sync with the current 3.5
> Beta 2) and realistic implementation for some of the extension
> methods, static methods, and helper style classes. I hope to delve
> into Table and DataContext later this week (the real toughies) but
> once I 'got' the whole deferred execution thing, this whole system
> started to make a lot more sense. (Hence my writing the CompiledQuery
> class ;) ).
I am happy to hear that you have made good progress.
> Anyways, there's too much file movement to do a sane patch, and since
> some of the new files aren't properly integrated into the build
> system, I don't want to submit a patch, however, as I clean up the
> code and make more progress, I'll release a branch later today, once I
> finish cloning SVN for a local repo.
Is it really necessary to clone our SVN?
> Anyways, I figured I should drop in some sort of status update, at the
> moment, the biggest hurdle for me is getting build systems to play
> nice, conceptually, it seems easy enough, just add a makefile event
> which outputs the VS projects and solutions. The other thing is I'm
> currently using Resharper to run the Nunit tests, and that needs to be
> added to the makefiles.
This should not be hard, MWF guys have some script if you want to
automate (.sources -> .csproj) conversion.
> Before I get in too deep, whats the policy with ChangeLogs? I'm
> assuming some sort of comment/description of changes is required,
> however, everyone has their specifics, and I didn't see anything in
> the wiki. Moreover, should I be submitting individual patches for each
> increment I complete? (for example when I finish integrating my tests
> into the build, should I submit that patch or wait until my work is
> 'done'. Seeing as the namespace I'm working on isn't really at risk of
> 'breaking' I would guess that reasonable benchmarks are ok, I'm open
> to whatever. Once I have a public branch of my work up, I'll just
> reference that.
The preferred way is to submit more small patches split by something 
common which
you can describe in ChangeLog. There is not much activity in olive now, but
maintaining your changes in the local repository for long time is not 
good. Anyone can
commit changes which you have already made.


More information about the Mono-devel-list mailing list