Accessing Device Properties in VS 2005 SP1 + Vista Fails

[jminiman]

I develop against a CE 4.2 device for the USPS (it's a custom-built
Motorola ruggedized, generic CE 4.2 image). Because WMDC doesn't
support CE 4.2, I've been forced to use Pocket Controller for a lot of
the device operational stuff (this works perfectly since I can go over
any TCP/IP connection). However, VS 2005 has bombed out on me! I was
following the manual-deploy process published here:
http://msdn2.microsoft.com/en-us/library/ms228708(VS.80).aspx

But I must have messed something up, because whenever I try to view
device properties under Pocket PC 2003 or Windows CE 5.0, I get the
following error: "Error retrieving information from user database.
Property not found". I open a new VS 2005 instance (running as
Administrator), click Device Properties, and bam-I get this error.

Has anyone seen this before? I was getting the error on VS 2005 RTM,
then installed SP1 in hopes the error would go away, but it didn't.
I'm hesitant to install the Visual Studio 2005 SP1 for Vista Beta
patch because sometimes VS beta components don't uninstall properly.

Any ideas would be great!

 

[Guest]

I think your CoreCon files got hosed, and the key is to delete the user
copies and let studio regenrate them. I don't recall exactly which file
tree to delete, but with that I think Google will get you there. I know
it's been covered in the archives or a MS blog.

Out of curiosity does this device support USB RNDIS? That what we're
currently using from XP and Vista on a custom CE 5.0 device and it works
quite smoothly.

 

[jminiman]

Chris,

Short of asking the vendor, how can we find out if USB RNDIS is
supported?

 

[Guest]

It will be in the registry. If this exists, you're probably in luck:

[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\RNDIS]

 

[Guest]

Keep in mind that the last key name (RNDIS is this case) is probably not
actually important. In FunctionDrivers it will have a "DefaultClientDriver"
value with the name of the driver to load, which is that key name. Then in
the key it has values which actuall have meaning in the USB world, so it
could be named something like "Foo" and still work for RNDIS as long as it
loaded an RNDIS driver.


--
Chris Tacke - Embedded MVP
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--

It will be in the registry. If this exists, you're probably in luck:

[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\RNDIS]


--
Chris Tacke - Embedded MVP
OpenNETCF Consulting
Managed Code in the Embedded World
www.opennetcf.com
--

Chris,

Short of asking the vendor, how can we find out if USB RNDIS is
supported?

 

[jminiman]

I have nothing in HKLM\Drivers\USB. I have HKLM\Drivers\Builtin with
the following keys:

NDIS, NDisPower, NDISUIO, USB, and a bunch of other unrelated things.
Under USB, I have these name/value pairs:

Dll - bvd_udc_ser.dll
Prefix - USB
Tsp - Unimodem.dll

 

[Guest]

Looks like it's USB serial only.