Hi,
I've looked into it more and found that the PC side does actually connect. Files containing keys are created on the board, there's PubKey.blb and EncodedSessionKey.blb in root and a specific key to my PC name and user name cretated in /Windows/NETCFKEYS. The file conmanclient.exe is also created but it's has a size of 0.

I saw in the utilities readme that this doesn't work with certain types of flash.

Is that the case here or have I set up my image incorrectly for the file system? I ran DelCryptroKey on both the board and my PC as suggested in the readme but nothing changed.

Thanks
Ian

Ian,

We here at Logic have had this up and running, though most of us now run with Platform Builder 4.2. 4.1 Is pretty sketchy and I notice that is what the weblink you posted is covering.

Depending on how you built your original image, you will want to make sure you added all necessary components with a new image creation, and not adding the ccomponents into an existing older image. Sometimes not all the sub-dependencies are copied in if added after the fact. MS's dependency checking is somewhat lacking after the initial image creation is complete.

For more information you might want to check the news groups on Google, under Microsoft.Windows.. There is some really good information posted there. I am sure you have already, but I would run a search on these forums for .NET debugging, as it has come up in the past.

Logic would be happy to walk you through this step by step with a support contract in place. Please see the main support page for more information on this.

http://www.logicpd.com/support

Ian,

Try this link to other messages see if this helps you any.

http://www.logicpd.com/su...hlight=net+debugging


Russellm

Hi,
I'm using Platform Builder 4.2. I'm also using the latest Logic BSP which I'm assuming is the right thing to do. The article referenced was presumably written when 4.1 was the latest and I'm assuming that it is still relevant.

I've been building images from scratch trying to see if any one particular component is missing but obviously so far I haven't found it.

Yes, I've been through the news groups on Google and I have some others that I haven't tried yet. I've seen the link you referenced, it was more to do with getting ActiveSync to work so I skipped it. I'll give it another look.

Thanks
Ian

Ian,

I am not sure if you already have ActiveSync up and running. Are you able to "explore" the CE device while its up and runnning, seeing the file structure using ActiveSync?

The reasons I pose these questions is sometimes the drivers are not easy to get working and can cause fits with getting connectivity between Platform Builder / eVC and the device.

-Russellm

Hi,
I'm using KITL to connect to the device. I don't think I'm using ActiveSync in any way. I can run the image then using the File Viewer put some .NET apps onto the file system and successfully run them.

Ian

Ian,

Yes if your using KITL then you can place files into your release directory, which by default is always mapped onto your device.

However, most of the interactive debugging, with the exception of what KITL provides, is facilitated over ActiveSync.

Try bringing up your system, bringing up ActiveSync, getting that connected and then start debugging your App. I am not sure which features you are trying to specifically use, but there is a good chance that its ActiveSync that needs to be turned on.

-Russellm

OK, I'll give ActiveSync a try. I was specifically wanting to use SDAuthUtilDevice.exe rather than ActiveSync to debug since it didn't require the initial connection to be done via a serial port. Also I saw some note saying that the IP address of the board had to be on a different subnet than ActiveSync for ActiveSync to work. All in all it seemed better and easier to use SDAuthUtilDevice.exe.

You make it sound like I have to use ActiveSync rather than having a choice of ActiveSync or SDAuthUtilDevice. Is that true?

I did try to get ActiveSync to work without success but I didn't try very hard. I'll try again.

Ian

Hi,
I now have SDAuthUtil.exe working under a retail build running from flash. It also has the Logic ethernet driver. If I switch back to running debug from platform builder using KITL as the transport then it doesn't work.

I have no idea why this is but as long as it works on the retail image so we can develop .NET apps with VS then I'm happy.

Thanks
Ian