VS 2012 (with Update 3) screws up .cmd files containing batch scripts

This may not be specific to Update 3 or VS 2012. I noticed that if you edit a .cmd file containing batch commands in Visual Studio, it adds garbage to the first line of the file.

The execution of the scripts will fail because of this.

Hence use notepad for this.

Comments

Popular posts from this blog

Tutorial: Using Google Cloud Storage from C# and .NET

Late 2008 Macbook only giving 1.5 gb/s speed with 6 gb/s Intel SSD?

Enable Visual Studio to use more than 2GB of memory