ConmanClient not installed correctly

[troy anderson]

I have followed the documented procedure for setting up a debug session with
VS.NET2003 and .NET device by running SDAuthUtil on both PC and device.
However, I get an error on the PC which states that ConManClient could not
be started. I have a PC running XP with VS2003.NET and a X86 processor
running CE.NET 4.2 with Compact Framework built into the OS. When I go to
the device and try to run ConManClient, I get an error saying "Cannot find
ConManClient (or one of its components)..." If I manually copy ConManClient
and its associated DLLs from the directory "Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\ConnectionManager\Target\wce400\x86" onto the
device and run ConManClient, everything works (i.e., I am able to install
and debug my application using VS.NET 2003). However, I would like to
understand what I may be doing incorrectly. Also I would like to simplify
the steps for debugging this application for other developers in our
organization. So could someone provide some clues on what I may be doing
incorrectly in the VS.NET2003 environment?

Thanks

 

[Paul G. Tobey [eMVP]]

I think that you might be missing the SDAuthUtilDevice component in your
CE.NET 4.2. In Platform Builder, this is called "Smart Device
Authentication Utility"...

Paul T.

 

[troy anderson]

Thanks for the quick reply. However, I have this component in my platform
via Platform Builder, this is called "Smart Device Authentication Utility."
In my description I meantioned that I have started SDAuthUtilDevice.exe on
the device and on the PC running VS.NET 2003.

 

[Paul G. Tobey [eMVP]]

So, if you look at the build log from a PB build of the device, does
ConManClient.exe show up as being added to the image? If so, you might go
to the flat release directory and use the depends.exe utility from VS.NET to
look at what ConManClient depends upon and make sure that any dependencies
*are also* being included in the OS build.

Paul T.

 

[troy anderson]

I found out my problem. Platform Builder did not add in the correct EXE for
my processor type after adding "Smart Device Authentication Utility"
component. After I performed a Clean and Rebuild Platform, everything
works.