Here's the setup:
I'm trying to connect / deploy to a Motorola Windows Embedded Compact 7 device from VS 2008. The development machine VM is Windows XP (it has tools and SDKs going back to eVC3 on it that will not run on anything newer). It is therefore running ActiveSync as opposed to WMDC. Basic RAPI seems to be working as I can browse the device file system, ect via ActiveSync. This developemnt system works successfully with dozens of other devices, but this might be the first CE 7 device. And again, the error message was simply "The bootstrap could not be loaded".
I'd appreciate any tips on getting a successful connection to the CE 7 device working.
I had exactly the same problem. The solution for me was to install the SDK for the pda. Mine was MC32N0.
You can find the sdk here
Related
We are running QuickBooks Enterprise 7 (I know it is old and not supported). I have MS Access applications that are using the SDK (via VBA) to send transactions to QB. We have started upgrading computers to Windows 10. While QB works fine, the SDK is not. We are getting the error "Could not start QuickBooks". I need to get this fixed as it is a critical system. I have tried to upgrade the SDK to 13 but that didn't help either.
I have a program written in vb.net and compiled in Visual Studion 2005 for Windows CE 5.0. It works fine on a Windows CE device. I am trying to run it on another device which has Windows WM. It will load, but doesn't respond to any commands. My understanding is that I need to recompile it with different libraries (per Motorolla - the device manufacturer) that are compatible with Windows CM. My problem is that I am new to the mobile environment and don't know how to find what I need and set up the environment. Can anyone point me in the right direction? Thank you
I've a windows 8 app and a windows 2012 Build Server with Jenkins and / or Finalbulder Contiua.
No I can only install Visual Studio for WinRT Apps only on Windows 8 or later.
So this means ,that my build server has to be windows , right
is there a way to compule windows 8 apps on non windows 8 os ?
Is there some kind of "build win 8 sdk" for other os ?
Short answer: no, you'll need Windows 8 or Windows Server 2012.
A Jenkins-specific tip: I tried a number of things but did not manage to have it start apps when Jenkins runs as a service. Starting from a logged-in user account was the only way I could get it to work.
Also I'd like to recommend our Apprunner project which we developed to install, run and uninstall packages from within Jenkins.
Finally, if you're working on a Javascript-based app, you can have a look at the unit-testing-related code in our SQLite component which uses Jasmine and outputs JUnit/Jenkins-compatible test result files.
I'm having problems migrating a PowerBuilder application from XP to Windows 7.
We've built the application in PowerBuilder on Windows XP, and when we attempt to install components in to component services on Windows 7 machines, we get compatibility errors. Everything works great on Windows XP. But I think because the DLL's on 7 are so different, it's having problems.
If the program was built using a PowerBuilder IDE in a Windows 7 environment, would that possibly fix the problem?
The application is divided into
- a server component running on Server 2003
- a client component which installs sucessfully on Win7
- proxy components that are generated into an MSI when the server components are installed.
The problem is only the proxy. The MSI doesn't want to work on Windows 7.
Without the proxy installed on the client desktops, the client can't communicate with the server.
When I run the MSI in compatibility mode on Windows 7, I get some details of the error. Here they are
Program Compatibility Issues found Incompatible Application Fix
application CCS_Proxy_XP_Exports
Issues found Incompatible Application CCS_Proxy_XP_Exports is
incompatible.
Fix application CCS_Proxy_XP_Exports Provides steps to fix the
incompatible application. CompatMode CompatMode UserVerifySolution
User Verification of Solution Verify_NO
Detection details Collection information Computer Name: ##########
Windows Version: 6.1 Architecture: amd64 Time: Wednesday, November
14, 2012 11:56:36 AM
Publisher details Program Compatibility Make older programs run in
this version of Windows. Package Version: 1.5 Publisher: Microsoft
Windows
Program Compatibility Make older programs run in this version of
Windows. Package Version: 1.0 Publisher: Microsoft Corporation
If I view more details on the event log, I get the following
“Product: Client Communications (Application Proxy) -- Error 1928.
Error registering COM+ Application. Contact your support personnel
for more information.”
General idea
Actually dll on the win7 platform are not different from previous ones. There can be differences related to the multiple and different C runtimes that live now in the WinSxS dll-hell directories but this should not impact powerbuilder (as I can say from my 11.5 classic release experience).
I suspect that you might have some problems related to the UAC and or ACL management. I recently upgraded some legacy PB applications by adding compatibility to the Vista / Win7 specifications.
In short : the application must run without needing administrative privileges, and must not try to modify data in privileged places like c:\ or c:\windows.
Thus everything must no more be installed in program files directory. The application binaries can be deployed in program files but if the application need to create / modify some files they must be deployed in a ProgramData subdirectory for user-shared datad and / or in the local user data files for the private data. The application has to be modified to create or find the files in the correct directories. If you do not comply to the standard, the file virtualization mechanism can hide a lack of rights and can simulate the files in a VirtualStore directory in the user local data but is just a workaround and it provides some other problems.
Com+ error
Given you error messages, if the proxy is also a PB application, given the fact that PB only produce 32bits binaries and that your system is a 64bits one, maybe that the tips to register a 32b COM+ onto a Win2008 could help you?
Thought, your proxy exe/dll file does not have manifest or manifest does not contains compatibility section. Try to add compatibility info to manifest.
There's no emulator for Windows 8, so in order to develop metro apps I must install the release candidate on a device and run Visual Studio there, right? That's what this page seems to suggest, but I just wanted to double check.
Yes, Windows8 is required.
However, VM can be used. For example, I'm running Win8RP/64 and VS2012RC in Oracle VirtualBox on Win7/64.
NOTE: For developing Metro Style App, you should NOT install VirtualBox Extension Pack.
Yes, you need Windows 8 to develop Windows 8 Metro style apps.
Metro Style apps rely on a new set of APIs which are implemented only in Windows 8 through the the Windows Runtime (WinRT).
There is no emulator for Windows 7 and not even for Windows 8... Windows 8 has a simulator which in practice is just a Remote Desktop session to the same machine. It is not an emulator.
While Windows 8 is not in its final version, what I recommend is to install Windows 8 in a VHD (virtual hard disk) and boot your PC directly to the VHD. It is faster than running virtual machines (because only the disk is virtual, all the rest is real hardware) and you can keep your Windows 7 intact.
This is what I've been using since Developer Preview. I have a dual-boot configuration being one for the Windows 7 that is booting from the regular disk partition, and one Windows 8 that is booting directly from the VHD on disk.
Metro UI style is just a design approach and some guidelines. You are free to implement such interface using Visual Studio 2010 as well as 2008. Using C# and WPF everything is possible. But, indeed, new Visual Studio has a set of Metro style components (WPF) with which your development process will be much more quicker.
The only thing you can't use at OS other than Windows 8 - is WinRT subsystem.
Almost all of the development tools needed to build Metro style applications can be run on OS's other than Windows 8 (Visual Studio and the package creation tools require Windows 8). So it should be possible to set up a build environment using msbuild.exe (or even make/nmake) that will compile and link metro-style applications on an OS other than Windows 8.
However some parts of development MUST be done on Windows 8 - the tools for some of the steps of development will only run on Windows 8.