[Mono-dev] Linq to Sql Start

[Kevin Kubasik]

/me eyes get big

Wow, my complete apologies, I didn't realize the patch was so
inflated, its probably mostly line endings, I'll try and slim it down,
although if anyone has had some prior experience with a good
tool/practice, I'm all ears.


As far as changing what is necessary, there was a lot of shifting
around with in the System.Data.Linq department, this blog post[1]
makes a haphazard effort to summarize them. I wasn't super
conservative when the class was empty or all notimplemented
exceptions. And I could always be corrected, I'm getting my public
API's from the Visual Studio Class Browser, and then random scouring
of the net for solid examples of use etc. as MSDN isn't as fleshed out
for the 3.5 classes.  However, I don't this I was ever excessive, a
lot of the time it


I'm sorry, I should have been more clean when I said VS wrappers, I
didn't mean Visual Studio Test Cases or anything, its all written in
Nunit, I just have a DataSet and DataContext that were generated using
the VisualStudio tools. As for the Database, its just for the big
sloppy overarching tests that I started with, they aren't necessary
now, I can remove them, once I clean up the EOL issues so I'm not just
compounding the problem.



[1] -http://oakleafblog.blogspot.com/2007/07/linq-changes-from-orcas-beta-1-to-vs.html

On 9/20/07, Marek Safar <marek.safar at seznam.cz> wrote:
> Hello,
> > Hey, my last e-mail got bounced for size, so if you really want the
> > zip, or the patch, everything is at
> > http://kubasik.net/files/olive_patches/
> >
> I am sorry but I am not going to review 2.2 MB patch file.
>
> My recommendations are:
> - Don't change what is not necessary
> - I see there is some problem with line ending, I can have a look at
> this if you find it difficult.
> - Please don't use VS unit test wrappers, or convince me why it's necessary
> - Your unit tests should not rely on DB.
>
> Thanks
> Marek
>
>


-- 
Cheers,
Kevin Kubasik
http://kubasik.net/blog