Hi,
I've been using emBedded visual C++ for 2-3 years writing application for pocket PC ( Mainly Ipaq'a).
I've recentrly invested in a Xda but when I attempt to "update my remote output file" from with embedded VC ++" i get the following error:
" Microsoft Active sync connection server failed, Please make sure active sync is running and retry the download etc.."
Of course Activate sync is running, and running correctly, Has anyone had this issue before ?
I can manually copy my executable to my device and run it,but then I can't debug. I'm in the process of download VC 4.0 and going to try that, but really wold like to runing in under the 3.0 version.
Any comments would be appreicated.
Bad news dude, eVC++ works only with PocketPC 2000 + 2002. The development environment you'll need to develop on 2003+ is either eVC++ 4.0 or Microsoft Visual Studio.NET.
Thanks for the update,
I've installed Embedded VC 4.0 and the SP3, Now I can download to my XDA which is great.
Now I want to maintain backwards compatiable and download to my ipaqs in 2002, I can't change the actiive configuration to PPC2002
Is there a way to compile my application for both 2002 and 2003 using VC 4.0 or do I need to maintain both IDE's
Sorry but there's no way to maintain both 2K2 and 2K3 targets from eVC 4. You can have the same set of source code but eVC 3 + 4 have different project file types. Have a project per IDE containing the same source code. Just remember when you add files to the project you're working on, remember to add the files to the other platform's project as well.
Happy coding!
-Timbo.
Related
I've tried to install .NET CF v2 on my Qtek 9000. (NETCFSetupv2.msi) . It gives me "Application manager cannot install this application on your mobile device due to an invalid setup file. Reinstall and try again". Did anybody manage to install .NET CF v2 ?
I had real troubles with this! I asked a friedn at Microsoft and his advice was to check that ANY .NET files that had been installed were DELETED before trying again. When an install fails on this it leaves asome bits hanging around and then the next try fails!
I cleaned any .NET stuff off, installed again and WOOHOO it worked!
It doesn't works. I found the damn thing (netcfagl1_0.dll) in the Windows folder. I was able only to see it (could not copy or move it, (even tried to change properties with Total Commander CE)). The file still remains "protected". Strangely I can't see it with "Explore PocketPC" from ActiveSync even with "Show hidden files and folders" and with "Hide protected operating system files" unselected.
YOOHOO!! I did it!
I found an article and bang! http://pluralsight.com/blogs/jimw/archive/2005/10/12/15504.aspx
I’ve wanted to get this post out for a couple of weeks but I guess better late then never.
A lot of you may have heard of the great Pocket PC device offer that was announced at PDC. At the event, Microsoft was subsidizing the sale of a limited number of iMate Jasjar Pocket PC Phone Edition devices at a remarkably discounted price of US$149. This price represents a more then 85% discount off of the list price of US$1,180.
The iMate Jasjar is quite cool because it has a high-resolution display (640 x 480) that can be viewed in both landscape and portrait. It also has a QWERTY keyboard, WiFi, Bluetooth, GPRS phone, 520MHz processor and has two, count ‘em, two cameras. And what makes it especially cool is that runs Windows Mobile 5.0 so it supports all of the latest Windows Mobile 5.0 managed APIs. Basically it’s a pretty cool device offering all the latest and greatest features. (see pictures)
Since PDC is a developer event, many of the folks who were lucky enough to successfully purchase one of the Jasjar devices wanted to try using Visual Studio 2005 to build a .NET CF 2.0 app and run it on their new device. For the people who didn’t have device experience, successfully building their first WM 5.0/.NET CF 2.0 app required a little more housekeeping to get started then they realized.
What I’d like to go over in this post is two of the more common issues I saw people encounter in trying to build their first .NET CF 2.0/Windows Mobile 5.0 application and run it on a real device.
Visual Studio 2005 doesn’t support Windows Mobile 5.0 out of the box.
As bizarre as this may sound its true. When you install Visual Studio 2005 it automatically installs .NET CF 2.0 along with the Pocket PC 2003 SE and Smartphone 2003 SE SDKs. It does not install the Windows Mobile 5.0 SDK. As a result you can’t build applications that take advantage of the Windows Mobile 5.0 APIs. To do so requires that you download and install the Windows Mobile 5.0 SDK for Pocket PC and/or the Windows Mobile 5.0 SDK for Smartphone. Once those SDKs are installed you can build Windows Mobile 5.0 projects that can access the Windows Mobile 5.0 managed libraries. If you install both of the 5.0 SDKs you’ll also add about 10 more emulators representing the various Windows Mobile 5.0 device form factors.
The absence of Windows Mobile 5.0 from Visual Studio 2005 isn’t a pre-release issue. Last I heard, it’s very unlikely that that the Windows Mobile 5.0 SDKs will be included in the RTM version of Visual Studio 2005 either. I’ve never heard an official reason for why the SDKs aren’t included but the prevailing theory is their size. Apparently the combined size of the two SDKs is large enough that if included, the Visual Studio 2005 install would no longer fit on a single DVD which would of course significantly complicate the production and distribution. Again just a theory, but if its true leaving the 5.0 SDKs as separate downloads does make sense.
Running a .NET CF 2.0 application on a WM 5.0 device, throws an exception indicating that a newer version of .NET CF is required.
There are actually two issues at work here. First, Windows Mobile 5.0 devices ship with .NET CF 1.0 SP3 installed in ROM, not .NET CF 2.0 therefore before a .NET CF 2.0 app can be launched .NET CF 2.0 must be installed. When Visual Studio 2005 would push the .NET CF 2.0 CAB file down to the device and attempt to initiate the CAB install onto the device, the installation of .NET CF 2.0 fails because of the new WM 5.0 security model.
As many of you probably know, one of the big changes in Pocket PC 5.0 was the addition of the one-tier security model (as opposed to the two-tier model on Smartphone 5.0). One of the features of the new security model is that remote actions performed on the device by the desktop can be restricted. In the case of the Beta 2 or pre-September CTP versions of .NET CF 2.0, the CAB file is signed by a test certificate that is not recognized by the Pocket PC 5.0 device. As a result,the remote installation fails.
The best way to eliminate this problem is to upgrade your Visual Studio 2005 installation to either RC1 or to a September or later CTP. In these newer versions of Visual Studio 2005, the .NET CF 2.0 CAB file is signed by a properly trusted cert and therefore installs fine. If you don’t have access to a newer version of Visual Studio 2005 you can still get around the installation problem by using either the Mobile Device folder on My Computer or the ActiveSync Explore feature to manually copy the .NET CF 2.0 CAB file1 down to the device. Once you’ve copied the CAB file down to the Pocket PC you can then use the File Explorer on the Pocket PC to launch the CAB file manually by just tapping on the file name. Now the CAB is still signed by an unknown cert but because you’re launching the installation interactively you are simply prompted with a warning indicating that the signer is unknown and then asked if it is OK to proceed. Simply select “Yes” and the CAB is installed as normal. Your .NET CF 2.0 app will now run fine.
Wow – there was still a bunch more stuff I wanted to talk about but this is already longer then I meant for it to be - Check out the pics of the Jasjar below if you haven't already.
1C:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\WindowsCE\wce500\armv4i\NETCFv2.wm.armv4i.cab
Click to expand...
Click to collapse
http://maniac.fschreiner.de/content/view/7/15/
With SmartJournal, you can keep track of your phone calls at all times.
It takes the call log of your phone and transfers it into the Outlook journal.
Credits for the idea go to Paul O'Brien who posted an utility which does the same here - unfortunately this one did (and does) not work with non-English versions of Microsoft Outlook, so the tool posted here is a rewrite from scratch.
System requirements
Tobe able to run SmartJournal, you need the following:
Windows 2000/XP/2003
1MB free hard disk space
Microsoft Outlook (2003 tested, but 2000/XP should also work)
ActiveSync installed
As it is build with Visual Studio 2005, you the redistributables pack is needed. To install this, you need:
Windows Installer 3.1
Redristributables pack
I have Visual Studio 2005 on my PC plus the WM5 SDK. I have been developing a WM5 application and using the emulator to debug. It is nearly ready and thought that I would debug through the Wm5 PPC. I was then confronted with a warning message that the Compact Framework 2.0 was not installed on my PPC. OK I thought so downloaded the NETCFSetupv2.msi from Microsoft. When I try to run this I am told that I already have the .NET 2 Framework - presumably because I have VS 2005 etc.
Is there any way for me to get the CF2 onto my PPC without having to uninstall VS 2005???
Hi there,
Yes you can....
...\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\wce500\armv4i
go to this folder and pick up the frame work that suits you
copy the cab file "NETCFv2.wce5.armv4i.cab" for Pocket PC to Pocket PC and install it.....
regards
Aftab Alam
If you go into the properties of your project within VS2005 you will see a tab page for Devices. On that tab page change the target device to that which you want to deploy it to and lower down the page you will see a check box to "Deploy the latest version of the .NET CF". Ensure that box is checked. Debug your project and the CF will be installed on the device.
Hi,
I have just completed my first XDA program using VB.Net 2005 and have targeted to a Pocket PC 2003, which is the operating system of the XDA but I get this message what can I do? VB.Net does not have any other options for Pocket PC 2003.
Error 1
The specified program requires a newer version of Windows on the device. Device Connectivity Component
Please don't be insulted by this but VB was, is and always will be the crappiest language in existence.
My personal rants aside, try installing .NET CF 2.0 I know by default that is what VS 2005 uses and WM 2003 devices only have CF 1.0 / 1.1 in ROM.
Please don't be insulted by this but VB was, is and always will be the crappiest language in existence.
You may well be right given the problems I am having but sadly it’s the only one I know and I quite frankly was well happy when I manged to create this my first mobile app which works great on the emulator
My personal rants aside, try installing .NET CF 2.0 I know by default that is what VS 2005 uses and WM 2003 devices only have CF 1.0 / 1.1 in ROM.
I have tried your fix fix but my XDA does not like it and comes back with the message
The File “\windows\appmgr\install\microsoft.net\CF 2.0.CAB” is not a valid Windows CS Setup file
Am I doing something wrong
Thats odd. Only thing I can think of is try and re-download the installation from here.
No, done it again with the same result.
Do you know the exact file name for the correct cab and then I can perhaps search my hard drive and manually copy it to the XDA and execute it there
Anyone
Hi,
All have cracked the problem myself, the XDA has Pocket PC 2002 is there anyway to upgrade it to Pocket PC 2003?
Hi. So I just got a dump of my iPAQ 110, and I found this file. Earlier i stumbled onto this article:
http://www.ekhoury.com/2006/04/21/how-to-make-msn-messenger-add-ins/
Unfortunately this doesn't work for the latest messenger on the PC, but I was wondering if i can do something similar to make plugins for the mobile messenger. I tried to start a "Smart Device" project in VS2008 (I already have the wm6.0 sdk refresh installed), and then add this dll as a reference, but I get "A reference to "WLMMessengerplugin.dll" could not be added.", and when i click the help button it links me to an article saying this:
The project you are trying to load targets a device platform that your Visual Studio installation is not configured to support.
To correct this error
Install the platform that supports the project you want to load.
Anyone had any success with this?