Hi all,
Trying a new application which has a setting file and which was running fine
on .NET, I got the following exception when running it in Mono:
System.Configuration.ConfigurationErrorsException: Unrecognized attribute
'xsi'. (/root/gwtest/PrivateLife.exe.config line 1)
at
On 20.01.2012 08:18, jaysonp wrote:
Hi Robert,
Again I would make a follow-up regarding my question about $monoprefix
in Windows.
$monoprefix does not exist. It's just a shortcut I'm using in place
of directory where Mono was installed into.
Robert
Hi Robert,
Thanks for the clarification! :)
Here's my setup now:
1. I have a Main mono cert store hosted on a Windows Machine, filled up
with certs already
2. C:\ProgramData\.mono, which is the machine's mono cert store, has
been shared already.
3. I have a new Windows
On 20.01.2012 12:50, jaysonp wrote:
My question is, on the new Windows client machine, how will I map/mount
the shared main mono cert store, in such a way that the client machine will
treat this as its machine mono cert store?
To hopefully clarify, here are some scenarios:
1.
Thank you very much David!
--
View this message in context:
http://mono.1490590.n4.nabble.com/Centralized-MonoStore-tp4268377p4313415.html
Sent from the Mono - Dev mailing list archive at Nabble.com.
___
Mono-devel-list mailing list
Hi,
I want to know more about the algorithm / approach used in monodevelop when
inspecting the value of locals. I find the data inspection in MonoDevelop to
be very peculiar.
Very often the debugger says Evaluating Sometimes observing an integer
local can take many seconds to come
I'm trying to get IKVM working with MonoTouch. That has required a lot
of crazy hackery, but now I'm crashing the AOT compiler, and I don't
think I'm going to be able to fix this one myself (since I don't have
the source). Here's what it reports:
AOT Compilation exited with code 134, command:
On 20.01.2012 20:38, Michael Bayne wrote:
I'm trying to get IKVM working with MonoTouch. That has required a lot
of crazy hackery, but now I'm crashing the AOT compiler, and I don't
think I'm going to be able to fix this one myself (since I don't have
the source). Here's what it reports:
Try
On Fri, Jan 20, 2012 at 11:38 AM, Michael Bayne m...@samskivert.com wrote:
since I don't have the source
I guess this isn't completely true. I can at least look at the mono
source and try to triangulate from there. Based on that, I'm seeing
only two likely callers of
On Fri, Jan 20, 2012 at 12:31 PM, Robert Jordan robe...@gmx.net wrote:
Try to add -v -v -v to the AOT compiler's command line arguments
in MonoDevelop.
Unfortunately that didn't yield any additional output.
BTW, the MonoTouch mailing list is over there:
This seems more like a compiler issue
On 20.01.2012 21:46, Michael Bayne wrote:
On Fri, Jan 20, 2012 at 12:31 PM, Robert Jordanrobe...@gmx.net wrote:
Try to add -v -v -v to the AOT compiler's command line arguments
in MonoDevelop.
Unfortunately that didn't yield any additional output.
BTW, the MonoTouch mailing list is over
On Fri, Jan 20, 2012 at 1:22 PM, Robert Jordan robe...@gmx.net wrote:
It doesn't really matter where the problem is. MT is a commercial,
closed-source product, and its support mailing list isn't mono-devel.
Fair enough. I'm not used to using commercial software. :)
Other than that, you may
Michael Bayne wrote:
(or an issue of IKVM generating funky bytecodes)
Define funky. IKVM.OpenJDK.Core.dll definitely contains things out of the
ordinary, but I'm pretty sure they are legal (as in ECMA CLI specification) and
definitely sure that it passes peverify.
Regards,
Jeroen
13 matches
Mail list logo
