PERL Scripts to DOTNET

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Jay Warmack

    #1

    PERL Scripts to DOTNET

    I have some large legacy scripts written in PERL and am looking for a way to
    either convert them to .Net or develope and adapter so that new ASP.Net and
    CSharp components can access the business logic in these scripts. Any
    suggestions for dealing with PERL in a .Net environment?

    Thanks for any suggestions you might have.

    Jay


  • Dino Chiesa [Microsoft]

    #2
    Re: PERL Scripts to DOTNET

    The easiest way I can think of would be to engineer some data interchange.
    Eg, the perl script runs, and its output is placed into an XML file.
    The .NET app runs, and slurps in the XML. The use of XML, of course, is
    irrelevant - you could just as easily use a database, or a csv file, or ...

    If you need it to be concurrent and online, then you need a different
    approach.
    Perl has support for SOAP (client and server), so you could try to install
    the module SOAP::Lite from CPAN. Then expose your perl logic as a
    webservice, and allow C# and the ASP.NET page to invoke the Perl webservice.

    I have used SOAP::Lite as a client, and it's simple and easy. I have not
    used SOAP::Lite in server mode. But I hear that it is simple and easy - you
    can get it running in just 15 minutes or so. One downside is that
    SOAP::Lite is just in beta.



    -----
    side note:
    these approaches apply to any 2 disparate platform technologies.


    -D



    "Jay Warmack" <jwarmack@webla ndingzone.net> wrote in message
    news:OmL67vYqDH A.1488@TK2MSFTN GP12.phx.gbl...[color=blue]
    > I have some large legacy scripts written in PERL and am looking for a way[/color]
    to[color=blue]
    > either convert them to .Net or develope and adapter so that new ASP.Net[/color]
    and[color=blue]
    > CSharp components can access the business logic in these scripts. Any
    > suggestions for dealing with PERL in a .Net environment?
    >
    > Thanks for any suggestions you might have.
    >
    > Jay
    >
    >[/color]


    Comment

    Working...