Re: [Visualperl-discuss] FW: Visual Studio ASP.NET web applications using ActivePerl, VisualPerl, and PDK
by Eric Promislow other posts by this author
Jan 19 2005 9:54AM messages near this date
view in the new Beta List Site
RE: [Visualperl-discuss] FW: Visual Studio ASP.NET web applications using ActivePerl, VisualPerl, and PDK
|
RE: [Visualperl-discuss] FW: Visual Studio ASP.NET web applications using ActivePerl, VisualPerl, and PDK
David Christensen wrote:
> Eric Promislow wrote:
>
> >Yes, you need to look at another product, and you asked on the right
> >list, given that you're using Visual Perl. ActiveState's PerlASPX
> >product lets you build ASP.Net applications and web services using
> >Perl code.
>
>
> Thanks for your reply. :-)
>
>
> I downloaded and tried the demo of PerlASPX, but it didn't seem to integrate
> into Visual Studio. Is it supposed to, and I just messed up or was confused?
No, it doesn't integrate into Visual Studio. We haven't yet built an
ASP.Net-aware project for Visual Perl yet either.
>
>
>
> >See http://www.activestate.com/Products/PerlASPX/ for more info.
>
>
> I looked at that web page previously, and couldn't figure out what PerlASPX is
> nor how it differs from VisualPerl, PerlNet, PDK, etc.. I still can't, and I'm
> annoyed at having to register with yet another web site to read a review.
Understood. We don't have the clearance to lift the material off of
DevX's site and republish it ourselves. If you can find a copy of
Perl and the .Net framework (http://www.amazon.com/exec/obidos/ASIN/0130652067,
some used copies there).
>
>
> I'm looking for a product or products that plug in to VS .NET 2003 that provide
> the same level of features and functionality as, say, C# or VB. My first
> objective is building .NET web applications. Later goals include Windows
> applications, console applications, and .msi installable packages. Which AS
> product(s) should I be evaluating?
>
Visual Perl directly helps you build console applications in the VS.Net
environment.
The best way to build Windows applications is to currently use C# or VB.Net
as the front-end language, writing back-end components in Perl. You need
PerlNET from the Perl Dev Kit to compile Perl modules into .Net-aware components.
The Perl Dev Kit also ships with PerlMSI, which lets you write small Perl
scripts to generate MSI packages.
Hope this helps,
Eric Promislow
>
> TIA,
>
> David
_______________________________________________
VisualPerl-discuss mailing list
VisualPerl-discuss@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Thread:
David Christensen
Eric Promislow
David Christensen
Eric Promislow
David Christensen
Matt Herdon
David Christensen
Matt Herdon
Brendan LeFebvre
|