Re: Regarding, Using Com DLL in WindowsCE Device Applications

I have the same problem as Kiren, the exception still here after i
resigstered the Com dll in the windows mobile emulator. Can you give me some
help

Thank you in advance


Eric Chan

"Chris Tacke, eMVP" wrote:

It's impossible to do. The DLL was compiled for a different OS and
processor. Without source code there's no way to make it useful in CE.
Even with source it could take a lot of work to port it.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

"Kiran" <Kiran@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1E3A23A3-4EF6-4A1F-9D80-CBDAD681CD99@xxxxxxxxxxxxxxxx
thank you for your quick reply.

we don`t have the source code for the DLL.So do you know any other way to
resolve the problem.
Is there any 3rd party tool available to convert the dll to work with
windows CE

Thanks & Regards
kiran


"Peter Foot" wrote:

You can't use desktop COM components in device projects - COM dlls for
Windows CE must be built for Windows CE and the specific processor
architecture of your device.

Peter

--
Peter Foot
Microsoft Device Application Development MVP
www.peterfoot.net | www.inthehand.com
In The Hand Ltd - .NET Solutions for Mobility

"Kiran" <Kiran@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:10362DEF-B97A-44DB-9427-41315F34092F@xxxxxxxxxxxxxxxx
hi,
I am new to mobile applications(windowsCE Device Application C#). I
added
a
com dll as reference.when i run the application it gives an error
message
like ...
"COM object with CLSID '{21723099-8833-4F74-94F4-BEC4B158CFBB}' cannot
be
created due to the following error: Class not registered ."

But the same Com DLL is working fine in .net windows application.The
only
problem with WindowsCE Device application.
Is my approach is correct to use COM DLL in WindowsCE Applications?. Or
Is
there another way to register com DLL to use in windowsCE device
application.
Please help me .

Regards
Kiran




.

Relevant Pages

  • Re: .Net packaging/wrapper application?
    ... it just didn't work well in reality due to DLL ... Windows works is to look in the executable's directory for a needed DLL ... the way apps used to work when they developed Windows. ... Looks to me like Jim is looking for the .NET equivalent of compiling ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Unnown process... 5eplorer.exe
    ... do not remove the cause (a "super"-hidden .dll program) but only remove ... symptom files and registry settings. ... It has all permissions but 'copy' denied to everyone, ... then by using the Windows XP Recovery Console. ...
    (microsoft.public.win2000.general)
  • Re: WinSxS, functional under 2k ?
    ... The newSide-by-Side Assembly technology was introduced with Windows XP to help reduce or eliminate DLL Hell. ... If you recall earlier Windows versions, like Windows 95, when you installed an application you were warned if the installer tried to replace a DLL from the system folder with an older version and you were asked if you wanted to accept the change. ... Until Windows XP it wasn't so easy to use different versions of shared system DLLs, that is what the new Side-by-Side assemblies attempts to resolve. ...
    (microsoft.public.win2000.general)
  • Re: Determine name and path of dropped object?
    ... MDE I would really suggest the use of external DLL to hold the subclassing ... windows after loading the Microsoft Office Visual Basic Editor, ... Public Declare Sub DragAcceptFiles Lib "shell32.dll" _ ...
    (microsoft.public.access.modulesdaovba)
  • Re: .Net packaging/wrapper application?
    ... the simple answer to DLL Hell for Visual Basic apps was simply to place a copy of the needed DLLs in the same directory as your executable. ... The way Windows works is to look in the executable's directory for a needed DLL BEFORE using the registry to find one EVEN IF THE REFERENCED DLL IS REGISTERED ON THE PC RUNNING THE APPLICATION THAT NEED IT. ... Perhaps I'm getting old and but what really bothers me is nobody seems to notice this--maybe the 80s was before they got into programming. ... Looks to me like Jim is looking for the .NET equivalent of compiling with static libraries to produce a single executable. ...
    (microsoft.public.dotnet.framework.aspnet)