Hi Jan,
I am trying to use XML::Simple in PerlNET and I am having the following  
error when runnin XMLin ():
could not find ParserDetails.ini in /PerlApp/XML/SAX

Unhandled Exception: System.ApplicationException: Can't locate type  
XML.SAX.PurePerl
    at KikkerInteractive.smsgw.sendsms(String login, String password,  
String msisdn, String tpoa, String sms, String udh, String dcs, String  
sessionid, String ackreply, String refid, String mobilenotif, String  
originatorp, String destinationp)
    at smsgw_test.Class1.Main(String[] args) in  
c:\cygwin\home\severan\projects\vs\smsgw_test\class1.cs:line 20
Unknown signal 79

I have tryed your work around of :
BEGIN
{
	$ENV{HARNESS_ACTIVE} = 1;
}

but the Can't locate type XML.SAX.PurePerl remains...

What is strange is that it does work outside of PerlNET (given I have  
created a dummy ParserDetails.ini file...)

Thanks

Severan

On Wed, 25 Aug 2004 01:33:18 -0700, Jan Dubois <jand@[...].com>   
wrote:

>  On Tue, 24 Aug 2004, Severan Rault wrote:
> > Hi Jan,
> > 	I have actually found the solution to my problem.
> > What I was trying to do is define an interface with a parameter that is
> > any object.
> >
> > =for interface
> > 	[implements KikkerMessageInterface]
> > 	string Execute (Object obj)
> > =cut
> >
> > So that my C# program which uses the perlNET package (which implements  
> > the
> > interface) can pass any sort of things
> > to my perl code, like a DB handler a DataSet ect...
> > I though I needed to cast the Object received from the C# into its  
> > class,
> > but it is actually done for me by PerlNET. (how cool is that :) ).
> 
>  That is exactly what I meant when I wrote that a PerlNET object always
>  represents the actual type of the referenced object and not the abstract
>  typed specified in e.g. the method signature.
> 
>  This is the big advantage of a dynamic language: the same variable can
>  take different types every time the code is executed. And if the code is
>  calling a method on the variable (or passing the object to another
>  function/method), then the method resolution takes the actual type of
>  the variable *at runtime* into consideration to resolve overloaded
>  method definitions.
> 
>  So yes, I agree that it is pretty cool. :)
> 
>  Cheers,
>  -Jan
> 
> 
>  _______________________________________________
>  Perl.NET mailing list
>  Perl.NET@[...].com
>  To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs



-- 
Severan Rault
Technical Director

Kikker Interactive Pte Ltd
hp: +6598173517
_______________________________________________
Perl.NET mailing list
Perl.NET@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs