Re: [Mono-dev] [Mono-list] error on viewstate
On Thu, 20 Sep 2007 09:32:13 +0200, Hubert FONGARNAND [EMAIL PROTECTED] scribbled: Hello, as i said before... DropDownList are broken on mono 1.2.5 Maybe there will be a backport in mono 1.2.5.1 The backport is indeed in 1.2.5.1 regards, marek signature.asc Description: PGP signature ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Mono-list] error on viewstate
as i said before... DropDownList are broken on mono 1.2.5 Maybe there will be a backport in mono 1.2.5.1 Le jeudi 20 septembre 2007 à 07:39 +0200, Lorenzo Viola a écrit : Hello, I also get the same error hoping for a fix... which is the right place to post this bug ? best regards Hi All. Sorry for boring :-) I have a problem. In an aspx page, when i click on a button which perform an action, but remains in the same page (for example, in a validation on the server that not pass the test, then appears an message in the validationsummary), and after, click the button a second time, an error occurs //Index is less than 0 or more than or equal to the list count. Parameter name: index 1// Here is the complete stacktrace System.ArgumentOutOfRangeException: Index is less than 0 or more than or equal to the list count. Parameter name: index 1 at System.Collections.ArrayList.get_Item (Int32 index) [0x0] at System.Web.UI.WebControls.ListItemCollection.get_Item (Int32 index) [0x0] at System.Web.UI.WebControls.ListControl.LoadViewState (System.Object savedState) [0x0] at System.Web.UI.Control.LoadViewStateRecursive (System.Object savedState) [0x0] at System.Web.UI.Control.LoadViewStateRecursive (System.Object savedState) [0x0] at System.Web.UI.Control.LoadViewStateRecursive (System.Object savedState) [0x0] at System.Web.UI.Control.LoadViewStateRecursive (System.Object savedState) [0x0] at System.Web.UI.Page.LoadPageViewState () [0x0] at System.Web.UI.Page.InternalProcessRequest () [0x0] at System.Web.UI.Page.ProcessRequest (System.Web.HttpContext context) [0x0] Someone to know about this? How can i to fix this? Thanks. Best regards. ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list ___ Ce message et les �ventuels documents joints peuvent contenir des informations confidentielles. Au cas o� il ne vous serait pas destin�, nous vous remercions de bien vouloir le supprimer et en aviser imm�diatement l'exp�diteur. Toute utilisation de ce message non conforme � sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'�tant pas s�curis�es, l'int�grit� de ce message n'est pas assur�e et la soci�t� �mettrice ne peut �tre tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Mono-list] error on viewstate
No the backport is not complete... as i say here http://lists.ximian.com/pipermail/mono-devel-list/2007-September/024766.html Le jeudi 20 septembre 2007 à 11:48 +0200, Marek Habersack a écrit : On Thu, 20 Sep 2007 09:32:13 +0200, Hubert FONGARNAND [EMAIL PROTECTED] scribbled: Hello, as i said before... DropDownList are broken on mono 1.2.5 Maybe there will be a backport in mono 1.2.5.1 The backport is indeed in 1.2.5.1 regards, marek ___ Ce message et les �ventuels documents joints peuvent contenir des informations confidentielles. Au cas o� il ne vous serait pas destin�, nous vous remercions de bien vouloir le supprimer et en aviser imm�diatement l'exp�diteur. Toute utilisation de ce message non conforme � sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite. Les communications sur internet n'�tant pas s�curis�es, l'int�grit� de ce message n'est pas assur�e et la soci�t� �mettrice ne peut �tre tenue pour responsable de son contenu. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Linq to Sql Start
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. Thanks Marek ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] 'configure: error: ./configure failed for libgc'
Andy Hume wrote: I've been having problems over the past few days getting a build to work and on tuesday night and yesterday morning it was quite broken here. So I cleaned everything up and made sure I'd the most recent SVN updates. Now on doing ./autogen --... as described by shana it fails with: [[ ... ... checking sys/dg_sys_info.h usability... no checking sys/dg_sys_info.h presence... no checking for sys/dg_sys_info.h... no checking for threads package to use... win32 checking whether Solaris gcc optimization fix is necessary... no configure: creating ./config.status config.status: error: cannot find input file: Makefile.in configure: error: ./configure failed for libgc ]] Is there something wrong with my setup? Or something that breaks cygwin building? Any suggestions? I see from looking at monobuild status now that the original build problems I experienced weren't only affecting me so I probably didn't need to clean up, but I'm here now. :-( You probably do need to clean up. Note that monobuild builds are mostly clean that do civilized cleanups and autogen every time. Also note that the build itself is successful at this point (r86057), so it is only affecting you. Atsushi Eno ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Mono-list] error on viewstate
On Thu, 20 Sep 2007 12:15:24 +0200, Hubert FONGARNAND [EMAIL PROTECTED] scribbled: No the backport is not complete... as i say here http://lists.ximian.com/pipermail/mono-devel-list/2007-September/024766.html The patch you mention in that post has been applied to the 1.2.5.1 branch in revision 85745 regards, marek signature.asc Description: PGP signature ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] 'configure: error: ./configure failed for libgc'
Ok I did /more/ tidying up. I first tried deleting the whole mono/libgc folder and svn-updating it. And...fingers crossed...it seems to be working now. Well the autogen.sh step completely successfully and make is running now. Phew! Thanks Andy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Atsushi Eno Sent: 20 September 2007 12:49 To: mono-devel-list@lists.ximian.com Subject: Re: [Mono-dev] 'configure: error: ./configure failed for libgc' Andy Hume wrote: I've been having problems over the past few days getting a build to work and on tuesday night and yesterday morning it was quite broken here. So I cleaned everything up and made sure I'd the most recent SVN updates. Now on doing ./autogen --... as described by shana it fails with: [[ ... ... checking sys/dg_sys_info.h usability... no checking sys/dg_sys_info.h presence... no checking for sys/dg_sys_info.h... no checking for threads package to use... win32 checking whether Solaris gcc optimization fix is necessary... no configure: creating ./config.status config.status: error: cannot find input file: Makefile.in configure: error: ./configure failed for libgc ]] Is there something wrong with my setup? Or something that breaks cygwin building? Any suggestions? I see from looking at monobuild status now that the original build problems I experienced weren't only affecting me so I probably didn't need to clean up, but I'm here now. :-( You probably do need to clean up. Note that monobuild builds are mostly clean that do civilized cleanups and autogen every time. Also note that the build itself is successful at this point (r86057), so it is only affecting you. Atsushi Eno ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] How to use monocharge to bootstrap the build?
On 09/19/07 Philippe Monnet wrote: Over the last couple days, I have been trying to figure out how to use monocharge (now that I was able to build it). monocharge should simply not be used, as the README says. If you have problems in bootstrapping from svn you should build and install first from a released tarball. lupus -- - [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Linq to Sql Start
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/ sorry! On 9/20/07, Kevin Kubasik [EMAIL PROTECTED] wrote: Ok, well in addition to the git way: git clone http://kubasik.net/git/olive-kkubasik.git git branch --track localbranch origin/linq_kubasik git checkout localbranch or the web interface[1], I have included a plethora of patches. The first one (kkubasik-olive) is a simple diff of my working directory against subversion head (or almost, theres the anon delay and my lazness, but it should be pretty close). The zip is a patchset (the way git wants to do them) with a separate patch for every commit I've made to my local repo, probably a pain to actually apply, but good if your confused over an odd diff. And lastly the RevLog (or as its better known git log --pretty --numstat --summary) I'm working on a complete(ish) changelog entry, but its pretty big. (I've been nabbing some low-hanging fruit as I go, null checking, API updates etc.) Anyways, the patches will probably be (somewhat) obsolete later this evening, as I've just been making headway. That doesn't mean ignore them, I need some review of whats going on (things like the DummyDataProvider.cs DiffWrapper.cs and DiffTracker.cs specifically) also any other codeing habits or the like. I've never worked on Classlibs before, and I'm completely open to criticizm, please don't be afraid of hurting my feeling, most of this code is experimental, to see if I've got everything figured out. On a separate note, if anyone is checking the web interface, or the patches, they might notice the TestSuite is currently lots of VisualStudio specific autogenerated code, and a Sql Server 2005 Express Edition database. Being as that toolchain is the only known working implementation (there have been several attempts at MySql backends, I have head mixed things, some were just decompilations of the Sql Provider components with a few syntax changes, and some where from scratch and still buggy.) If there's a frontrunner I'll gladly port the tests, however, until then, (especially seeing as we don't build or run this library by default atm) I would prefer to shelf the overhead associated with making those test's crossplatform. Once we have some form of implementation (even something like 20-30% functional API compatibility, I can get it integrated with makefiles, and using dummy objects for our db backend. All that said, what is the policy for moving this type of code into the repo? Would we just keep the test module separate (maybe as an svn:external ?) or something, or is it ok? Anyways, I hope I'm on the right track here, and actually poised to help, and not just be a constant question sinkhole. I know that a lot of the full-time mono developers telecommute, is there a good time to catch people on the IRC or a Jabber conference room? Anyways, if anyone gets a chance, let me know what possible potential solutions might be with regards to the test suite. Please feel free to examine/peruse/molest the other code as well, however most of that is placeholders etc. until I can flesh out more helper classes/methods. Here is the ChangeLog entry I wrote for this lump of patches, even though its not really a release or anything. 2007-09-20 Kevin Kubasik [EMAIL PROTECTED] * A series of small API Compatability fixes for Beta 2 * A Test Project LinqDataTest (Windows Specifict ATM) * The beginnings of a Linq to Sql Test Suite * DataShape.cs - DataLoadOptions.cs (API Change) * DataContext.cs - Added missing interfaces and method stubs * Write and test GetTable() * Started work on Translate() * Added missing public Properties * DummyDataService.cs * Primarily to extend IDataService.cs for testing * Could potentially become a 'core' implementation * IDataService.cs * Uncommened interface * Organized methods by instance-public and everything else * State.cs * Added a 'ChangeState' enum, as seen in several places on MSDN * Table_T.cs * Added several missing interfaces * Method stubs for corresponding methods * Started work on Add * Implemented Expression handling * DiffTracker.cs DiffWrapper.cs * The backend of Table, will provide access as an IEnumerable * Allows the sane implementation of SubmitChanges() * ChangeSet.cs * Working implementation matching docs on MSDN * EntityRef.cs * BuildFixes when working with Windows * Link_T.cs * Ported existing elements of implementation to updated API * IExecuteResults.cs IFunctionResults
Re: [Mono-dev] Linq to Sql Start
/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 [EMAIL PROTECTED] 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 ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Linq to Sql Start
Hello, 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. It is best to submit small patches as you go that trying to land a huge contribution all at once. Also, it seems that the 2.2 meg file contained a lot of auto-generated code.It might make sense to write our own tool that generates those files instead of checking-in 2.2 megs of generated stuff. Miguel ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] [Gtk#] How to print on win32 and Unix
I use gtk for printing, it works on Linux, but I have not tried it on windows yet. Sample code is below if it can be to any help: http://wordtrainer.googlecode.com/svn/trunk/wordtrainer/Wordtrainer/GtkPrinting.cs David Arnaud-Goddet skrev: Hi all, I develop a GUI in csharp which have to work and windows and Unix. I would like to add in my Gtk.Windows a button to print document. I find, in the mono doc the class : Gtk.PrintUnixDialog I read that : This class implements a Print dialog for platforms which don't provide a native printing dialog What does native printing dialog mean? Which platforms already have a native printing dialog and how can I use it ? Moreover if somebody has a sample code to a print dialog it will be fine! Thanks. -- David ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list -- Markus Kilås +46(0)70 424 94 85 [EMAIL PROTECTED] [EMAIL PROTECTED] www.markuspage.com ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] How to use monocharge to bootstrap the build?
Actually someone else recommended that I use monocharge as I have been unable to build from a stable source release, or a a daily build, or from SVN (trunk or tagged release). I realize my situation is challenging due to a shared hosting scenario and a lack of a local Linux box (don't have access to any box that could run a VM either).I have had to build all new updates of the core GNU tools (except the compiler for now).My shared host is running Fedora core 2.6 with a 2.95.4 gcc.I am only asking for some direction on core settings or procedure not yet explained on the mono web site. I have Googled ad nauseum too and have tried many things for over a week without much success.Help! (did I say I was a Linux newbie too?)On09/19/07PhilippeMonnetwrote:Overthelastcoupledays,Ihavebeentryingtofigureouthowtousemonocharge(nowthatIwasabletobuildit).monochargeshouldsimplynotbeused,astheREADMEsays.Ifyouhaveproblemsinbootstrappingfromsvnyoushouldbuildandinstallfirstfromareleasedtarball.lupus---[EMAIL PROTECTED]debian/rules[EMAIL PROTECTED]Monkeysdoitbetter___Mono-devel-listmailinglistMono-devel-list@lists.ximian.comhttp://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Linq to Sql Start
Hey, I totally get that, I really hadn't meant for there to be sooo much lumped into that patch. I'm going through and breaking the task down into smaller utility classes (some public, some private) and once the framework for them is in place, I can seriously examin the grander scheme. Anyways, this e-mail is 3-fold 1) I have attached a neat and clean and pretty patch that does the following: * Implements QueryCompiler near 100% * Adds ChangeSet to the build, and adds a nearly complete implementation * ChangeLog and Build infrastructure for both of these classes * I filed a bug so the patch wouldn't get lost, its here at: https://bugzilla.novell.com/show_bug.cgi?id=327018 (Yeah, its kinda a dumb bug, but its a random subset of work I guess...) 2) You might notice that I did not include any mention of Unit Tests (implying untested code, a big no-no!) I do have tests, but most of them still revolve around query expressions using the generated NorthWindDataContext, and I am unsure of how exactly to proceed. Miguel had mentioned writing a tool to generate the mappings code (which is on the TODO at some point, but that task is almost impossible to reasonably test before we have working Expression parsing and accurate execution (in terms of time, order, and source). For my own experimentation, discovery and testing, this setup (augmented by the VS debugger) works quite well for determining the behavior of API's. However, there is far too much overhead at the moment to make that part of the official test suite. I know this is probably just my inexperience with not only Nunit, but the Test driven development model in general. Since the whole System.Data.Linq namespace is currently test-less, I don't know if we would hold off on new code until that issue has been taken care of, or we can put it off until theres a more cohesive framework to test, or what. I'll be busy enough collating things and completing full classes instead of just 1 or 2 methods. 3) What exactly is the practice as far as code commenting/documentation. The current patch is bare (my local copy has a smattering of TODO's FIXME's and general blurbs anywhere things get messy, new, or complex. Most of the other libs don't seem to have the inline documentation, just some general comments. There are some smatterings about it in the wiki, but most of the code in SVN isn't like that, so I just thought I would ask. Cheers, Kevin Kubasik On 9/20/07, Miguel de Icaza [EMAIL PROTECTED] wrote: Hello, 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. It is best to submit small patches as you go that trying to land a huge contribution all at once. Also, it seems that the 2.2 meg file contained a lot of auto-generated code.It might make sense to write our own tool that generates those files instead of checking-in 2.2 megs of generated stuff. Miguel -- Cheers, Kevin Kubasik http://kubasik.net/blog compiledquery_changeset.patch Description: Binary data ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] windows build breakage? (missing CreateString)
Recently (I think it's been since middle of this week or so) I have been unsuccessful to build non-bootstrap mono on windows, it complains about missing CreateString. Is it only me or is the build broken? Note that it won't show up as monobuild status as it is non-bootstrap build.) Making all in net_2_0 make[3]: Entering directory `/home/atsushi/svn/mono/data/net_2_0' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/atsushi/svn/mono/data/net_2_0' make[3]: Entering directory `/home/atsushi/svn/mono/data' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/home/atsushi/svn/mono/data' make[2]: Leaving directory `/home/atsushi/svn/mono/data' Making all in runtime make[2]: Entering directory `/home/atsushi/svn/mono/runtime' if test -w ../../mcs; then :; else chmod -R +w ../../mcs; fi cd ../../mcs make PROFILES='default net_2_0 net_2_1' CC='gcc -mno-cygwin -g' all-profiles make[3]: Entering directory `/home/atsushi/svn/mcs' make profile-do--default--all profile-do--net_2_0--all profile-do--net_2_1--all make[4]: Entering directory `/home/atsushi/svn/mcs' make PROFILE=basic all make[5]: Entering directory `/home/atsushi/svn/mcs' ** (C:/cygwin/usr/local/lib/mono/1.0/mcs.exe:496): WARNING **: cannot find CreateString for .ctor make[6]: *** [build/deps/basic-profile-check.exe] Interrupt Atsushi Eno ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] windows build breakage? (missing CreateString)
Hi Eno, Most of us had this issue, but it's a matter of making sure that you have a matching mono binary with mscorlib. If you are running mono from the build tree you must have MONO_PATH configured, otherwise, like my setup, just 'make install' it. If that doesn't help, you might need to bootstrap first from a tarball in case your instalation got corrupted. On 9/21/07, Atsushi Eno [EMAIL PROTECTED] wrote: Recently (I think it's been since middle of this week or so) I have been unsuccessful to build non-bootstrap mono on windows, it complains about missing CreateString. Is it only me or is the build broken? Note that it won't show up as monobuild status as it is non-bootstrap build.) Making all in net_2_0 make[3]: Entering directory `/home/atsushi/svn/mono/data/net_2_0' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/home/atsushi/svn/mono/data/net_2_0' make[3]: Entering directory `/home/atsushi/svn/mono/data' make[3]: Nothing to be done for `all-am'. make[3]: Leaving directory `/home/atsushi/svn/mono/data' make[2]: Leaving directory `/home/atsushi/svn/mono/data' Making all in runtime make[2]: Entering directory `/home/atsushi/svn/mono/runtime' if test -w ../../mcs; then :; else chmod -R +w ../../mcs; fi cd ../../mcs make PROFILES='default net_2_0 net_2_1' CC='gcc -mno-cygwin -g' all-profiles make[3]: Entering directory `/home/atsushi/svn/mcs' make profile-do--default--all profile-do--net_2_0--all profile-do--net_2_1--all make[4]: Entering directory `/home/atsushi/svn/mcs' make PROFILE=basic all make[5]: Entering directory `/home/atsushi/svn/mcs' ** (C:/cygwin/usr/local/lib/mono/1.0/mcs.exe:496): WARNING **: cannot find CreateString for .ctor make[6]: *** [build/deps/basic-profile-check.exe] Interrupt Atsushi Eno ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] More ODBC questions: AutoCommit and BeginTransaction
mandag 03 September 2007 skrev Mads Bondo Dydensborg:
Hi again.
I still can not resolve this question. But I did discover, that there is no
public way to change the autocommit mode through the mono stack, meaning,
that if one uses a transaction, one can never return to autocommit mode.
Is this really the right way to do things?
Regards
Mads
Hi all
I am not posting a bug, because I have no idea if this is a bug. Perhaps
this
is the intended way:
For ODBC connections, the default mode is autocommit: Each statement is
followed by an commit, done by the driver, client side. This can be disabled
programmatically.
When an ODBC transaction is created in mono, we change the attributes in
OdbcTransaction.cs:
51 internal OdbcTransaction(OdbcConnection conn,
IsolationLevel isolationlevel)
52 {
53 // Set Auto-commit (102) to false
54 OdbcReturn
ret=libodbc.SQLSetConnectAttr(conn.hDbc, OdbcConnectionAttribute.AutoCommit,
IntPtr.Zero, 0);
We have to do that, obviously, but my question is wheter mono should
reestablish the state of autocommit upon completion of the transaction?
Currently it does not, but is this to be expected? I think, from my reading
that it is, but would very much like a confirmation.
Currently I am not able to check out the behavoiur using MS .NET.
Thanks,
Regards
Mads
--
Med venlig hilsen/Regards
Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo
Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77
34
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
--
Med venlig hilsen/Regards
Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77 34
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
