Advertisement

02.11.2008 at 07:21AM PST, ID: 23153171
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.4

Help formulating a more specific WMI query, not using a collection

Asked by jjthomas3 in Microsoft Visual Basic.Net

Tags:

When programming in WMI one typicall performs a WMI Query like "Select * from Win32_BIOS". The return is typically loaded into a collection and then we loop through the collection in a statement something along the lines of "For each objItem in wmiCollection".  The properties would then become (in the case of the BIOS serial number) objItem.SerialNumber.

I'd like to query specific information and assign it directly to a variable with out needlessly looping through a collection of properties I am going to discard anyway. Is there a way to skip the whole collection assignment / For/ Next loop ?

The code I am using looks like this (straight from the WMI Code Generation tool from M$)

             Try
                Dim connection As New ConnectionOptions
                connection.Username = userNameBox.Text
                connection.Password = passwordBox.Text
                connection.Authority = "ntlmdomain:DOMAIN"

                Dim scope As New ManagementScope( _
                    "\\FullComputerName\root\CIMV2", connection)
                scope.Connect()

                Dim query As New ObjectQuery( _
                    "SELECT * FROM Win32_BIOS")

                Dim searcher As New ManagementObjectSearcher(scope, query)

                For Each queryObj As ManagementObject In searcher.Get()

                    Console.WriteLine("-----------------------------------")
                    Console.WriteLine("Win32_BIOS instance")
                    Console.WriteLine("-----------------------------------")
                    Console.WriteLine("SerialNumber: {0}", queryObj("SerialNumber"))

                Next
                Close()
            Catch err As ManagementException
                MessageBox.Show("An error occurred while querying for WMI data: " & err.Message)
            Catch unauthorizedErr As System.UnauthorizedAccessException

                MessageBox.Show("Connection error (user name or password might be incorrect): " & unauthorizedErr.Message)
            End Try

 What I'd like to do is ditch the whole For Next loop and assign my end result directly to a variable;  Where the Query would be "SELECT SerialNumber from Win32BIOS"..... I'm creating a XML Driven routine and am only after exacting properties.

I'm VERY new to VB.NET. And even newer to trying to work with WMI through VB.NET.Start Free Trial
 
 
[+][-]02.11.2008 at 10:15AM PST, ID: 20868676

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]02.11.2008 at 11:49AM PST, ID: 20869533

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]02.11.2008 at 11:54AM PST, ID: 20869590

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]02.12.2008 at 05:48AM PST, ID: 20874624

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zone: Microsoft Visual Basic.Net
Tags: VB.NET
Sign Up Now!
Solution Provided By: graye
Participating Experts: 2
Solution Grade: A
 
 
[+][-]02.12.2008 at 06:20AM PST, ID: 20874895

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 7-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]02.12.2008 at 03:05PM PST, ID: 20880185

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 7-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32 / EE_QW_2_20070628