Re: [Mono-list] Mono.Facebook
On Dec 19, 2007, at 10:49 PM, Julien Sobrier wrote: I was wondering what is the status of this library, and what is planned for the future. Do you recommend to use this one rather than the official one? What is the difference between Mon.Facebook and Mono.Faceebook.Platform? Mono.Facebook is the current implementation, tied to XmlDocument and uses the XML response type. I started Mono.Facebook.Platform to target platform applications specifically and uses JSON as the response type (which is much smaller in terms of transport time and sometimes in terms of Facebook's generation of data). Currently I would use Mono.Facebook for anything production since Mono.Facebook.Platform is still in a state of flux and very-very- alpha. When I'm done it'll support almost everything you would want to do with ASP.NET Facebook platform applications and it will also support the Bebo platform (similar, but has some quirks) as well, out of the box. Mono.Facebook.Platform also requires you use the .NET 2.0 profile and gmcs. BTW, there are 2 API I couldn't find in Mono.Facebook * session valiation: find out if a session is valid from the Faebook URI parameters, private and public key (without actually tryingto establish the facebook session, as described at the end of http://developers.facebook.com/documentation.php?doc=auth) * ordered list of friends: it is not possible to oder a list of Friend simple bythe last name to match the way Facebook oders it under the Friends tab. For example, if a last name is made of 2 words like de Vaux, Facebook puts it at V, not at D. I guess it is the same thing for van ..., von ..., etc. Session validation doesn't necessarily apply to Mono.Facebook.Platform, since you can accomplish these tasks through the RequireAdd or RequireLogin methods. As for ordering of friends lists this is only possible (at all, regardless of library) by using FQL with the ORDER BY token, which isn't currently supported by Bebo's implementation. If you're curious about trying out Mono.Facebook.Platform, I haven't documented much if anything, but I've written an application that's currently live and chugging along with users called Why are you awesome? (http://apps.facebook.com/whyareyouawesome/) you can grab the source code with: svn co https://source.geekisp.com/bleep/trunk/WhyAreYouAwesome/ As for Mono.Facebook, there are some examples in the examples/ directory; let me know if you need any further help :) Cheers, -R. Tyler Ballance Slide, Inc. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] LolCode on the DLR with Mono
On Nov 17, 2007, at 3:08 AM, Sandy Dunlop wrote: Does anyone know why CreateDelegate is failing when called from the Microsoft.Scripting assembly? Is this something I can work around? Firstly. http://icanhascheezburger.com/2007/10/13/fail-2/ Secondly I would guess it's because there doesn't appear to be a Microsoft.Scripting (at least at a first glance at my development GAC with the olive code installed), past the work in Microsoft.Scripting.Silverlight. Have you tried referencing a Microsoft version of that DLL just to see if that much works? I could be wrong on this whole thing, but how often do I get to post a LOL cat to the mono list :) Does the latest IronPython alpha (6?) work for you either? KTHX BAI! ;) ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Festival TTS Wrapper
On Oct 29, 2007, at 4:17 PM, [EMAIL PROTECTED] wrote: Sorry to disapoint you, but my wrapper is not even a server call to the festival TTS, is more cheating :-), is only a wrapper for a C shared library that send the correct echo $MESSAGE | festival -- tts :-) , I also see the posibility to try a more sofisticate wrapper, but as you say is to much complicate, so this is a working approach :-) A novel approach to say the least, but I agree, it's not great, but it's a start :) I attach the C shared library and the C# wraper with a simple test program. May be we can work in a better wrapper. I also agree on this :) I think we should consider approaching managed text-to-speech from the side of Flite instead of Festival (I think lupus actually suggested this when I was first discussing it on #mono, but I foolishly went ahead with trying for Festival anyways). The one core thing I started to do with my wrapper (from here out referred to as Tao.Festival) was provide support for both a server-oriented Festival interface, i.e. connecting on the Festival's port (1234 I believe) and then performing the commands, or using a C#-C-C++ wrapper I had written to take advantage of libFestival.a which is usually installed on most Linux systems when the Festival package is added. I had not started on the server-oriented code yet, but had the wrappers in place for relying on libFestival which proved to be a stupid idea and will/ would cause the entire Mono process to SIGSEGV every single time because of some of the intricacies to native platform interop with code that's *so* expectant on being statically linked *always* as Festival is. I can upload the code to my anonymous Subversion repository, but I think it's only worth it from a research perspective in seeing why exactly Festival is a bad route to go with :) Our end goal is easy to define I think, ideally we would want to provide developers with the following calls: Mono.Speech.SayText(Hello Monkeys!); Mono.Speech.SayText(Hello Monkeys!, FileStream, Mono.Speech.WaveFileType); I suggest you look at the following for an idea on why Flite will be far easier: http://www.speech.cs.cmu.edu/flite/doc/flite_7.html#SEC17 I will try to port my existing design of Tao.Festival over to something more Flite-based this weekend, at the very least to evaluate whether or not Flite will truly be a better option than Festival, and to evaluate whether the concept will *actually* work. As much as I would love to be able to provide compatibility with Microsoft's new System.Speech.Synthesis API, I just don't think that's ever going to be possible given the state of open source speech synthesis systems (unless somebody writes a fully managed one on Mono of course :)). So maybe would should just strive for providing something that Gtk# developers can use, specifically in some of the applications Novell includes in their SUSE distribution (how cool would it be for Banshee to tell you what song it's spinning up next like a DJ!) I'm tremendously busy during the week, but I'll post something this weekend after I'm able to set aside some time to get back to TTS and wrapping crazy interop code around legacy C (Flite's last release was almost 3 and a half years ago). Glad to see somebody else is interested though! :) Cheers, -R. Tyler Ballance p.s. using Apple's Carbon APIs for Speech Synthesis, this hypothetical Mono.Speech API could also work on Mac OS X :-D ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] MonoSummit: Planning the Sessions
On Oct 26, 2007, at 7:23 AM, Miguel de Icaza wrote: Hey folks, Am looking for ideas for topics that developers would be interested in hearing about at the Mono Summit. Last year, we chose in advance that the developers in the team will each present what they are working on. This does not necessarily map to what people wanted to learn or discuss. As one of the folks who couldn't convince their employers that a trip to spain in November is *necessary*, I swear! will there be any sort of netcasting or recording sessions on video to be posted after the fact? I would really love to hear about some of the more dynamic language sessions that you mentioned and of course, some Mono/Mac OS X stuff as well. I wish I could participate, but I think I've expended my favors to ask of my employer for the year already ;) Cheers, -R. Tyler Ballance ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] [Mono-dev] MonoSummit: Planning the Sessions
On Oct 26, 2007, at 7:23 AM, Miguel de Icaza wrote: Hey folks, Am looking for ideas for topics that developers would be interested in hearing about at the Mono Summit. Last year, we chose in advance that the developers in the team will each present what they are working on. This does not necessarily map to what people wanted to learn or discuss. As one of the folks who couldn't convince their employers that a trip to spain in November is *necessary*, I swear! will there be any sort of netcasting or recording sessions on video to be posted after the fact? I would really love to hear about some of the more dynamic language sessions that you mentioned and of course, some Mono/Mac OS X stuff as well. I wish I could participate, but I think I've expended my favors to ask of my employer for the year already ;) Cheers, -R. Tyler Ballance ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] C# festival TTS wrapper
On Oct 20, 2007, at 8:55 PM, Mauricio Henriquez wrote: Hi: Recently I build a very, very basic Festival (text to speech engine) wrapper for C#, with this you can make talk your C# app :-), anyone interesting?, where can I put the files to make this available?. Recently I started working on something similar a few weeks ago but stopped after realizing how insane getting something functional would be :-P The main problem with Festival, especially embedding it (using their server interface is cheating ;)), is surprisingly difficult since the main opensource TTS systems (Festival and FLite) both rely primarily on statically linking the hell out of everything with the most convoluted build systems. Getting code marshalling to work with Fetsival proved to be too large of a pain, and I'm hesitant to try the same with FLite since they're so similar. That notwithstanding, I'm very interested to see what you've come up with, even if it does just hit their server API. Please let us know when you post the source code. :) Cheers, -R. Tyler Ballance ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Developers: need 1.2.6 release notes.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 24, 2007, at 8:25 AM, Miguel de Icaza wrote: Hey folks, If you developed a new feature, fixed an important bug, implemented a new optimization or reached an important milestone that must be mentioned in the release notes, please send me an email so we can include these for the Mono 1.2.6 release notes. I was unable to find anything regarding a roadmap, so I guess the pertinent question is, when should everybody have these in to you, and when's 1.2.6 planned for release? (When I spoke with you in Boston I remember you saying the next release was in a couple months) Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHH3HVA2GmJ0VpG78RAqolAKCOR6HaFXuJNf0C90X/fBW7B718VACeLiLw HPwTp++46ABuJjPq2MIduwA= =p+Vc -END PGP SIGNATURE- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] Citing Mono
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 24, 2007, at 12:36 PM, murthy.sudarshan wrote: Hello, How do I cite Mono in a (conference/journal/dissertation) publication? I could not find the name of Mono's publisher on the Mono web site. The Mono Project (dink) is an open source, and thus mostly decentralized, product built by a community of developers. It's not published by any one company, although Novell and Mainsoft contribute greatly. Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHH6EIA2GmJ0VpG78RAhbyAJwJORcbcG3F/EC3aT1tOZebbCKdCACeJt60 2jvfFB45nMfVV5OKgLR6uG8= =gqaW -END PGP SIGNATURE- ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] SQL Server 2005
On Oct 23, 2007, at 11:35 AM, Konstantin Bokarius wrote: When will Mono support SQL Server 2005? As soon as you write it ;) Sorry, couldn't help myself, I haven't a clue. Cheers, -R. Tyler Ballance PGP.sig Description: This is a digitally signed message part ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Replicating System.Web.Script.Serialization bugs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 15, 2007, at 2:14 AM, Konstantin Triger wrote: Hey Tyler, 1. Your code must come AFTER 'if (type == null)' for obvious reasons. The best place would be just before 'return Convert.ChangeType (obj, type);' at the end of the function. 2. Please add the following test cases (passing on MS .Net): Converting to Nullable from empty and non-empty strings. I went ahead and committed in r 87847 (and r 87848 because I'm an idiot and forgot to move the code down and only realized after I checked with null _) Anyways, I'm a bit unsure where I should commit the test, I'm assuming in System.Web.Extensions/Test/ System.Web.Script.Serialization/JavaScriptSerializer.cs? I'm just unsure because I see gert commit tests like a madman elsewhere :-P Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHGexDA2GmJ0VpG78RAjwtAJ4pq1cZsYNbDBSDUhHnhUvI5HKoBwCfX5Hm XaI/yQu+6Hi3erorUm1hS60= =jmcq -END PGP SIGNATURE- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] mod_mono on FreeBSD ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 19, 2007, at 10:00 PM, Ruben Guinez wrote: Hi everybody!. I need to deploy an application with apache/mod_mono to FreeBSD (5.3). I can to do that? Or not yet? Please anybody does know?. I'm currently doing this running mod_mono out of the BSD-Sharp ports tree. I can't remember if the machines are 5-STABLE or 6-STABLE, but they're certainly running BSD-Sharp :) Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHGZ8QA2GmJ0VpG78RAhgPAJ0aIfc7JCN8wLaRHDzIAbkXVLyh1wCghes9 sVuk88SLHBobJ2cuulUDUtw= =RDGl -END PGP SIGNATURE- ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Windows vs Linux - different behavior using Facebook.dll
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 11, 2007, at 1:48 PM, Abe Gillespie wrote: Hello All, I'm using this Facebook toolkit as I attempt to develop a Facebook app: Your mileage may vary with using the FacebookToolkit as it has a LOT of .NET 2 and .NET 3 features, like LINQ and reasonably obtuse UserControls. Also of relevance would be how you're using this, for a Platform application, or an external desktop/web application outside of Facebook? I would recommend you try running this against trunk, more just because I'm curious as to how it'll work, but if things continue to explode, I'll dig into it. If all else fails, I know the guy who wrote the toolkit, and work a couple of blocks away from him, so I can go hit him with a stick if he's doing anything *too* nasty in there :) Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHGenaA2GmJ0VpG78RAqojAJwPoChJaos58EZ68P6jlUYmaTV2aACguaYQ yaYWe9CT9lenbGeXaQkmaRs= =TPYC -END PGP SIGNATURE- ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Replicating System.Web.Script.Serialization bugs
On Oct 1, 2007, at 10:17 AM, Adar Wesley wrote: Hi Kosta and Tyler, Having worked on this code with Kosta and following this thread a couple of questions come to my mind. 1. Are there any other types that need special care, besides Nullable? How about generic types? As far as I remember, we don't have any tests with generics. Are we missing anything else? 2. I was trying to think of a good strategy for implementing this, and havn't made up my mind yet. I agree with Kosta that the try, catch approach is not the best way. I think something a bit more fine grained should be used. What would happen if the value is xxx and the type is int?? This should probably throw the error and not silently assign the null value. (Requires a test with MS code...) Coming back to this, since I'm hacking on it right now. A value of xxx _will_ throw an InvalidCastException, whereas an empty string will not. I think I might be overcomplicating this, the only possible valid JSON syntax for an empty value seems to be , I've got the following patch that I'm waiting on peer-review to commit. It handles the case in https://bugzilla.novell.com/show_bug.cgi? id=328836 with regards to mimicking the .NET behavior for empty JSON values with regards to Nullable types. It'll still throw on xxx values that are attempting to be converted to long/int/etc. Konstantin, just say the word and it'll be committed, otherwise, I'm at a lose for solutions to handle this :-P Cheers, -R. Tyler Ballance JavaScriptSerializer.328836.patch Description: Binary data PGP.sig Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Replicating System.Web.Script.Serialization bugs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Oct 1, 2007, at 1:42 AM, Konstantin Triger wrote: Hey Tyler, If you need this urgently, please provide a fix. If not - it will be somewhere in my todo list and will be fixed in a couple of weeks. Would you recommend just adding another if statement in: internal object ConvertToType (Type type, object obj) Or is the bug elsewhere? The best I could tell as far as a fix would be would be to check if it's a Nullable type, and then try/catch a convert recursing into ConvertToType and in the catch setting hasValue = false, etc. If you can take the time to suggest a plan of action, I'd be more than happy to fix, test and commit a patch for this, since it's somewhat blocking me right now :) Cheers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHAMahA2GmJ0VpG78RAj6DAJwNBqkPL85OBjufkZafa4v6/lW60wCgoiJT DUyhiLCjc+xXrwQ6i8ouMcY= =rs5n -END 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] Replicating System.Web.Script.Serialization bugs
On Oct 1, 2007, at 10:47 AM, Konstantin Triger wrote: 2. I was trying to think of a good strategy for implementing this, and havn't made up my mind yet. I agree with Kosta that the try, catch approach is not the best way. I think something a bit more fine grained should be used. What would happen if the value is xxx and the type is int?? This should probably throw the error and not silently assign the null value. (Requires a test with MS code...) That's what I understood Tyler did and got null… Do I understand correctly? My experiments weren't with JSON that actually was a string (i.e. xxx) being Convert.ToInt32()'d, it was the fact that most JSON API providers denote any empty value with an empty string (i.e. ) Which in our current serializer, does a check in Convert.ToInt32/Int64 such that str.Length 0, and throws an exception, instead of handling the nullable type that I was passing it.. I'm not sure if the fix is in Convert.ChangeType to handle Nullable types properly, or if it's specific to System.Web.Script.Serialization. I didn't have the time to test this further. Cheers PGP.sig Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Replicating System.Web.Script.Serialization bugs
On Sep 26, 2007, at 12:39 AM, Andrés G. Aragoneses [ knocte ] wrote:
R. Tyler Ballance escribió:
[...]
Without providing compatibility for MS.NET, the only alternatives
seem to be some application specific hacks, either with crazy
properties as mentioned above, or using Nullable types (which we
don't yet support in Mono right?)
Hey, I think Mono has support for Nullables since much time ago.
Unfortunately, I tried this in Mono, and our
System.Web.Script.Serialization barfs on Nullable types :(
Fortunately, .NET doesn't! Alas there is hope :)
I've attached my modified JsonTest class (attached), and here's the
output:
Microsoft .NET 2.0.5:
--
Testing for empty values in JSON with this string:
{int_key : }
int_key =
--
Mono version 1.2.5 (/trunk/ r86375)
--
[mono] \w @ mono JsonTest.exe
Testing for empty values in JSON with this string:
{int_key : }
Unhandled Exception: System.InvalidCastException: Unknown target
conversion type
at System.Convert.ToType (System.Object value, System.Type
conversionType, IFormatProvider provider) [0x0]
at System.Convert.ChangeType (System.Object value, System.Type
conversionType) [0x0]
at
System.Web.Script.Serialization.JavaScriptSerializer.ConvertToType
(System.Type type, System.Object obj) [0x0]
at
System.Web.Script.Serialization.JavaScriptSerializer.ConvertToObject
(IDictionary`2 dict, System.Type type) [0x0]
at
System.Web.Script.Serialization.JavaScriptSerializer.ConvertToType
(System.Type type, System.Object obj) [0x0]
at
System.Web.Script.Serialization.JavaScriptSerializer.ConvertToType
[JsonObject] (System.Object obj) [0x0]
at System.Web.Script.Serialization.JavaScriptSerializer.Deserialize
[JsonObject] (System.String input) [0x0]
at JsonTests.JsonTest.Main (System.String[] args) [0x0]
[mono] \w @
--
I've also reported the bug here: https://bugzilla.novell.com/
show_bug.cgi?id=328836
Cheers
JsonTest.cs
Description: Binary data
PGP.sig
Description: This is a digitally signed message part
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Replicating System.Web.Script.Serialization bugs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sep 25, 2007, at 6:58 AM, Konstantin Triger wrote: One workaround would be to slightly massage the script prior to deserialization. A regexp should remedy things, maybe? This will kill performance, so can be a workaround implemented in app code only... The other application-only hack that I thought could be implemented would be changing all of the properties that should be serialized in from JSON would be strings, and then either using a separate property that would be responsible for calling Convert.ToInt64 if the value is not an empty string, otherwise returning UINT_MAX or something that would indicate that there is not a real value for this Int64 property. Without providing compatibility for MS.NET, the only alternatives seem to be some application specific hacks, either with crazy properties as mentioned above, or using Nullable types (which we don't yet support in Mono right?) Proverbial rock and hard place :-P Cheers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFG+Ww4A2GmJ0VpG78RAnd8AKCjJmW3emgmwGEniSMnUXxTTipwdACfTrQ2 hlU6YQOspOm9AvJaOHwUBKk= =4gYJ -END PGP SIGNATURE- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Replicating System.Web.Script.Serialization bugs
I discovered that whilst consuming Facebook's API data in JSON
format, that both .NET 2.0 and Mono (from trunk) have the exact same
System.Web.Script.Serialization bug when dealing with empty value
fields in the JSON key/value string, for example:
{some_key : }
Which is handled properly as an empty value by Python and Javascript
alike, barfs inside the stronger-typed C#, when you try to serialize
it to a long value (for example), throwing the following exception
on both .NET and Mono
Unhandled Exception: System.Exception: is not a valid value for
Int64. --- System.FormatException: Input string was not in the
correct format: s.Length==0.
at System.Int64.Parse (System.String s, NumberStyles style,
IFormatProvider fp) [0x0]
at System.ComponentModel.Int64Converter.ConvertFromString
(System.String value, System.Globalization.NumberFormatInfo format)
[0x0]
at System.ComponentModel.BaseNumberConverter.ConvertFrom
(ITypeDescriptorContext context, System.Globalization.CultureInfo
culture, System.Object value) [0x0]
[full stack trace from attached test code at the bottom of this email]
Ideally this would just *not* be serialized out, leaving the object's
property that maps to some_key empty/uninitialized, but instead the
application that consumes and deserializes the JSON will explode,
especially if the JSON provider (Facebook in my case) provides fields
such as this as optional.
As I mentioned to sontek in the IRC channel, it certainly seems like
I'm screwed in this case, since we are compatible with Microsoft's
bugs :( So the bigger question is, what work around or recourse do I
have in this case? I have kicked around the idea of adding a
Mono.Script.Serialization to trunk that would essentially just apply
a series of patches to System.Web.Script.Serialization, but I'd
rather avoid that route as it doesn't tend to grow well, but I don't
see a really decent workaround except to implement a magic property
for EVERY single optional JSON key (which in some calls can be up to
about 50 keys) to do a Convert.ToInt64 if there's a string on get {},
otherwise return a null (this sucks, and I don't want to implement it
for every frakking deserializable attribute that could need to be
deserialized as anything but a string)
I've attached my test case, but I have a sense someone is going to
point out that the emperor has no clothes, and that I am indeed
screwed :-P
Cheers
JsonTest.cs
Description: Binary data
Unhandled Exception: System.Exception: is not a valid value for
Int64. --- System.FormatException: Input string was not in the
correct format: s.Length==0.
at System.Int64.Parse (System.String s, NumberStyles style,
IFormatProvider fp) [0x0]
at System.ComponentModel.Int64Converter.ConvertFromString
(System.String value, System.Globalization.NumberFormatInfo format)
[0x0]
at System.ComponentModel.BaseNumberConverter.ConvertFrom
(ITypeDescriptorContext context, System.Globalization.CultureInfo
culture, System.Object value) [0x0]
--- End of inner exception stack trace ---
at System.ComponentModel.BaseNumberConverter.ConvertFrom
(ITypeDescriptorContext context, System.Globalization.CultureInfo
culture, System.Object value) [0x0]
at System.ComponentModel.TypeConverter.ConvertFromString
(ITypeDescriptorContext context, System.Globalization.CultureInfo
culture, System.String text) [0x0]
at System.ComponentModel.TypeConverter.ConvertFromInvariantString
(ITypeDescriptorContext context, System.String text) [0x0]
at System.ComponentModel.TypeConverter.ConvertFromInvariantString
(System.String text) [0x0]
at
System.Web.Script.Serialization.JavaScriptSerializer.ConvertToType
(System.Type type, System.Object obj) [0x0]
at
System.Web.Script.Serialization.JavaScriptSerializer.ConvertToObject
(IDictionary`2 dict, System.Type type) [0x0]
at
System.Web.Script.Serialization.JavaScriptSerializer.ConvertToType
(System.Type type, System.Object obj) [0x0]
at
System.Web.Script.Serialization.JavaScriptSerializer.ConvertToType
[JsonObject] (System.Object obj) [0x0]
at System.Web.Script.Serialization.JavaScriptSerializer.Deserialize
[JsonObject] (System.String input) [0x0]
at JsonTests.JsonTest.Main (System.String[] args) [0x0]
PGP.sig
Description: This is a digitally signed message part
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Who broke master pages in trunk :)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 31, 2007, at 4:58 AM, R. Tyler Ballance wrote: I'm checking out the 1.2.5 tag from SVN just to double check that the release didn't contain the regression, I'll report back if it does. For what it's worth, the tagged release of 1.2.5 doesn't have this issue, so it's a recently committed regression I'm assuming Mono JIT compiler version 1.2.5 (/tags/mono-1-2-5/ r85094) Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFG2A5FA2GmJ0VpG78RAmEOAJ0RLwM3/Q4OrgbKhuYPzkcidIVaCQCguvqe dic2BaNwqETakMnVv0sLJ3E= =AnFh -END 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] Who broke master pages in trunk :)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 31, 2007, at 7:00 AM, Marek Habersack wrote: Your test works perfectly for me - no book (on r85091) Running with a more recent snapshot (Mono JIT compiler version 1.2.5 (/trunk/ r85187)) versus a released version (Mono JIT compiler version 1.2.3.1) I still get functional ASP.NET master pages in 1.2.3.1, and errors in 1.2.5 r85187. Grumble. If anybody has any tips for how I can debug this a bit better than I have thus far, I've run with MONO_LOG_LEVEL=debug to verifiy that it's running against the DLLs in my trunk GAC, but other than that I'm drawing a blank with an error 500 on it ;) Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFG2sf9A2GmJ0VpG78RAhRFAKCE70gyOARnDhmiDB30xeCXUSqO9ACfarQc wg0uLM4yY5Wheu61/AWTWhk= =mjgH -END PGP SIGNATURE- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Who broke master pages in trunk :)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I figured I'd throw this out there while testing out my ASP.NET applications against trunk this evening I discovered that every single project that used a master page would throw errors like: Description: Error parsing a resource required to service this request. Review your source file and modify it to fix this error. Error message: Cannot find type DontPanic.Default File name: /home/tyler/source/bleep/DontPanic/site/Default.aspx Line: 1 Source Error: %@ Page Language=C# Inherits=DontPanic.Default MasterPageFile=DontPanic.master % %@ Register TagPrefix=DontPanic TagName=Search Src=Search.ascx % asp:Content Runat=server ID=DefaultContent ContentPlaceHolderID=MasterPageContent The Mono version/rev I'm using is: Mono JIT compiler version 1.2.5 (/trunk/ r85091) Just thought I'd bring this up, I'd do an 'svn blame' but I don't even know where to start :) I'm checking out the 1.2.5 tag from SVN just to double check that the release didn't contain the regression, I'll report back if it does. Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFG2AJSA2GmJ0VpG78RApGWAJ9T8sK+rA0IaQG/ICAcE8SyWwn93QCeN92b oNeYAQ4iSbgO0EtgAWIt/D4= =b2WO -END 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] Who broke master pages in trunk :)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 31, 2007, at 5:20 AM, Marek Habersack wrote: On Fri, 31 Aug 2007 04:58:10 -0700, R. Tyler Ballance [EMAIL PROTECTED] scribbled: Hey, [snip] Just thought I'd bring this up, I'd do an 'svn blame' but I don't even know where to start :) Would you mind filing a bug with a test case? Thanks in advance, Working on that, if Novell's crap login and authentication system would send me my frakking validation email Anyways, here's the test case with the screenshots for 1.2.5 (release) vs. the rev of HEAD I'm running. http://monkeypox.org/mono/bugs/masterpages/ The test case uses nant, so just run 'nant run' and it'll fire up xsp2 for you ;) Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFG2BfJA2GmJ0VpG78RAnmsAJ0X3Mcvdasps5dcpUI/i2MoNl92OQCeOIX0 2rm9dOGIvmT3c95DE4VJu0c= =/I9D -END PGP SIGNATURE- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] DLLMapping for ASP.NET based projects
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 29, 2007, at 7:08 AM, Amc Gmail wrote: in our case: 1. we have api.dll which doing some p/invoke from our libapi.so 2. in api.cs source code DllImport look like this: [DllImport(api)] private extern static int fnc(ref IntPtr io_ptr); 3. in web-site/bin i have api.dll and api.dll.config which is: ?xml version=1.0 encoding=utf-8? configuration !-- to debug under xsp: target=../build/libapi.so.1.0.1 to run under mod_mono: target=/path/to/our/lib/libapi.so. 1.0.1 to use /usr/lib default: target=api -- dllmap dll=api target=/path/to/our/lib/libapi.so.1.0.1 / /configuration as you can see i am not changing mono standard dll mappings which you may want to, but hope my sample would help somehow. good luck :) Yeah, tried this and it still doesn't work :/ My config is: ?xml version=1.0 encoding=utf-8? configuration dllmap target=./bin/libsqlite3.dylib dll=sqlite3/ /configuration Where ./bin/libsqlite3.dylib is in my xsproot directory's bin directory. Still no dice :-/ Cheers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFG1lx8A2GmJ0VpG78RAl9OAJ0c/O2OVeBepzl2Y58s13lYSCdFFQCghwuv ZExnR9IBpb5Mq5e9GVNGtVk= =CeJL -END PGP SIGNATURE- ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] DLLMapping for ASP.NET based projects
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been trying to figure this one out for a while, but I can't seem to crack it. Apple distributes a crap version of SQLite so I'm trying to get Mono.Data.Sqlite.dll to map properly to my own version (more recent, etc) with my ASP.NET based project (using xsp2 now) and I'm having an awful lot of trouble getting the usual' dllmap sort of stuff in my Mono.Data.Sqlite.dll.config to work properly Any tips on getting ASP.NET code that has to p/invoke to properly DLLMap like EXEs do? Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFG1A4RA2GmJ0VpG78RAqfgAKCWi5KUaYcLQUVZn9uQN8SCKDV5GQCff19d pj2A64YCb1fkOekenctGkuc= =kBGb -END PGP SIGNATURE- ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Trying to set up hosting on mono
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 13, 2007, at 1:29 AM, Andreas Färber wrote: Am 08.08.2007 um 16:02 schrieb Maxim Karavaev: It seems like Mono don't restart web-site after modifying of web.config file. Does FreeBSD use kevent-based file monitoring? That is broken so does not recognize file changes. My workaround is to set MONO_MANAGED_WATCHER=1. Yes, FreeBSD (and Mac OS X) have had kevent support for some time. (http://www.freebsd.org/cgi/man.cgi? query=kqueueapropos=0sektion=0format=html FreeBSD RELENG_4 AFAIK) If for some reason the mod_mono doesn't respect or use this is probably a bug, or a difference in implementations causing the watcher part of mod_mono to break on FreeBSD. Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGwM2hA2GmJ0VpG78RAh2QAJ9hGfgN7CcuHeBMCe+hKlo5SrG88QCgpmfJ swnsgYkVgHj+9tMh/sGVm+k= =st4v -END PGP SIGNATURE- ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-dev] Having difficulty porting to OS X.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Aug 1, 2007, at 1:42 PM, [EMAIL PROTECTED] wrote: Hi, I wrote a CSharp app using Visual Studio 2005 Express Edition. I brought the exe file over to the mac where I have installed the latest version of Mono. I get some error messages from mono and was hoping someone could help me work these out Applications using Windows Forms on Mac OS X will have turbulent waters to pass through. Unfortunately the GDI+ stuff is still based off of X11. Feel free to help port Windows Forms to use Quartz as a backend ;) Cheers, - -R. Tyler Ballance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGsP0RA2GmJ0VpG78RAvlzAJsHbAhY6fs78oFWvaFgaZHTzAkm6ACfaait rvpE0nbiCLcvBXXSfwXKfas= =qm/z -END PGP SIGNATURE- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] Developing in a mix environment
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jul 30, 2007, at 10:46 PM, John Anderson wrote: What are your guys best tips for working in a mix environment (Windows/Mac/Linux) ? How do you avoid running into new line/carriage return problems between editors? How do you handle building projects between the systems? -- Do you use nant/make files, if so, how do the windows developers handle that -- Do you use vs solutions with monodevelop? How well does it work? Is there something on the Mac that can do this? What are the gotchas about developing in a mixed environment? How well does the mono add-in for Visual Studio work? -- What versions does it work with I've been using NAnt and relatively standard editors (Vim and Emacs are 'relatively' cross-platform) and then as the other folks have already mentioned Subversion can be used to set properties on files to ensure line-ending standardization. The rub really comes when you need to work with developers that use Visual Studio 2005 (exclusively! =[) then it's either usually a case of running their existing project files through prj2make and hoping for the best or making your case for Nant or something like Premake/ PreBuild. Cheers, - - R. Tyler Balllance -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGsQbfA2GmJ0VpG78RAofYAJwPvmm/p4VtiSZHZUk5zZMWqH2oNQCdEqf0 vaXZ4Fwy6DG9pZUk0SwQITg= =m3U2 -END PGP SIGNATURE- ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-dev] Roadmap for System.Web.Extensions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy, I was wondering if anybody had an idea on the roadmap and/or release schedule for the System.Web.Extensions which currently sits in the Mono subversion repository but is not being distributed as far as I can tell. For now I am fine with using my local version of Mono built out of SVN, but I'm not sure if I want to depend on the JSON support in System.Web.Extensions until I'm certain when it'll go out ;) Cheers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGoxpkA2GmJ0VpG78RAq//AKChfWkrGTrCmqpWxZvaUqZAqU1fsACgrFCp cqV0ZLK746mhafQhVmQ34d4= =+c5o -END 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] Porting to OpenMoko
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Since we are not hardware hackers, we will only be getting the basic model, which is branded as Application Developer Platform and is 150 dollars cheaper too. I ordered my 'Basic' yesterday, and am anxiously awaiting it's arrival. In the meantime I'd like to get started with setting up a development that requires as little actual testing on the device as possible, i.e. using it as a last sanity check once something works virtualized (or if something doesn't, make sure it at least works in OpenMoko on the device) Have any of you gotten a QEMU or Xoo-based OM environment setup to cross-compile for ARM? If so, any caveats (especially on Feisty Fawn)? I'm currently fighting Qemu's refusal to accept SDL on the system, so past that, tips on building OpenMoko QEMU images would be especially helpful (or posting the images themselves!) I'll admit my laziness here, but I'd prefer not to fight up the same hill if one of you has :) The faster we can get Mono working on the device, the faster I can get a groovy Sansa-like interface working ;) Cheers -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGnds1A2GmJ0VpG78RAta/AKCBaPNDoqc94puWPWVujeZCVsR6dQCfUiT7 QEg91EWb799iQ5qyiNZAybA= =R14s -END PGP SIGNATURE- ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] Porting to OpenMoko
I've noticed on the OpenMoko wiki/gforge site that there is an active/planning project related to porting .NET/Mono, while deciding whether or not I should purchase an OpenMoko phone in lieu of purchasing the oft prised iPhone (no habla SDK :() I'm wondering if any of you have started working on a port, which would definitely influence my purchasing decision (not that I'm against starting the debugging with the debug board for our Mono ARM port, it is ARM right?) I would enjoy nothing more than to upgrade my phone with the OpenMoko phone, but the ability to start working on mobile Mono applications on it as well would be nice, not that the Nokia's aren't nice, but they're not as open :-P If I purchase the kit, I'll be purchasing the Neo Advanced set which includes the nice development extras (woot) and wouldn't mind a coffee shop hack-a-thon in the San Francisco area to get things started if anybody's up for it. Just figured I'd check. Cheers R. Tyler Ballance: Custom Mac and Linux Development at bleep. consulting contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] PGP.sig Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Porting to OpenMoko
On Jul 10, 2007, at 12:39 PM, Miguel de Icaza wrote: Hello, I am also considering getting an OpenMoko phone (personal) and getting a couple for developers in the Novell team one as well. Sounds great! Are you thinking it'll be worth chipping out for the advanced set with the debug board as well for Mono/Moonlight development? Or might the ability to hack on the single (Neo Basic) phone be enough? Just curious, they had me at black carrying case What some folks have been saying is that they want to port Moonlight/Silverlight to it, and implement all kinds of gratuitous animations on it. I wouldn't imagine this to be hard since OpenMoko (at least now) ships with a full libX11, along with plenty of other graphic libraries that make it seem like the most difficult aspect of the port would be getting the hosting of the Moonlight widgets working. That said, I guess we'll know Silverlight/Moonlight has made it when I can punch the monkey, on my phone :) Regardless, please share your experiences with the getting the phone if you can, I'm definitely interested in hearing how the process goes as I'll probably be ordering early next week. Cliff, have you successfully gotten OpenMoko up and running in QEMU just yet? I'm starting by tinkering with qemu-arm to see just how much of the Mono/Arm codebase will build and working back from there. Cheers R. Tyler Ballance: Custom Mac and Linux Development at bleep. consulting contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] PGP.sig Description: This is a digitally signed message part ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] [Mono-osx] Mono 1.2.3 Preview Pains
On Jan 26, 2007, at 4:02 PM, R. Tyler Ballance wrote: On Jan 26, 2007, at 3:33 PM, R. Tyler Ballance wrote: But that gets me building. I'm working through why my Dumbarton- based $PROJECT[ no longer...runs on 1.2.3, but here's the error: 2007-01-26 15:29:56.811 $PROJECT[14970] Compress Assembly Path: / Software/Perforce/user/tyler/$PROJECT[_(Network)/build/Debug/ $PROJECT[.app/Contents/Libraries/Compress.dll ** ERROR **: runtime invoke called on uninitialized runtime aborting... Stacktrace: $PROJECT[ has exited due to signal 6 (SIGABRT). While I know what this means, I'm not exactly sure why it's cropping up as this code workedthis morning on 1.2.2, More details to follow :) After rebuilding my Dumbarton.framework against the 1.2.3 preview I had installed, the SIGABRT went away. I'm somewhat curious as to if there is an issue with the embedded API in 1.2.2 being incompatible with 1.2.3, and if that was causing the issue. It is certainly not an issue to switch development to using 1.2.3 instead of the 1.2.2 release, but something seems awry in the Dumbarton linked against 1.2.2 would break completely for 1.2.3; did some API change deep in the runtime, or are all embedded projects subject to breakage on point releases? Just curious so I don't hit this issue again. Cheers R. Tyler Ballance: Custom Mac and Linux Development at bleep. consulting contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] DllNotFoundException Woes
I've been using this Mono application I've developed just fine on a handful of machines for quite some time, and we're starting to move it over to new (SUSE/RHEL4) machines and all of a sudden, we're seeing just System.DllNotFoundException's when we start it now. I've even tried directly mapping with this exe.config file: configuration dllmap dll=Asset target=/usr/local/ansa/bin/libAsset.so / dllmap dll=Package target=/usr/local/ansa/bin/ libPackage.so / /configuration But regardless it's still spitting: System.DllNotFoundException: /usr/local/ansa/bin/libAsset.so at (wrapper managed-to-native) Autonomic.Ansa.LibAsset:findOSName () [...snip...] Despite the fact that I'm staring right at the file: [EMAIL PROTECTED]:~ ls -la /usr/local/ansa/bin/libAsset.so -rwxr-xr-x 1 root root 24352 2007-01-16 02:12 /usr/local/ansa/bin/ libAsset.so I'm pretty sure everything's spelled right and mapped correctly, but on neither my fresh SUSE 10.0 install, nor my fresh RHEL4 (both with just mono-core installed) can seem to figure out where the frak the asset library is :( Ideas? Cheers R. Tyler Ballance: Custom Mac and Linux Development at bleep. consulting contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] DllNotFoundException Woes
On Jan 16, 2007, at 7:08 PM, Robert Jordan wrote: Try ldd /usr/local/ansa/bin/libAsset.so. Maybe it's missing some references. If not, you may trace Mono's native lib loader with MONO_LOG_LEVEL=debug MONO_LOG_MASK=dll mono yourapp.exe ldd(1) did the trick. I absolutely hate the Linux version of DLL Hell. it wasn't finding librpm-4.4.so, instead of trying to link against librpm-4.1.so. Adjusting the MONO_LOG_LEVEL also helped point out the error, I'll have to backlog this into memory next time DllNotFoundExcetion's pop up. Thanks :) R. Tyler Ballance: Custom Mac and Linux Development at bleep. consulting contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-dev] UnixStream Patch
I know I've talked about the desire for this simple addition to the UnixStream class with Alp before, but I have found a need for it elsewhere.All this does is exposes the internal bool ownsHandle as a property, so it can be modified after instantiation, instead of only in the UnixStream(int, bool) constructor.Cheers UnixStream.cs.patch Description: Binary data R. Tyler Ballance: Custom Mac and Linux Development at bleep. consulting contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] UnixStream Patch
On Dec 22, 2006, at 8:13 AM, Jonathan Pryor wrote: On Fri, 2006-12-22 at 03:42 -0600, R. Tyler Ballance wrote: I know I've talked about the desire for this simple addition to the UnixStream class with Alp before, but I have found a need for it elsewhere. Could you tell us what the need is? I can't think of any scenarios in which it would be necessary... When using a class such as UnixFileInfo that can create/open and return a UnixStream there's absolutely no way to wrest control over who owns the handle because the object's already instantiated. In a set of scenarios when dealing with installed libraries (Mac OS X) some of them have a compounded close function, that finishes compression, for example, and then proceeds to close() the file descriptor. My current workaround for this is to use a shim between the installed libraries, and my Mono code to accomplish the same task that could be accomplished if I could set 'ownsHandle' after object instantiation. Cheers R. Tyler Ballance: Custom Mac and Linux Development at bleep. consulting contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-list] using Mono.Unix
On Dec 7, 2006, at 12:42 AM, brad brock wrote: I've tried but failed. For information, I use Mono that comes with debian etch. This is the result of 'mono -V' command : Mono JIT compiler version 1.1.17.1, (C) 2002-2006 Novell, Inc and Contributors. www.mono-project.com TLS: normal GC:Included Boehm (with typed GC) SIGSEGV: normal Disabled: none And this is the error message when I compiled my source code : test.cs(9,44): error CS0234: The type or namespace name `Unix' does not exist in the namespace `Mono'. Are you missing an assembly reference? Compilation failed: 1 error(s), 0 warnings How should I fix it? mcs -r:Mono.Unix.dll yourunixfile.cs Cheers R. Tyler Ballance: Custom Mac and Linux Development at bleep. consulting contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] How to pass arrays from C to embedded Mono?
On Nov 18, 2006, at 4:25 AM, Hugh Perkins wrote: How can arrays be passed from C into embedded Mono? As I had mentioned in IRC (remember, you decided to /ignore me) The answer is in the documentation (http://www.mono-project.com/ Interop_with_Native_Libraries#Arrays_Embedded_Within_Structures) There should be no difference conceptually between marshalling an array into a standard managed Mono runtime versus marshalling into a embedded Mono runtime. You still need to marshal the data properly between the unmanaged and managed bits of the executable's runtime. The steps for calling and passing the array from C into the embedded runtime should be apparent after conforming the following bits of documentation (http://www.mono-project.com/ Embedding_Mono#Invoking_Methods_in_the_CIL_universe) to your needs. Cheers R. Tyler Ballance: Custom Mac and Linux Development at bleep. consulting contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] Uncertainty and Doubt about MONO
On Nov 4, 2006, at 7:56 PM, Jonathan Pryor wrote:*Where* did Novell admit anything similar to this? To paraphrase theSCO case, provide file line numbers for confirmation. :-)Microsoft Novell only appear to have signed a statement saying thatneither company will sue the other companies customers over *any*patents. This would likely apply to Novell Netware and eDirectory asmuch as it applies to openSUSE.Forgive me for being naive, but regardless of the IP status of Mono, or any of the Novell products, how on earth does the legality of their product come under the realm of my responsibility, to where I can be held liable for using their products, notably, Mono?Say I'm implementing a completely cross-platform solution that uses the .NET runtime on the Windows platform, and the Mono runtime everywhere else, if there is any liable intellectual property in the Mono runtime, how on earth am I (as a customer of Novell, and someone who merely uses the Mono runtime) in any legal danger?To use to a physical metaphor, say I buy these special receding screws from MiguelCo Construction Supplies, and I build numerous houses/buildings with said receding screws (since MiguelCo's receding screws are cheaper, and work with more types of material), if further down the line its discovered that MiguelCo's receding screws are really a take-off on GatesCorp's design (which are far more expensive, and only work in redwood indigenous to the pacific northwest), legally, how can I even be included in any sort of litigation?All I did was build something that uses legitimate (to the best of my knowledge) tools and materials? Predict doom as much as you want about a Novell/Microsoft partnership, but how does their IP somehow damn my products that base off of theirs?That said, maybe Microsoft will be a bit more forthcoming with some of the features/specifications that are needed to have proper .NET 2.0 class library compatibilityor they'll just sue us all ;)CheersR. Tyler Ballance: Lead Mac Developer at bleep. software contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Supporting a Mono-based project on AIX
Howdy, I have a client that's looking to move our recent port of our software to Mono to support AIX as well as Linux, etc.I've read previous mailing list posts about somebody being able to compile Mono for AIX, and I was wondering if there's a project page for Mono/AIX, or any sort of status report? Stability of Mono on AIX?Mono has been a godsend in that we can support Mac, Linux, Solaris, FreeBSD, etc with one code base, but AIX support is the proverbial holy grail for us, anybody have any information pertaining to Mono on AIX? Cheers R. Tyler Ballance: Custom Mac and Linux Development at bleep. consulting contact: [EMAIL PROTECTED] | jabber: [EMAIL PROTECTED] ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
