This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I am still trying to get LightSpeed to work for the first time. LightSpeed is referencing a method that does not exist in Mono's System.Data. I tried builing on Windows and running on Mac, and I tried building on Mac and running on Mac. I also tried copying Windows System.Data, but as expected, Mono could not use it because it calls native code. Is there a workaround for this? (BTW, I really want to use Linq, so I cannot use the compatibility version.) Missing method System.Data.SqlClient.SqlParameter::set_UdtTypeName(string) in assembly /Library/Frameworks/Mono.framework/Versions/2.10.6/lib/mono/gac/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll, referenced in assembly /Users/kareemf/Documents/Tools/Taskmaster/TaskmasterMindscape/Taskmaster/bin/Debug/Mindscape.LightSpeed.dll Unhandled Exception: System.MissingMethodException: Method not found: 'System.Data.SqlClient.SqlParameter.set_UdtTypeName'. |
|
|
|
|
It may work, but it may not. The above is an example of where things fall down due to inconsistencies between what is available on the Windows .NET platform and Mono. I am guessing you have a mapping in your model which uses a SQL UDT (perhaps you are using one of the Spatial types?) which triggers the method call from LightSpeed. Unfortunately UDT support doesnt seem to be implemented in Mono - see http://www.go-mono.com/momareports/apis/System.Void%20System.Data.SqlClient.SqlParameter;;set_UdtTypeName(System.String) If this is the case you should look at switching the return type to be an object or a string instead so you can deal with the value more manually in your application code. I am not sure if the SQL Server types library loads happily on Mono (presumably it does) in which case you can re-cast or convert the value from Well Known Text to work around this.
Jeremy |
|
|
|
|
I still cannot get my first program to run on Mac with Mono. I am using Mono 2.10.6 and SnowLeopard. I created a new project, added one entity with just an identity column. The program creates one entity and attempts to insert that. This works on Windows. On Mac it fails for the same reason I have seen in all of my attempts (listed below). It looks like Lightspeed is always referencing that non-existant property. I am certainly not using UDT's as far as I can tell. Just a single table with a single int PK. I know in the past, according to forum posts, you were testing on Mac. Is that still the case? I ask because Mac will be a very important platform for my project (that and Windows). I hope for parity. Thanks. Kareem
|
|
|
|
|
I still cannot get my first program to run on Mac with Mono. I am using Mono 2.10.6 and SnowLeopard. I created a new project, added one entity with just an identity column. The program creates one entity and attempts to insert that. This works on Windows. On Mac it fails for the same reason I have seen in all of my attempts (listed below). It looks like Lightspeed is always referencing that non-existant property. I am certainly not using UDT's as far as I can tell. Just a single table with a single int PK. I know in the past, according to forum posts, you were testing on Mac. Is that still the case? I ask because Mac will be a very important platform for my project (that and Windows). I hope for parity. Thanks. Kareem
|
|
|
|
|
Hi Kareem, Yes we smoke test major releases with Mono however we have not encountered that problem. That said we do compile the actual test suits under Mono as opposed to copying the assemblies over so perhaps that has an impact. I suspect this may only be a problem if you are using the SqlServer2008 provider even though it may not be being explicitly called as part of what you are doing as we do have checks in there for use of spatial types that require that method to be available. Can you confirm if you are using the 2008 provider option and if you are try switching back to SqlServer2005 and see if that resolves the issue. Using SqlServer2008 as a provider only adds support for automatic translation of spatial types, use of DateTime2 and translation of user UDTs so it doesn't sound like you will be taking advantage of those at this time. Jeremy |
|
|
|
