Home/ Questions/Q 218599
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T18:46:00+00:00

I would like to write simple scripts in C#. Stuff I would normally use

  • 0

I would like to write simple scripts in C#. Stuff I would normally use .bat or 4NT .btm files for. Copying files, parsing text, asking user input, and so on. Fairly simple but doing this stuff right in a batch file is really hard (no exceptions for example).

I’m familiar with command line “scripting” wrappers like AxScript so that gets me part of the way there. What I’m missing is the easy file-manipulation framework. I want to be able to do cd(“..”), copy(srcFile, destFile) type functionality.

Tools I have tried:

  • NANT, which we use in our build process. Not a good scripting tool. Insanely verbose XML syntax and to add a simple function you must write an extension assembly. Can’t do it inline.

  • PowerShell. Looks great, but I just haven’t been able to switch over to this as my primary shell. Too many differences from 4NT. Whatever I do needs to run from an ordinary command prompt and not require a special shell to run it through. Can PowerShell be used as a script executor?

  • Perl/Python/Ruby. Really hate learning an entirely new language and framework just to do batch file operations. Haven’t been able to dedicate the time I need to do this. Plus, we’re a 99% .NET shop for our toolchain and I really want to leverage our existing experience and codebase.

Are there frameworks out there that are trying to solve this problem of “make a batch file in C#” that you have used?

I want the power of C#/.NET with the immediate-mode type functionality of a typical cmd.exe shell language. Am I alone in wanting something like this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I would try to get over the PowerShell anxiety because it is the shell of the future. All of the software coming out of Microsoft is using it as their management interface and especially version 2.0 is ridiculously useful.

    I’m a C# developer most of the time but PowerShell has solved that whole “WindowsApplication42” problem of temp projects just piling up. PowerShell gives you full access to the .NET framework in a command line shell so even if you don’t know how to do something in PowerShell, you most likely know how to do it in .NET.

    • 0