On 04/12/2013 20:24, Roger Massey wrote: > Here is a link [2] to a zip file with a windows netconfigexe. (The . > is missing to make the mailer happy). If you have a windows machine > run netconfig.exe on it. It should output a json string that > describes > the machines network config. > > You could verify the json is legal on web validators (jsonlint, ...) > or post the string to the list. > > If you have visual studio c# 2010 the source code is also in the zip > and comments to the list are welcome. > > It is my first c# program so be gentle. > > Roger > > PS. I never could get the exe and/or zip through the mailer. > > > Links: > ------ > [1] https://dl.dropboxusercontent.com/u/17774745/netconfig.zip > > _______________________________________________ > Assimilation mailing list - Discovery-Driven Monitoring > [email protected] > > http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation > http://assimmon.org/
The program is very well written. The only question I have is whether all the use of com interop and struct packing is necessary? Are there really no .NET interfaces in either management or other namespaces which provides this information? It seems like the System.Net.NetworkInformation namespace may be some help here. If the program works as it needs to I'm all up for keeping it the way it is but from experience I know the second you start using pInvoke or COM interop in a c# application it makes maintenance of the program harder and spinning up other people to work on it harder as well. Dave _______________________________________________ Assimilation mailing list - Discovery-Driven Monitoring [email protected] http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation http://assimmon.org/
