pimstore dll for working with pocket outlook calendar

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: coder (coder_at_discussions.microsoft.com)
Date: 01/21/05


Date: Fri, 21 Jan 2005 05:37:02 -0800

Hi all

I have just started some research into writing an app for Windows Mobile
2003 for an ARM processor device, so please excuse my in-experience or any
stupid questions...

What I would like to do :
----------------------------
I would like to write an app for a Pocket PC running Windows Mobile 2003
that can take data from a received SMS message and create a new calendar
appointment using some of that data. However the part about getting the data
from an SMS is the second phase and all I'm concentrating on right now is
being able to add,delete and view appointments/calendar items.

What I have done :
----------------------
I have created a windows mobile app using visual studio .Net and VB.Net and
have got the basic frontend of the prototype that I want to demo for my boss.
All using the Windows Mobile 2003 emulator.

Where I am stuck :
----------------------
I want to create a new calendar entry. So I try import the pimstore.dll for
the arm processor however it is not a valid assembly, presumably because the
.Net compact framework doesn't allow COM dll's to be referenced as in a
normal .Net desktop application.

So I use the tlbimp.exe function to change the pimstore.dll to a
pimstoreM.dll. Now this file I can import into my Mobile app but with an
error that the import may or may not be for the correct platform. ??

Once that has been added, I cannot view the reference in the object browser
as normal, but I can type all the coding using the normal pimstore.dll
interfaces, without any errors indicated by the blue underlining. However
when I compile the app i get the following :

1) Error: The dependency 'mscorlib, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=969db8053d3322ac' in project 'Diarise' cannot be copied to the
run directory because it would conflict with dependency 'mscorlib,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.
   and
2) Error: The dependency 'mscorlib, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' in project 'Diarise' cannot be copied to the
run directory because it would conflict with dependency 'mscorlib,
Version=1.0.5000.0, Culture=neutral, PublicKeyToken=969db8053d3322ac'.

I'm not sure why I'm getting these errors, or how to overcome them. Please
any suggestions will help...



Relevant Pages

  • Re: Best way to build unmanaged C++ for WM5
    ... download the files; or b) statically link. ... But I continue to get the "not valid PocketPC ... > sharedMFC app, you get these files mentioned in the Properties by default. ... > I always immedately switch that setting to Windows Mobile 5.0 PocketPC ...
    (microsoft.public.pocketpc.developer)
  • Re: validating a password string
    ... This application is a commercial windows mobile ... app that is sync'ed with a desktop client / SQL. ... Dim vPassword1 As String ... Dim frmMainMenu As New SystemMenu 'create the system menu ...
    (microsoft.public.dotnet.languages.vb)
  • Re: app running in Mobile 5 sometimes crashes in Mobile 6
    ... The application uses a modified version of the ShowDialog() ... method to display forms, as explained in a MSDN article. ... running the application for over a year now, all in Windows Mobile 5 ... We started testing our app. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: access
    ... if you have a really complicated database and need wireless connectivety to ... >> You can't actually run Access on a Windows Mobile device. ... You would then need a third party app to work ... >> One of my favourite apps is HanDBase from DDH Software. ...
    (microsoft.public.pocketpc)
  • Re: "The underlying connection was closed: Could not establish trust relationship for the SSL/TLS se
    ... You're making a remote method call to a network service. ... your app has a dependency upon something it has no control ... app has no control. ...
    (microsoft.public.dotnet.framework)