Your boss would make about as much sense if he wanted you to move to Eclipse for family reasons and other reasons associated with the Dow Jones Industrial average. There's a fat non sequitur or two hiding in there somewhere.
I'm fairly experienced with .NET and Perl, so:
Using Visual Studio.NET isn't going to help you build code that creates SQL/DDL any better than Emacs/vim will. VS.N does offer some nifty tools for creating queries, stored procedures, etc., but doesn't offer squat in the way of creating code that will let you 'burn' databases. Using ADO.NET might give you better performance than using DBI, but that's probably not going to matter unless you are creating hundreds of databases at the same time.
VS.N has about as much to do with security as Notepad does. The .NET platform (which is not the same thing as VS.N) does have some spiffy APIs for users/groups/permissions which makes it easier to code securely (if you even know HOW to code securily), but there's precious little about .NET that makes it inherently more secure than Perl or even Java.
I don't have a whole lot bad to say about .NET. I just know that its still alot easier to do most things w/Perl, at least for me. I've never tried the .NET version of Perl ($295!) but I have read positive things about it.
It sounds to me like your boss just thinks that .NET is just somehow 'cooler' or more buzzword-compliant. And that eventually he/she will want you to code with C# or (be very afraid!) VB.NET.
In reply to Re: VisualStudio.Net and Perl
by Art_XIV
in thread VisualStudio.Net and Perl
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |