It’s the little things…

Ever since I started working with console-based WSH scripts, I found the tendency to break input pipes if not launching explicitly with cscript to be a source of frustration and actual damage. A few weeks ago, I started using “shadow scripts”: I would generate a CMD or BAT file with the same base name as a WSF, in the same folder, and give it the one line: @cscript “%~dpn0.wsf” %* Although it was a little annoying to do at first, I found that I was suddenly writing more and more console scripts due to how simple use was. It makes … Continue reading It’s the little things…

Getting a schema for mssecure.xml with “infer”

[Listening to: Mozart – Fur Elise (03:34)] While looking for a way to handle patch management mini-tasks, I ran across the following response by a Microsoft employee to a request for the schema for mssecure.xml (in context, the softie did not sound happy about having to give this kind of answer): Microsoft doesn’t publish the schema for the MSSECURE.XML file. We reserve the right to modify, change and update the schema as necessary to enhance products that rely on and use the MSSECURE.XML file. That’s not precisely true. Microsoft does publish a schema, an implicit one. What people tend to … Continue reading Getting a schema for mssecure.xml with “infer”

.NET and Console Tools – We’re Getting There, But…

[Listening to: We Have Explosive – The Future Sound of London – We Have Explosive (03:26)] I’ve been going through Visual Basic .NET 2003 Resource Kit this morning, looking for goodies I can reuse elsewhere. One of the “metrics” I use is how good console tool support is. Strictly speaking, this is not a VB issue, it is a .NET issue, and I’m finding myself wandering off to think about the whole issue of console tool support as a concept in Windows systems. The real underlying problem is not one of what classes are available here and there for console … Continue reading .NET and Console Tools – We’re Getting There, But…