[Mono-list] [Mono-hackers-list] Connection-less tests in System.Data
I will answer my own question. The various connection-less tests in System.Data use nunit prior to 2.0. The various provider connection-oriented tests do not use nunit, but have names like SqlTest.cs for SqlClient, PostgresTest.cs for PostgreSqlClient, MySqlTest.cs for for MySql, TestDB2Conn.cs for DB2Client, etc... I still need to make these tests get the connection parameters from the command-line or use a config file. The Tests for assembly System.Data are found at mcs/class/System.Data/Test The connection-less tests can be run in mcs/class/System.Data/Test on Windows: ../../nant/NAnt.exe test I assume on Linux, this would be: make -f makefile.gnu test If you want to add various tests to a test that already exists, such as, add a test called public void TestThisThing() to DataColumnTest, just add the method to the file. NUnit will automatically call this test. However, I would still like to know how to compile and run the tests with .NET. This way, I know the tests for Mono are correct. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Morgan Sent: Sunday, January 26, 2003 12:15 AM To: Ville; Nick D; Mono Hackers mailing list Subject: [Mono-hackers-list] Connection-less tests in System.Data Hello NickD and Ville, I have no idea what the status of the connection-less tests that use NUnit in System.Data. I haven't tried running them. However, just by looking at the tests seems like they don't work. I could be wrong. Should we be trying to use NUnit 2.0 now, or is the old NUnit fine? Ville, Do the NUnit tests in System.Data work for you? How do you get them to work on .NET and then later get them to work on Mono? This is very important because my tests for Mono are based on how they work for .NET. My tests now just need to be converted to NUnit. I have some tests for the DataRow class which affects other classes too, such as, DataTable, DataRowCollection, DataColumnCollection, and DataColumn. Any comments are welcomed. Thanks, Daniel ___ Mono-hackers-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-hackers-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Mac OS X build error...
On 01/26/03 Jonathan LaCour wrote: Just getting ready to start working for a company that heavily uses .NET, and I am interested in starting learning with mono. I have a Mac OS X 10.2.3 powerbook and I tried compiling and installing mono as follows. First, I compiled and installed the mono-0.19.tar.gz package, and it worked without a hitch. However, when I attempt to compile mcs, I get a problem, as below: mint can't bootstrap mcs on MacOSX yet, help in debugging the issue is welcome. lupus -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] compiling mono
On 01/25/03 Alexander Chan wrote: I compiled mono on my ibook running gentoo linux on it. I had one problem though. i ran make and make install. It seems that mint and mcs was compiled but not mono. really odd.. what should i do? mono (the JIT compiler) has not been ported yet on ppc: we're working on it. lupus -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
RE: [Mono-list] interpreter/interp.c
Got it. Thanks. If you're using mono from cvs, make sure you run ./configure with the --enable-maintainer-mode option, this will take care or rebuilding the correct makefiles after changes to Makefile.am file. You can just run configure again to fix the compilation on your system. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] problems with Directory::GetParent()
Hi, It seems that System.IO.Directory::GetParent() is broken, ie. GetParent (/a/b) returns a/b The fix is to replace: return new DirectoryInfo (Path.GetDirectoryName (path + Path.DirectorySeparatorChar + ..)); with: return new DirectoryInfo (Path.GetDirectoryName (path)) Interestingly, that was the original definition of this method, but a later checkin changed it to the current incorrect version. Why was that done? Can I check this stuff in ? bye Zoltan ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Some ideas for dotgnu.
Hello, -gtk Link against the Gtk# libraries -gnome Link against the Gnome# libraries These switches don't really belong in the compiler. The compiler is potentially for use in any environment (Win32, MacOS X) so favouritism doesn't make sense. There are very few cases deserving of special attention by the compiler. All of those cases are when the compiler may know better than any build system or user e.g. gcc -pthread. Yes, but we might disagree on what `-gtk' and `-gnome' link to. Should that by default reference and import Atk? Glib? Glade? Bonobo? Gnome-Print? Which parts of the platform? Miguel ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Newbie question
On Sun, 2003-01-26 at 00:18, [EMAIL PROTECTED] wrote: I think that WinZip isn't problematic with CRLF. I am not trying to be belligerent, but have you ever run WinZip on a tar file created on a Unix box and seen it change all CRs on text files to CRLFs? I have, and I think I am running the latest version (8.1 build 4132, if anybody cares). A de/compression application must be deterministic, it only runs an algorithm and doesn't look inside the content of any file. Tell that to WinZip. It uses some heuristic to determine what is a text file and what is a binary, and it works differently on text files. This can be changed in the configuration dialog box, but it is on by default. Thanks for trying to help, Pedro. You are correct, Cygwin and WinZIP should be set up correctly to work with Unix files. But I think we are veering off-topic regarding this. I was only trying to help Jeroen, in case he was using a tool that I know for a fact causes problems with Unix tarballs on Windows. -- PJ Cabrera pjcabrera at pobox dot com ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
