Has anyone tried the Windows Mobile 6 SDK
http://www.microsoft.com/downloads/...3A-A651-4745-88EF-3D48091A390B&displaylang=en
Have yet to download it myself, but I believed with this and the KITL mode we could compile a new crossbow rom? Maybe we could then use this core in the XDA-Live version?
Maybe anyone who knows about this stuff can give his reaction, I'm just thinking out loud.
man, d/l speed is slow.
I think you will find that the SDK is only for developing applications that run within the OS, not for creating images of the OS. This was the case for the mobile 5 sdk it allows developers to use the new cf.net framework. The 6 SDK includes the new namespaces including the updated system namespace and the new xbox namespace, as well as the new emulators.
Related
i need the software to run some program if anyone can send that or any links to download thanks
Hi,
The SDK for Pocket PC is actually available for free at Microsoft!
You just have to search a little for it: use "Pocket PC SDK 2002" as keywords at www.microsoft.com, or try this direct link:
http://www.microsoft.com/downloads/...4a-bd94-4167-b817-2b2e548b2e92&DisplayLang=en
The SDK for Pocket PC 2003 only includes VC++ 4.0, but the SDK for Pocket PC 2002 contains both VCC++ 3.0 and Visual Basic CE 3.0.
For VB Apps to run, you need to install the VBRUN-Runtime library on the PDA.
Be aware that embedded VB has some severe drawbacks, compared to VB6:
- you don't have the DoEvent command, so no "multitasking"
- you don't have VAR() and VAL()
- you don't have many of the controls
- it is VERY slow
More info's about it:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbceide/htm/evbstart.asp
Cheers,
vma
VBRuntime.cab
VBRuntime.cab
Note that it is better to write your apps in Visual C++ rather than VB, as VB will not be supported on future devices...
eMbedded Visual Basic can run on WM 2003, just use the following link to download the runtime library from the following link:
http://msdn.microsoft.com/mobility/windowsmobile/downloads/evb_eula.aspx
This will allow any applications written using eVB 3 to run on your device!
I'm going to start with why, then how.
Why: I use the open source SharpDevelop to write Windows Mobile .NET applications. Some of the managed libraries that are included in Windows Mobile are not usable without the Windows Mobile SDK files. Microsoft's SDK Installer checks for Visual Studio, and if it not installed, will NOT install the SDK.
How: Download the SDK, open a command prompt, cd to where the SDK was downloaded to and type (making appropriate changes):
Code:
msiexec /a "MSI File.msi" /qb TARGETDIR="Full path to target directory"
For example, lets say that the file is called "WM6 SDK.msi" (which it is not), you downloaded it to "C:\WM SDKs\" and you want to extract it to "C:\WM SDKs\WM6 SDK\", you would type:
Code:
cd C:\WM SDKs
msiexec /a "WM6 SDK.msi" /qb TARGETDIR="C:\WM SDKs\WM6 SDK\"
The DLLs you need to add a references in your project will be under a folder called Designtimereferences
Anyone find this useful?
heyy thanks i found this useful...havent tried it yet, but didnt wanna go about downloading and installing VS if i dont want/need to
thanks man
hasseye said:
heyy thanks i found this useful...havent tried it yet, but didnt wanna go about downloading and installing VS if i dont want/need to
thanks man
Click to expand...
Click to collapse
No problem ... Thanks for the feedback.
cool!
Ultracool Man!
thanks for sharing the information .... no doubt it is useful to alot
Interesting! Anyone know if this enables the SDK to work with Visual Studio Express?
FloatingFatMan said:
Interesting! Anyone know if this enables the SDK to work with Visual Studio Express?
Click to expand...
Click to collapse
I doubt it ... I use SharpDevelop. I have a legal copy of Visual Studio 2003 + 2005, but I use SharpDevelop.
SharpDevelop
Does sharp develop support Compact Framework 3.5?
What are some advantages to using this?
I normally develop with visual Studio 2008 Professional with the Window Mobile 6 SDK.
Wish I would have know about this sooner.
2008 Standard does not support windows mobile development and pro was kind of spendy.
2005 standard supports it.
<slight rant>
Why microsoft? Why would you require pro to make apps, when you need to gain market share. The other platforms are growing because of the availabilty of apps.
</slight rant>
Sharp Develop DOES support CF 3.5, but you need to install .NET CF 3.5 and .NET CF 3.5 Power Toys on the PC to use it ... See Compact Framework on SharpDevelop Wiki.
Hi, do you know if is there any version of gcc ported of windows mobile?
My idea is to develop apps directly on the phone. do you know if is there any package, sdk, etc, to develop ON the phone? (like m-shell for Symbian device, if you know it)
Thank you very much
gygabyte017 said:
Hi, do you know if is there any version of gcc ported of windows mobile?
My idea is to develop apps directly on the phone. do you know if is there any package, sdk, etc, to develop ON the phone? (like m-shell for Symbian device, if you know it)
Thank you very much
Click to expand...
Click to collapse
As mentioned on the WIKI page, there is Pocket GCC at http://sourceforge.net/projects/pocketgcc/files/
The project has been inactive for a long time, but I have used it on an older Pocket PC and was able to compile some programs.
Also see info here: http://mamaich.uni.cc/. Click on "Old Site" and then "Pocket PC".
I need to write an app to run on Windows CE .net 4.2. I would like to get platform builder for Windows CE .net 4.2, but it doesn't seem to be available on the microsoft site. Can someone help me find it?
It is not the .net that was 4.2, it was the version of CE. This appeared as WM 2003 and WM 2003 SE. The .NET compact framework for the machines was 1.0 or 1.1.
To test the app in an emulator use the standalone emulator. Now at version 3.0
http://www.microsoft.com/downloads/...AF-12E3-4B2F-A394-356E2C2FB114&displaylang=en
The WM 2003 SE images for it are here
http://www.microsoft.com/downloads/...b5-f2a2-47d7-a41d-825fd68ebb6c&displaylang=en
To write .net 1.0 and 1.1 WM apps you will need VS2003 PRO.
VS 2005 and VS 2008 can be forced to create .net 1.0/1.1 executable images but it's a total pain in the ...., you have to hack the build files to get it to work.
For C++ Win32, AFC or MFC you can use the free version of EVC 4.0
http://www.microsoft.com/downloads/...3D-50D1-41B2-A107-FA75AE960856&displaylang=en
Dont forget to apply SP4 to it after install. (Same page, use the link at the bottom)
Thank you very much for the help!
How about modifying the BSP or kernel, which version of tool would you use for that?
For that you will require the CE 4.2 Platform Builder package. Microsoft pull superceded versions off their site, the current version is for CE 6.0
The evaluation version works fully for six months then you have to licence it.
Search in Google for "CE Platform Builder 4.2". Some non Microsoft sites may have a copy of it, but some of these sites could also be of a rather dubious nature. i.e warez peer-to peer file sharing etc.
The documentation for it can be found here
http://msdn.microsoft.com/en-us/library/bb851528(v=MSDN.10).aspx
actually that's what the guy asked for in the first post
Hallo,
I have the question, if VB (not the sdk, only a program) could run on WM 6.5? I know there is a eMbedded runtime, to use VB, but only for the Version WM 3 ... Does anybody know, if VB program run also with these eMbedded runtime and WM 6.5?
Thanks und regards,
Flo
If the program has been written in VB .NET Compact Framework (Visual Studio 2002 onwards), then it should run on your device, without the need for a runtime, as the .NET CF is the 'runtime' for the program. All mobile devices have one version of .NET CF installed in rom on the device. Later versions can be installed. Even if the program was written for an earlier version of .NET CF than that on your device, if the device can JIT compile it successfully against the version installed then it will run. If serious differences exist between the methods used in the program's CF version and the device, then it will report that you will need a later version installing.
The moral of the story here, is keep your app as 'simple' as possible, and it increases the range of devices on which it will run.
A 'runtime' version of VB was used in Embedded Tools Version 3.0 (VB and EVC 3.0), before EVC 4.0 replaced it. It is no longer on Microsoft's website but other copies of it exist on the web if you search for it.
There is no reason why a program written in Embedded Tools 3.0 should not run on WinMo 6.5, though some of the dll 'import' definitions may be getting a bit long in the tooth. Like a lot of previous development environments, it's just been dumped at the side of the road.