Guest Mattcoad Posted November 26, 2003 Report Posted November 26, 2003 I'm having some trouble getting the Smartphone 2003 SDK working with my Visual Studio 2003. I've got a long history of using Visual Studio .NET and have the prior version installed. However I don't have embedded Visual C++. During installation an error message pops saying during the execution of some VBScript it "Could not initialize property bag". The installation then proceeds. However if I then start up Visual Studio, I can happily create the Ye' Olde SmartPhone hello world app. However when I attempt run it using the emulator it always says "There is a problem with the build" however the error log is very light on actual reasons on what the actual problem is. If you force it to attempt to run anyways but pops up an error "Could not load WinCE Image." and Visual Studio gets stuck forever trying to load the emulator. I have no trouble running a Pocket PC app.
Guest Peter Foot Posted November 26, 2003 Report Posted November 26, 2003 Did you have Visual Studio running when you ran the installer? also do you have Admin priviledges on the PC you are using? Also some Anti-virus software can have problems with vbscript files (I'm running NAV and it pops up a prompt but I'm able to authorise the script and continue) Setup uses a VBScript to set up some of the files/registry entries required to plug into Visual Studio. You could try re-running the scripts from the C:Program FilesWindows CE Toolswce420SMARTPHONE 2003Install_files folder, or run the installer again and repair the installation. Peter
Guest srider Posted November 29, 2003 Report Posted November 29, 2003 has anyone found a fix for this? it's driving me nuts :lol:
Guest srider Posted December 3, 2003 Report Posted December 3, 2003 has anyone found a fix for this? it's driving me nuts :lol: Well, I think I've found a fix. Re-install Windows Scripting Engine 5.6
Guest jez Posted December 4, 2003 Report Posted December 4, 2003 I'm having problems installing the SDK. Visual Studio .NET enterprise architect, gets half way and quits having "encountered an error" MsiInstaller reports in the Event Log Product: Microsoft Smartphone 2003 SDK -- Installation operation failed. Anyone else had similar problems? Jez
Guest Peter Foot Posted December 4, 2003 Report Posted December 4, 2003 Are you installing from an Administrator account (or account with admin priviledges?). Is Visual Studio shut down at the time of installation...
Guest jez Posted December 4, 2003 Report Posted December 4, 2003 Yep, the obvious stuff is done. I definatly some kind of install quirk - seems to ditch out during some kind of hardware config..... Jez
Guest Peter Foot Posted December 4, 2003 Report Posted December 4, 2003 Do you have an active network connection on the PC? Or do you have a Connection setup with a "Virtual PC Emulated Ethernet Switch" listed in the properties for the connection? I can't remeber at which stage in the install this is added but you need an active network connection for the emulator and the virtual switch can be used if you don't have a permanent lan, wifi or similar connection. Don't you just wish these installers would give out a descriptive error message. :roll: Peter
Guest jez Posted December 4, 2003 Report Posted December 4, 2003 Ah, thats what it is..... Forgot about the emulator being based around VirtualPC. I have VirtualPC 2004 installed, which is probably causing the issue. Perhaps I'll try removing VPC 2004, installing the SDK and then reinstalling VPC. I'll have ago in the morning. Thanks for pointing that out!!!
Guest jez Posted December 8, 2003 Report Posted December 8, 2003 OK, sorted this in the end. Thought I would let you know the issue, just incase someone else stumbles across a similar problem. Virtual PC 2004 seems to replace the VPC System driver which causes the SDK to rollback the install. This can be seen from logging the Windows Installer Install. In order to get it to install, you will need to remove VPC 2004 (not yet tried to reinstall it), remove the Smart Device Programibility from the Visual Studio .NET install (VB.NET and C#) (add remove programs) and then reinstall it. This then solves the problem! J
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now