Perl or Powershell

My employee wants to make a system for scheduling SQL queries. The client is a Microsoft bitch, so he asked for something on .NET (they suggested C# and VB). I know a little better, and i proposed perl (we have a good perl team here), and, as an alternative for .NET we suggested Powershell.

Now, the client wants it on Powershell

Am i fucked now?

>>1
by "The client" i mena "The customer".

>>1
>>perl

Now you have 100 problems

Execute a Perl script from within a shell script. Or plain out tell him that his suggestions are not the right tool for the job. Yes, tell him that.

>>3
Not so much. We have strict coding standards and we use lots of testing.

Besides, i never had a serious problem with perl at all, besides keeping "programer creativity" under control, because, you know, the side effect of TIMTOWTDI is unreadability.

>>1
as an alternative for .NET we suggested Powershell.
wat

>>1
If the system documentation to that system is up to scratch, good system abstraction should make any implementation details trivial to complete.

operators vs Enterprise-Commandnames.

>>7
THANK YOU, CAPTAIN OBVIOUS!!! YOU SAVED THE DAY ONCE AGAIN!!!

IHBT

perl > powershell^1000

perl > powershell^1000

>>3
I read that xkcd too

as an alternative for .NET we suggested Powershell
Powershell is .NET in all but name.