Connecting Visual Studio IDE to CE 6.0 Target Device with CoreCon

Connecting Visual Studio IDE to CE 6.0 Target Device with CoreCon
Created by on 11/20/2010 10:54:27 PM

CoreCon is used to establish connectivity between Visual Studio 2005/2008 IDE and CE 6.0 target dev... 


Introduction

As part of the process in developing application for a Windows Embedded CE 6.0 (CE 6.0) device using Visual Studio 2005 or 2008, we need to establish connectivity between the Visual Studio IDE and the CE 6.0 device in order to deploy the application for testing and debug.

CoreCon connectivity is one of the available options to establish connectivity between the Visual Studio 2005 (VS2005) and Visual Studio 2008 (VS2008) IDE to a CE 6.0 device.

Note:

For the remainder of this article, Visual Studio is referring to both the Visual Studio 2005 and Visual Studio 2008.

CoreCon Files

CoreCon files needed to establish connectivity between the Visual Studio IDE and CE 6.0 target device are installed to the development workstation as part of the Visual Studio software installation.

CoreCon files supporting multiple processor architectures are installed to the following directory:

\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\

Under the above directory, there are multiple sub-folders.  Each sub-folder contains the CoreCon files to support designated processor architecture, with corresponding folder name, as follow:

\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\Armv4

\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\Armv4i

\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\Mipsii

\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\Mipsii_fp

\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\Mipsiv

\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\Mipsiv_fp

\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\Sh4

\Program Files\Common Files\Microsoft Shared\CoreCon\1.0\Target\wce400\x86

Placing CoreCon Files to the Target Device’s File System

To establish connectivity between the Visual Studio IDE and a CE 6.0 target device using CoreCon, the appropriate CoreCon files must be accessible within the device’s file system. 

There are two methods to place the CoreCon files to the device’s file system:

·         The CoreCon files are copied to the device’s file system after CE 6.0 OS runtime image is launched on the device.

·         The CoreCon files are included to the OSDesign project and compiled as part of the CE 6.0 OS runtime image.

Configure Visual Studio Device Connectivity Settings

To establish connectivity, we need to configure device connectivity settings from the Visual Studio IDE with an application project open.

Prerequisite:

A properly configured CE 6.0 OS runtime image is launched on the target device, with CoreCon files placed to the target device’s file system.  Both the development workstation and CE 6.0 target device are attached to the same Network.

·         With a Visual Studio application project open, select Tools|Options from the Visual Studio IDE to bring up the Options screen.

·         From the Options screen’s left pane, expand the Device Tools node and select the Devices node.

·         On the right pane, select the targeted CE 6.0 device and click on the Properties button to bring up the device properties configuration screen.

·         From the device properties configuration screen, click on the Configure button to bring up the Configure TCP/IP Transport screen.

·         From the Configure TCP/IP Transport screen, select the Use specific IP address option and enter the CE 6.0 target device’s IP address.

Prior to initiating the connection from the Visual Studio IDE, launch the following CoreCon files from the CE 6.0 target device:

·         ConManClient2.exe

·         CMaccept.exe

Note:

CMaccept.exe disable the CE 6.0 target device’s security temporary (for about 2~3 minutes) to allow CoreCon connection to take place.  If connection fails to establish within this time frame, you need to launch CMaccept.exe again to make another connection attempt.

From the Visual Studio IDE, select Tools|Connect to Device to establish CoreCon connection to the CE 6.0 target device.

Depending whether you are using Visual Studio 2005 or Visual Studio 2008, the above steps may vary slightly.

Embedded101 Articles

Click to Expand/Collapse Groups
Skip Navigation Links.
Collapse Windows Embedded Compact (CE)Windows Embedded Compact (CE)
Collapse Compact 7Compact 7
Build A Windows Network Projector wi...
Filter Device Drivers
Asynchronous I/O request support
Configure Flash Storage to Launch Co...
CEDriverWiz V2.00: About this releas...
Installing CEDriverWiz for Visual St...
Collapse CE 6.0CE 6.0
Stream Driver with CEDriverWiz rev 0...
Connecting Visual Studio IDE to CE 6...
Windows CE: Save and Restore the Re...
Windows CE: Stream Interface Driver...
Windows CE: Persisting Registry Chan...
Windows CE: Enhanced BusEnum
Windows CE: Soft Reset
Windows CE: Reading a String from th...
Windows CE: Displaying Disk Informa...
Windows CE: Formatting TFAT
Windows CE: C# Application to Format...
Hive-Based Registry for CE 6.0
AutoLaunch for CE 6.0
Configure Flash Storage to Launch Co...
CEDriverWiz V2.00: About this releas...
Installing CEDriverWiz for Visual St...
Collapse CE 5.0CE 5.0
Configure Flash Storage to Launch Co...
Collapse Platform Builder & OS DesignPlatform Builder & OS Design
Platform Builder: Automatically Flus...
Windows CE: Enhanced BusEnum
Windows CE: Soft Reset
Windows CE: Displaying Disk Informa...
Build A Windows Network Projector wi...
CEDriverWiz V2.00: About this releas...
Installing CEDriverWiz for Visual St...
Collapse BSP, OAL & BootloaderBSP, OAL & Bootloader
Windows CE 6.0: User Mode KernelIoC...
Windows CE: Displaying Disk Informa...
Collapse RegistryRegistry
Platform Builder: Automatically Flus...
Windows CE: Save and Restore the Re...
Windows CE: Stream Interface Driver...
Windows CE: Persisting Registry Chan...
Windows CE: Reading a String from th...
Hive-Based Registry for CE 6.0
Collapse Device DriverDevice Driver
Stream Driver with CEDriverWiz rev 0...
Windows CE: Stream Interface Driver...
Windows CE: Enhanced BusEnum
CEDriverWiz V2.00: About this releas...
Installing CEDriverWiz for Visual St...
Collapse File SystemFile System
Windows CE: Formatting TFAT
Windows CE: C# Application to Format...
Collapse Application DevelopmentApplication Development
Connecting Visual Studio IDE to CE 6...
Windows CE: Persisting Registry Chan...
Windows CE: Reading a String from th...
Windows CE: Formatting TFAT
Windows CE: C# Application to Format...
AutoLaunch for CE 6.0
Windows CE: Stream Interface Driver ...
IBW & ICE
Stream Driver with CEDriverWiz rev 0...
Connecting Visual Studio IDE to CE 6...
Platform Builder: Automatically Flus...
Windows CE: Save and Restore the Re...
Windows CE: Stream Interface Driver...
Windows CE: Persisting Registry Chan...
Windows CE: Enhanced BusEnum
Windows CE: Reading a String from th...
Windows CE: Displaying Disk Informa...
Windows CE: Formatting TFAT
Windows CE: C# Application to Format...
Build A Windows Network Projector wi...
Hive-Based Registry for CE 6.0
AutoLaunch for CE 6.0
Hello all
Filter Device Drivers
Asynchronous I/O request support
Configure Flash Storage to Launch Co...
CEDriverWiz Version 2.00 User Manual
CEDriverWiz V2.00: About this releas...
Installing CEDriverWiz for Visual St...
CEDriverWiz Version 2.00: An Example
CEDriverWiz Version 2.00: Using the ...
Collapse Windows Embedded StandardWindows Embedded Standard
WES7
WES-2009
Windows XP Embedded
Target Designer
Enhanced Write Filter
Collapse NET Compact FrameworkNET Compact Framework
Windows CE: C# Application to Format...
Windows Phone 7
Misc.
Turkish porno izle video site in rokettubeporno izle