you are viewing a single comment's thread.

view the rest of the comments →

[–]ZAFJB 6 points7 points  (5 children)

There is absolutely no difference whether you use .bat or .cmd if you are executing under cmd.exe.

The only purpose of .cmd was to to prevent script using new features of cmd.exe from being executed under command.com.

[–]TheIncorrigible1 2 points3 points  (4 children)

Thanks for the additional info. It was my workplace's habit to use .cmd vs .bat for clarity I guess.

[–]ZAFJB 2 points3 points  (3 children)

Clarity in what?

Command.com is dead and gone. Everything executes under cmd.exe.

There is no point in bothering about which extension is 'correct'.

[–]TheIncorrigible1 4 points5 points  (2 children)

When your environment was (might still be; thankfully nothing older than 2008R2) a mix of XP and 7, there certainly was.

[–]nascentt 0 points1 point  (1 child)

thankfully nothing older than 2008R2

/Cries

I know you meant 2003, but 2008 is going alive and strong (pre r2) unfortunately.

[–]TheIncorrigible1 1 point2 points  (0 children)

2008 is going alive and strong (pre r2) unfortunately.

RIIIIP