471,356 Members | 1,641 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,356 software developers and data experts.

WMIC issue when upgrading to dotnet 2.0

Hi,

I'm developing software for a USB device with an FTDI chip. The
device is recognized through WMIC queries. When porting an
application from Visual Studio 2003, to 2005 it seems to work
perfectly on the machine I'm developing it on, however on some
machines, it simply does not recognize the USB device. On these
machines the 2003 version works exactly as expected, but not with the
2005 version. It is puzzling because this only happens on some
machines, (the machines developing on works completely normally...).
I have done windows updates, and installed both .net 1.1 and 2.0 on
the target machine with no luck. I'm sure that the device driver is
installed too.

I've tried nearly everything I can think of to fix the issue, and am
looking for some ideas, regardless of how far fetched they are. Any
idea, solution, or new way of looking at the problem would be
appreciated...

Thanks,

-Ken
Jun 27 '08 #1
1 1244
<km******@gmail.comwrote in message
news:a9**********************************@j22g2000 hsf.googlegroups.com...
Hi,

I'm developing software for a USB device with an FTDI chip. The
device is recognized through WMIC queries. When porting an
application from Visual Studio 2003, to 2005 it seems to work
perfectly on the machine I'm developing it on, however on some
machines, it simply does not recognize the USB device. On these
machines the 2003 version works exactly as expected, but not with the
2005 version. It is puzzling because this only happens on some
machines, (the machines developing on works completely normally...).
I have done windows updates, and installed both .net 1.1 and 2.0 on
the target machine with no luck. I'm sure that the device driver is
installed too.

I've tried nearly everything I can think of to fix the issue, and am
looking for some ideas, regardless of how far fetched they are. Any
idea, solution, or new way of looking at the problem would be
appreciated...

Thanks,

-Ken


WMIC is a command line utility, I don't see how you are using it from .NET
nor do I see what the version of VS has to do with this.
Please be more specific.

Willy.

Jun 27 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.