As a continuation to my earlier post on WEC2013 installation,i like to add some of the troubleshooting tips which will help if there is any error in the installation.Please read the post here.
July 19, 2013
3 Comments »
RSS feed for comments on this post. TrackBack URI
PrabuKumar's WinCE Blog 
What is the workaround for fix for this error: I had recently started working on a Windows Embedded Compact 2013 project in VS2012 Update 3. After installing the VS 2013 preview, On my first attempt to create a simple OS Design I get the following error.
CEBUILD: BUILDMSG: Running sysgen preproc (for COMMON)
C:\WINCE800\public\common\oak\misc\Sources.CE(6) : fatal error U1050: Error: Microsoft.NET Framework v4.x must be installed on your machine. {log=”C:\WINCE800\build.log(68)”}
In my registry, I can see that I have Net Framework v4.5.1 and Net Compact Framework v3.9 installed.
Comment by Robert K Rouse — September 14, 2013 @ 1:52 am
Don’t install Higher version of VS after installing the Platform Builder plugin.It may override some settings which was written by Platform Builder plugin.If you want to use VS2013 use virtual machine.
Comment by Prabu Kumar — September 18, 2013 @ 3:24 pm
Thanks for the article, I am attempting to get started with WEC2013 directly on my new W8.1 machine.
I had ‘issue 2’ occur to me and found that I had to manually install the Application Builder for Windows Embedded Compact 2013 from the installation disk.
I installed my BSP and found it could not build because of the “.NET Framework v4.x must be installed” error, same as the comment from Robert, I worked around this by changing the following files:
to C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\VsDevCmd.bat I added the line: “@set PATH=C:\Windows\Microsoft.NET\Framework\v4.0.30319;%PATH%”
I’m not sure if this next one is really needed but:
to the XXX_bsp.bat file in C:\WINCE800\platform\XXX_BSP I added the line: set _DOTNET40ROOT=C:\Windows\Microsoft.NET\Framework\v4.0.30319
I now can run platform builder and perform a full build and sysgen without getting any errors.
I don’t have a copy of VS2013 to try it out with but since the error seems to be around this .NET framework version issue, I don’t see why you couldn’t run VS2013 in parallel with platform builder VS2012 using this workaround.
Comment by Tom Leijen — December 20, 2013 @ 1:02 am