Learning the nuances of Visual Studio

I’m starting to use Visual Studio and programming more and more in C#. Mostly this is because I’m finding that creating tools with scripts for my end users to be too cumbersome for them to use. PowerShell scripts are not easily launched by a double click, you need to allow scripts in the first place (set-executionpolicy) and I can’t even trust that the computer has PowerShell installed! Batch files, while supported by pretty much any Windows version would need to be overly complicated or the batch language just doesn’t support what needs to be done.

On top of these limitations, I also need the tools to be able to stand alone, one file to download and one to run. Which is something that scripts just can’t always provide since there are just too many variables in getting them to run. Executables on the other hand can be compiled so that everything it needs, it has. Something of which is a feature I need so that my users have only one thing to worry about.

You can leave a response, or trackback from your own site.

Leave a Reply