Lori Pike writes "If you've chosen Microsoft's Visual Studio as your development framework, you can now add Perl to the list of fully-supported languages. Visual Perl is the new Perl plug-in for Visual Studio .NET, featuring a powerful array of Perl-specific features within the familiar Visual Studio environment."
Read on for more details about this May 9th webcast.
Lori continues:
Join ActiveState for a free webcast where you'll learn how to use Visual Perl to:
Increase your productivity with the full-featured editor
Produce higher-quality code with the Perl-aware debugger
Master regular expressions with the unique Rx Toolkit
Find and consume Web services in Perl
Date: May 9, 2002
Time: 10:00 AM PDT
Location: Online
Duration: 45 minutes
For more info or to register, click here.
In case you're interested
djberg96 on 2002-04-30T13:18:32
I've actually tried this using a demo of Visual Perl and Beta 2 of the
.NET framework (including Visual Studio).
While I'm no fan of Microsoft, this piece of software is hands down the best IDE for Perl that I've ever seen. Very slick interface with all the bells and whistles. Debugger, watch variables, variable inspection, code folding and even version control. The works.
If you're doing Perl in a Windows environment and .NET is something your company is into, this is the tool for you (assuming you can afford it).
VS.NET VC
lachoy on 2002-05-02T19:28:38
Did you use any sort of CVS plugin for the Visual Studio .NET version control? We've been poking around for this with minimal luck.
Re:VS.NET VC
djberg96 on 2002-05-02T20:11:29
Actually, I didn't have any luck with the version control, but then I thought that was something that would be worked out by the time the official release came out (I was using Beta 2).
I *suspect* they're going to try and drive folks to their propietary versioning system (SourceSafe I think its called).
Re:VS.NET VC
lachoy on 2002-05-02T21:28:29
You suspect correctly: Visual SourceSafe is the supported VC mechanism. There is a Source Code Control API for both VS.NET and VS6, but you can only use one type of version control at a time -- to work on CVS projects and VSS project you'd need to change registry settings or something. Blech. (Plus the CVS integration wasn't very good anyway, apparently.)
Welcome, if not for me...
MeerCat on 2002-05-01T21:26:26
I welcome AS's effort in doing this, as in many people's eyes it legitimises Perl on Win32 (if not in general).
Unfortunately, I think the MS IDE is particularly poor at being anything like a professional development environment - I spend plenty of time trying to wean my C++ developers off the VC++ IDE if only to open their eyes to how there are better ways to do things, integrate with other tools, use open rather than closed toolsets, to be aware of what they do rather than rely on wizards and similar... in short to spend more time making their intent clear in the code they write (which is what other developers have to read), rather than making their intent clear to an IDE which takes delight in doing what they want, but recording only the obscure end result. Sort of like a compiler that writes the object file but deletes the source code...
Of course, if AS can take this a chance to turn Perl into a competitor in the VB market (ie simple drag'n'drop of GUI design and hooking up handlers) then I think Perl could revolutionise GUI prototyping and "small-GUI" apps in the same way that it made such a huge impact on the "text-and-file manipulation" area. I recently prototyped a custom 3 tier global system in perl, but the (thick) client had to be done in VB to get all the work done in a reasonable timescale (using PerlCOM to let VB call the Perl communications layer) - if I could have written the GUI mock-up in Perl too I think I could have done a much better prototype much quicker, but the Tk and Win32::GUI modules need some visual tools...
--
T
