CoreCon API - Part V
Last post we looked at how to write a device side agent. I am uploading the source for file viewer written using CoreCon API's.
How to use
- You need to have visual studio 2008 installed in your machine.
- Extract the zip file. It has 2 solutions and 2 xsl files.
- Take a back up of your global datastore directory
- In vista this is "C:\Users\All Users\Microsoft\corecon\1.0"
- In non-vista this is "c:\documents and settings\All users\Application Data\Microsoft\corecon\1.0"
- Copy the xsl files to "addons" directory inside the Global datastore directory.
- Build the solutions. Copy the RemoteAgent.exe to d:\temp\Armv4i directory. If you are keeping the file in different directory then you need to modify the RemoteAgent.xsl file accordingly (modify the RootPath property)
- Execute the FileViewer.exe - you have the fileviewer ready.
I have created the RemoteAgent.xsl package for Armv4i architecture only. If you want to work in any other architecture then you need to build the RemoteAgen.sln in the required architecture. Add a Packagetype entry in the Remoteagent.xsl for that architecture. In case you want to add support for X86, then add the following inside the Packagetypecontainer (in RemoteAgent.xsl)
<PACKAGETYPE Name="x86" ID="x86" Protected="True">
<PROPERTYCONTAINER>
<PROPERTY ID="RemotePath" Protected="True">%CSIDL_WINDOWS%</PROPERTY>
<PROPERTY ID="RootPath" Protected="True">D:\temp\x86</PROPERTY>
<PROPERTY ID="CommandLine" Protected="True"></PROPERTY>
<PROPERTY ID="CPU" Protected="True">x86</PROPERTY>
<PROPERTY ID="Host" Protected="True">RemoteAgent.exe</PROPERTY>
</PROPERTYCONTAINER>
<FILECONTAINER>
<FILE ID="RemoteAgent.exe" />
</FILECONTAINER>
</PACKAGETYPE>
Place the remoteagent.exe built for X86 in D:\temp\X86 directory.
--
Anand R
Comments
Anonymous
December 07, 2007
PingBack from http://msdnrss.thecoderblogs.com/2007/12/07/corecon-api-brought-to-you-by-the-visual-studio-for-devices-team/Anonymous
December 24, 2007
The comment has been removedAnonymous
December 25, 2007
You will not be able to set the transport properties (IP/Port info) using the APIs (at least in the current release). If you want to modify the transport properties you need to do it via Visual studio only. As i mentioned in my post the sample i provided is for ARMV4I only. If you want to use this for x86, you need to have "standard sdk" installed (http://www.microsoft.com/downloads/details.aspx?FamilyID=fe5ca9a9-43d9-46d7-bcbe-9fff174acaf5&displaylang=en). If you build the same project for X86 you should be able to work with the winCE device as well.Anonymous
December 26, 2007
The comment has been removed