Re: [Ikvm-developers] Extension Method for System.Extention.printStackTrace() not found

[Ryan T. <rya...@ho...>]

Saxon is still low, and I figured out why the XSLT was broken, but it seems that I was missing my coffee this morning as I know extension methods are .net 3.5, yet I expected them to work with 2.0 :|
My bad.
I did find my answer when I upgraded the unit tests to 3.5 just to get my answer.
Cheers.

Ryan Ternier
 
 

Subject: Re: [Ikvm-developers] Extension Method for System.Extention.printStackTrace() not found
From: mi...@sa...
Date: Wed, 14 Aug 2013 00:30:55 +0100
CC: je...@su...; ikv...@li...
To: rya...@ho...


On 13 Aug 2013, at 19:43, Ryan Ternier wrote:Unfortunately, some applications are not able to be upgraded, especially enterprise healthcare applications. So yes, it's a 2005 compiler. Drop the attitude please.

I think you misread what Jeroen said. He made a purely factual statement to correct your assertion that 7.1 was the latest version; I don't think he was passing judgement in any way.
Saxon, for what it's worth, is still using something like 0.46.x.x. Need to check the details, that's from memory. We hit some trivial problem last time we tried to move forward, and stuck with what worked because we had no real reason to upgrade in the first place. Many Saxon users also stick with old versions of Saxon. It's frustrating to us when they hit a support issue, but I can well understand why they do it.
Sorry, I don't know the answer to your question.
Michael KaySaxonica