Martin Spedding's Blog

Adventures in a disconnected world

May 2003 - Posts

Learning WMI - useful downloads, importance of Google

I was trying to learn more about WMI for a project I am working on so I typed in a Google query and up poped this url. http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=9ef05cbd-c1c5-41e7-9da8-212c414a7ab0

Once you have downloaded the tool and installed it, you have a ready collection of useful WMI scripts with appropriate names. It has meant I have been able to get up to speed with WMI. All the examples are in vbscript but once you know how the calls look you apply your new found knowledge to .Net

As a side note I have been reading the interesting blog discussions about the influence and future of Google and have to say it really is an essential part of my development toolkit. Code examples and solving support calls (Google or groups.google.com), images for presentations (image search on Google). Like many others I seem to be using an RSS aggregator and Google rather than random surfing. 

Interesting inconsistency in the framework
I am curious why does System.AppDomain.CurrentDomain.BaseDirectory return L:\Documents and Settings\Martin\My Documents\Visual Studio Projects\MJSUtilities\testPipeline\bin\Debug and System.IO.Path.GetTempPath() return L:\DOCUME~1\Martin\LOCALS~1\Temp\ What I don't understand is why System.IO.Path.GetTempPath() returns an 8.3 format directory path whilst System.AppDomain.CurrentDomain.BaseDirectory returns correctly a long name format directory path. I am developing on Windows XP so I would not have expected this result. As I said I am curious, why does this inconsistency exist ?
More Posts