Python / Perl / Ruby / PowerShell are great additions to C # / VB.NET. If your boss hands you a text file and says that he inserts it into the database once or twice, then any of Perl / Python / Ruby (I'm not sure about powershell, but I think it's not much more complicated), it should be good to analyze it. Anyway, for your main applications, you're probably stuck in C #. You can use one of the more dynamic languages ββto create C # code.
Since you're in a Microsoft environment, PowerShell is probably your best chance to make your decision. Next to that, I would say IronPython or something else that integrates with the CLR. But the main problem is that for someone else, in order to support what you are doing, they will need to know which language you are using. MS plans to use PowerShell much more in the future, so it's probably easier to justify PowerShell and then say Python / Perl / Ruby.
If you just process the text file for one-time use. Or by creating a generator of one temporary code to generate all the code and then intend to maintain the generated code, then it does not matter. You are the one who will consume the results, and if you save time using Perl, then more energy for you. But if you do something that will be used again and again (for example, an active code generator in which you change the templates and run the generator instead of saving the generated code), then other developers working on what you did should know the language you used . It's much harder to talk about learning Perl / Ruby / Python in the Microsoft store. But PowerShell seems like an easy argument. I think the grandiose plan of MS is that in the end, applications will reveal more opportunities for the shell through command commands. Assuming this happens, PowerShell is even more hassle-free because it will reveal a lot of functionality for scripts that you won't get in any other way.
Cervo source share