Twitter: @CEDriverWiz
First in a series of blogs about porting a Compact 7 TI AM335X BSP to Compact 2013 using a SOM and a development board for the SOM as reference hardware for an industrial controller.
The issues get partly resolved.. Please read on. There were some issues with the August update. I posted this: The August update stated that : The Aug 2014 (11.0.50728 & 12.0.30527) release resolves the following issues: · The Debug.Start Debugging option will delete the deployment directory contents. · You cannot deploy a class library to the device if the solution does not contain an executable project. · You cannot specify an external program to execute when run is clicked. ====== · I tested the first point and that hasn’t been fixed · In an existing solution (One console app project and a DLL project on which it depends) if you right click on the DLL project in Solution Explorer, there’s no option to deploy it. Also if there is only a DLL in the solution same applies, so point 2 hasn’t been resolved. The issue in my previous post wrt being able to deploy and debug in other than \Temp hasn’t been resolved. So I suggest that nothing has been resolved. PS 12.0.30527 is the new installe ...
Ever get: "Warning MSB3061: Unable to delete file " message towrds the end of a build, eg: BUILDREL: BUILDMSG: Cleaning up "C:\WINCE800\OSDesigns\OSDesign9\OSDeisgn9\RelDir\VAR_SOM_AM33_ARMV7_Release" C:\WINCE800\public\common\oak\misc\buildrel.proj(495,5): warning MSB3061: Unable to delete file "C:\WINCE800\OSDesigns\OSDesign9\OSDeisgn9\RelDir\VAR_SOM_AM33_ARMV7_Release\proxydriver.dll". The process cannot access the file 'C:\WINCE800\OSDesigns\OSDesign9\OSDeisgn9\RelDir\VAR_SOM_AM33_ARMV7_Release\proxydriver.dll' because it is being used by another process. {log="C:\WINCE800\build.log(40826)"} C:\WINCE800\public\common\oak\misc\buildrel.proj(501,5): error : Error cleaning up flat release directory "C:\WINCE800\OSDesigns\OSDesign9\OSDeisgn9\RelDir\VAR_SOM_AM33_ARMV7_Release". Unable to delete the following file(s) "C:\WINCE800\OSDesigns\OSDesign9\OSDeisgn9\RelDir\VAR_SOM_AM33_ARMV7_Release\proxydriver.dll". ...
"Microsoft has finally joined the mini PC craze, introducing a Windows-compatible development board dubbed Sharks Cove."
Smartdevice projects opened in a Compact 2013 development context are not automatically upgraded to Compact Framework 3.9. This article discusses techniques for upgrading of Smartdevice (Compact 7) projects to the Compact 2013 context (Compact Framework 3.9). This includes comparison of project files as well as use of the CEESharpWiz wizard.
This article discusses the just recently released CECompactTools on Codeplex. This toolset has been morphed from Compact13Tools in that it provides the same shell apps for a Compact 2013 OS using the same C# source code but the Managed code is built directly as an OS Subproject!. That is, unlike Compact13Tools, there is only one software layer.
Command line app to transfer a file over TCPIP.
Microsoft is planning on running a 1 day WEHH 8.1 course for developers. Sometime in June. TBA.
And are trying to work out who is interested. Based on Registration/Expression of Interest, we will lock a date, and run this.
A Wizard, like CEDriverWiz etc, that runs from Tools menu to generate or import a C# Managed Code OS Subproject for Windows Embedded Compact 2013 Projects.
This project is a spin-off from Compact13Tools. Besides the name and URL changes, the Managed Code tools are built directly with OS as Managed Code Subprojects.