Hello,
I recently updated my Mono version from 2.4 to 2.4.2.3. After updating I
was not able to load my main ASP.NET project any more. Here is the error:
Server Error in '/' Application
The classes in the module cannot be loaded.
Description: HTTP 500. Error processing request.
Stack Trace:
Sys
I thank you for the hint where to search. I tried for my own and found the
solution. I had to reduce the warning level which
was normally set to 4. Interesting is though why he did throw an exception
but the flag was set to
false.
Thank you.
David das Neves wrote:
> Hey,
>
> I got some proble
On Thu, 2009-09-24 at 14:49 -0700, LKeene wrote:
> Hello, which mono.simd.dll should I reference in my project? I have two
> choices it seems:
>
> 1) C:\Program files (x86)\Mono-2.2\lib\mono\2.0\Mono.SIMD.dll
> 2) C:\Program Files
> (x86)\Mono-2.2\lib\mono\gac\Mono.Simd\2.0.0.0_0738eb9f132ed756/Mo
I have successfully got my .Net Windows Service running under Mono using
mono-service2 on openSUSE 11.1. I created an init.script and start the
service similar to as follows:
/root/mono-devel/bin/mono-service2 --debug -l:/var/run/monotest.pid
-d:/root/monotest monotest.exe
The service starts cor
On Thu, Sep 24, 2009 at 5:49 PM, LKeene wrote:
> Hello, which mono.simd.dll should I reference in my project? I have two
> choices it seems:
>
> 1) C:\Program files (x86)\Mono-2.2\lib\mono\2.0\Mono.SIMD.dll
>
> or
>
> 2) C:\Program Files
> (x86)\Mono-2.2\lib\mono\gac\Mono.Simd\2.0.0.0_0738eb9f132e
Hello, which mono.simd.dll should I reference in my project? I have two
choices it seems:
1) C:\Program files (x86)\Mono-2.2\lib\mono\2.0\Mono.SIMD.dll
or
2) C:\Program Files
(x86)\Mono-2.2\lib\mono\gac\Mono.Simd\2.0.0.0_0738eb9f132ed756/Mono.SIMD.dll
Thanks.
-L
--
View this message in contex
And, to chant the mantra: Patches are always welcome. (Not that I've
ever submitted any, but it begged to be said).
daniel wrote:
> Thats a shame.
>
> It appears from our testing that non compiled xslt is an order of
> magnitude slower then the compiled version. Which for our purposes is to
>
David das Neves wrote:
> Hey,
>
> I got some problems to compile and use my web application with mono. I think
> its an extraordinary problem which is not directly my fault. At least i hope
> so because its working fine with Visual Studio and its Compiler.
> Here is the error & stacktrace:
>
> Se
Hey,
I got some problems to compile and use my web application with mono. I think
its an extraordinary problem which is not directly my fault. At least i hope
so because its working fine with Visual Studio and its Compiler.
Here is the error & stacktrace:
Server Error in '/' Application
/tmp/neve
daniel wrote:
> I see from the msdn documentation that loading by type was added in .net
> 2.0 SP1. So it wasn't in .net 2.0. Which explains why it is missing from
> mono 2.0
Yeah, implementing an XSLT compiler looks like being a rainy Sunday job.
It's still not in Mono because it didn't rain th
Thats a shame.
It appears from our testing that non compiled xslt is an order of
magnitude slower then the compiled version. Which for our purposes is to
slow.
I see from the msdn documentation that loading by type was added in .net
2.0 SP1. So it wasn't in .net 2.0. Which explains why it is m
No browser, just a little desktop application.
So i guess the only way is with a web request and json.
Thanks for your interest and your links. :)
On Thu, Sep 24, 2009 at 3:44 AM, Ben Joldersma wrote:
> Lensman,
> Are you trying to do this in a browser? Or in a desktop or a server
> application
NET XslCompiledTransform has horrible design choice that there is *no*
public API
exposed to make compiled XSLT implementable. There is no choice for us
to implement
it at least from public documentation. We won't support it beyond any
wrapper.
(I feel almost no need to add this comment, but: l
13 matches
Mail list logo
