The current VMWear player is one of the greatest things Mono has to
boost exploration of Mono. I love it. In fact I love it so much, I
want another!
What about a VMWear player setup with Mono source and SVN so one could
just fire it up, update the source from svn and start contributing?
Hi,
This is now in SVN.
thanks
Zoltan
On 11/2/07, David Miller [EMAIL PROTECTED] wrote:
In current SVN the testsuite gives an abort on sparc because the JIT
generates a branch whose relocation cannot fit.
It's a branch to an exception stub, so the branch is to the end of the
I like the idea of having a debugging session. I am a VS.NET brat and am
struggling with the best way to debug (hunt down issues) and learn some of
the Mono framework. I have created VS.NET solutions for System.Drawing and
System.Windows.Forms so I could browse the source with VS.NET which
On 02/11/2007, Engler, Eric [EMAIL PROTECTED] wrote:
If we could just bundle a micro-mono for Windows into our
distribution, we wouldn't have to worry about testing on two
platforms (mono and MS .net) and the installation package
would be smaller and faster.
Is mkbundle an option? It
Hi Marek,
The attached patch fixes a regression introduced with your last change
to AssemblyResourceLoader.cs.
As the assembly name is encrypted via EncryptAssemblyResource, we
mustn't UrlEncode it anymore.
May I commit?
- Juraj
Index: AssemblyResourceLoader.cs
Thomas Wiest escribió:
Ernesto wrote:
Euan MacInnes wrote:
I would suggest that, rather than one version, Mono should split up
it's packages differently.
I have to agree. If we are talking about a on size fits all Mono
distribution, no version number can be too descriptive.
On Fri, 02 Nov 2007 10:51:17 +0100, Juraj Skripsky [EMAIL PROTECTED]
scribbled:
Hi Marek,
Hey Juraj,
The attached patch fixes a regression introduced with your last change
to AssemblyResourceLoader.cs.
As the assembly name is encrypted via EncryptAssemblyResource, we
mustn't UrlEncode
