Re: CF2.0: deploying my COM DLL to the emulator under VS2005

Tech-Archive recommends: Speed Up your PC by fixing your registry

I understand that I can reproduce this, but Beta 1 had so many issues with smart device projects, that now with beta 2 availability (it's already on MSDN) you would be much better of by switching to it.

--
Alex Feinman
---
Visit http://www.opennetcf.org
"Smith" <Smith@xxxxxxxxxxxxxxxxx> wrote in message news:OQuecVHRFHA.3496@xxxxxxxxxxxxxxxxxxxxxxx 
I am using Beta1.

The ATL project and the .NET are located in two different solutions (see below why).

When I right-click on the ATL Project in the first solution and select Deploy, the emulator is launched but I get a deployment error "%1 is not a valid Win32 application". Furthermore, I suspect the new Smartphone 2003 SE emulator is launched, not the Legacy one.

With the other solution and .NET project, I've got to deploy using the Legacy Smartphone 2003 SE project otherwise I get the same of deployment issues.

Looks like there is an emulator version (legacy or non-legacy) mismatch and Visual Studio is getting confused when both my ATL SmartDevice DLL project and my .NET C# project reside in the same solution, sometimes launching both emulators concurrently.

You can reproduce the problems I describe by doing the following:

- create an ATL SmartDevice project (DLL) supporting both PocketPC 2003 and SmartPhone 2003, then add an ATL freethreaded SimpleObject.
- build it then deploy it. First, you won't have the choice whether to use the legacy or new emulator and then you'll end up with the "%1 is not a valid Win32 application" issue.

When building a SmartPhone 2003 SE .NET application, if you deploy it to the new (non-legacy) emulator, you'll also end up with deployment issues.

I was also unable to build a proxy/stub library for the ATL project, merging it or not in the main DLL. I got compilation errors talking about PROXYFILE_FIRST_START or something like that. But this is another subject (I use automation-compliant interfaces now anyway so this is irrevelant).

Apparently Beta1 has serious problems with emulators and C++.

Any idea about whether Beta2 addresses these problems?

Thanks for your help.



"Alex Feinman [MVP]" <public_news@xxxxxxxxxxxxxxx> wrote in message news:%23OApUGHRFHA.904@xxxxxxxxxxxxxxxxxxxxxxx
Simply right-click on your ATL project in the solution explorer and select Deploy. This will register it as well.


--
Alex Feinman
---
Visit http://www.opennetcf.org
"Smith" <Smith@xxxxxxxxxxxxxxxxx> wrote in message news:eSZ11yGRFHA.1980@xxxxxxxxxxxxxxxxxxxxxxx 
Hi,

I've got a VS2005 Beta1 ATL DLL project and created an interop assembly with tlbimp. I have another project, Smartphone 2003 SE that I test with the Smartphone 2003 SE Legacy emulator (the other Smartphone emulator doesn't work, I have a deployment issue).
I have referenced the interop assembly from the .NET application but I suspect the actual underlying COM DLL doesn't get deployed when hitting F5 to start debugging.

Can you help deploying this DLL and register it in the emulator space? I've got absolutely no clue about what I should do.

Thanks.







.

Relevant Pages

  • Re: CF2.0: deploying my COM DLL to the emulator under VS2005
    ... The ATL project and the .NET are located in two different solutions (see ... I suspect the new Smartphone 2003 SE ... emulator is launched, not the Legacy one. ... Visual Studio is getting confused when both my ATL SmartDevice DLL project ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: How to register a directshow DLL in Windows Mobile 5.0 or 6.0?
    ... the emulator but now when I run the code CoCreateInstanceonto my filter ... emulator and on a Windows Mobile 6 terminal. ... // SampleGrabber.cpp: Implementation of DLL Exports. ... http://msdn2.microsoft.com/en-us/library/aa918244.aspx for how to register ...
    (microsoft.public.windowsce.app.development)
  • Re: again a "cant find PInvoke DLL" problem
    ... Right now I'm working only with an emulator, ... I have read on a forum that there is a \windows folder on ... I will try to build again the dll but I don't really understand ... I'm trying to develop a GIS mapping software on smart devices using VS ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Developing for the Windows 2003 Smartphones.
    ... Yes you will need to install the Smartphone 2003 SDK to add Smartphone ... This will add the emulator, ... Pocket PC 2003 SDK, which will give you additional emulators. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: How to install .Net CF?
    ... If the application is built for a regular Smartphone it won't work on the ... emulator since devices use ARM CPUs but the emulator is running on X86. ... > way is connecting the emulator with the ActiveSync, ... >> Peter Foot ...
    (microsoft.public.dotnet.framework.compactframework)