fasadreading.blogg.se

1. #Windows ce 6.0 requirements install
2. #Windows ce 6.0 requirements upgrade
3. #Windows ce 6.0 requirements registration
4. #Windows ce 6.0 requirements code
5. #Windows ce 6.0 requirements Pc

#Windows ce 6.0 requirements install

And please remember, install all the packages in flow as mention. But, no need to be upset, I have a copy.:)īeing large in size, I zipped the setup file in small packages for convenient downloading. As I mentioned, VS2005 is already dropped down by Microsoft. If any of Visual Studio 2013/ Visual Studio 2010 / Visual Studio 2008 is already installed on your Desktop, while installing Visual Studio 2005, it is not necessary to uninstall other edition, as each of them are independent of each other. But unfortunately, I will say, "No.!, Visual Studio 2005 is necessory." Also, Visual Studio 2005 Express Edition will not be of use. It sounds good, you may ask me that I have already installed Visual Studio 2013/ Visual Studio 2010/ Visual Studio 2008, can I use it for Windows CE 6.0.

That is to say, the VS2005 is now the development environment for Windows CE 6.0. 7.Unlike the previous versions, the platform builder for Windows Embedded CE 6.0 is no longer independent program but a plug-in in the Visual Studio 2005. If you are too lazy to build your own gensdk32 project, you can download mine from here. "C:\Program Files (x86)\Microsoft Platform Builder\6.00\cepb\IdeVS\ GenSdk32.exe" "C:\WINCE600\OSDesigns\S4WE\S4WE\SDKs\SDK1\obj\BuildSDK1.xml"

Now you can copy and paste the command line of the previous failed gensdk.exe execution and replace it with gensdk32.exe: Go back to your OSDesign and choose “Build\Open release directory”. To build our SDK we have to run gensdk32 from the PB command line. Now you can copy gensdk32.exe to the same directory where gensdk is installed. Now you are ready to build it by choosing “build\build solution” from the VS2005 menu. Select the “Build” tab, choose “Release” as active configuration, and “x86” as Platform Target for your application. We can do that by double clicking on the “Properties” node in Solution Explorer, this will bring up the project properties page: Reg delete "HKCU\SOFTWARE\Classes\Wow6432Node\CLSID\īefore we can build our application we need to configure it as 32bit only.

#Windows ce 6.0 requirements registration

To fix this issue you should execute your command prompt as administrator (right click on cmd.exe or use this "trick" to create an administrative command prompt shortcut on your desktop or start menu) and re-register the vbscript runtime.įirst of all, remove current registration information:

#Windows ce 6.0 requirements code

The first issue I found is an error (2738) when the setup tries to run some vbscript code to complete the installation. You should run all the setup application as an Administrator, so you should give administrator rights to your current user (you may need to do that also to run VS2005) or, at least, right click on the setup executable and choose "Run as administrator". SetupĪs usual the first problems may happen during the tools installation.įirst of all if you have newer releases of Visual Studio currently installed on your development machine you should unistall them and re-install them after you have set-upped VS2005 and Windows CE Plaform Builder. In this post I'll try to report all the issues that I found with my setup and, hopefully, provide solutions (and maybe workarounds) to make Windows CE development possible on 64-bit machines.

#Windows ce 6.0 requirements upgrade

This is an unsupported scenario for Windows CE development tools, so I'm not suggesting that you should upgrade your OS to 64bit if you are happy with your current 32bit setup. On the other side running VS2005 and the Windows CE tools on the "main OS" istead of running them inside the virtual machine will provide better performances and avoid some of the issues of virtualization (limited or wasted disk space, issue with some devices, like USB devices etc.), so I decided to install the tools on Win7-64bit as my main working environment and leave virtual machine for specific configurations. Using a 64bits OS will allow me to use more than 4GB of RAM and this is quite important for me because it will allow me to run multiple virtual machines to test beta products and keep some customers' development environment isolated from the others (for example for customers that need to test and certify each installed QFE and may allow me to install them on my development machine some time after their availability).

#Windows ce 6.0 requirements Pc

I recently bought a new PC and I choosed a machine based on the 64bit version of Windows 7.