There??™s one tip for each week of the year. As you continue working at the command
line, build batch files and scripts, and discover new commands and utilities that Microsoft
has hidden there, you??™ll discover just how much of a resource the command line can be. Now
that I??™ve shared my tips with you, I??™d love to hear about any tips you might have. Write me at
JMueller@mwt.net
to share them with me.
1.
Always test new scripts and batch files using a test machine. Verify that the script or batch
file works as anticipated before you test it on production machines. Even after you test scripts
and batch files, provide additional monitoring while the script or batch file is new to allow
potential bugs to surface.
2.
Consider learning to use batch files for automation before you move on to scripts. Many
automation tasks don??™t require scripts to succeed. Batch files are a very simple and easily
understood way to add automation to the command line.
3.
Third-party utilities are a tempting way to make the command line more accessible. However,
it??™s usually a better idea to determine whether Windows provides a command or utility
to accomplish the task first.
Pages:
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332