Re: WMDC developer doc badly needed... by Hong
Hong
Wed Apr 11 18:16:03 CDT 2007
Hello Kyle, I have the following issue with Windows Mobile Device Center:
We have an ActiveSync service provider that allows user to change settings
on the desktop by implementing IReplStore2::DoOptionsDialog and
IReplStore::ActivateDialog. In WMDC, the "Sync Settings" link for our SSP is
enabled when you check the checkbox to enable our SSP, but when you click
this link right after you check the checkbox, you get "No setting is
available" (or something similar) message. From now on, the "Sync Settings"
link for our SSP is removed and there is no way to change the setting any
more. If you do not click this link when you first enable our SSP (check the
checkbox), after a successful sync, this "Sync Settings" link for our SSP is
always enabled and works.
I noticed that if I click the "Sync Settings" link when I first enable our
SSP (get "no setting avaiable" message), a registry value "Settings =
NotImplemented" is added to the partner's sync object registry key. If I
delete this regitry value then disconnect / reconnect the device, the "Sync
Settings" link for our SSP shows up again.
My question is: if IReplStore2::DoOptionsDialog is for SSP to bring up
settings dialog before Initialize is called, and this works in ActiveSync,
why WMDC ignores it compeletely? Apparently WMDC is looking for some
undisclosed interface to be implemented in "Settings = [progid]" registry, so
what kind of interface should a SSP provide? Can we get some documentation
about it?
Thanks,
Hong Lu
Senior Software Engineer
CardScan, Inc.
"Kyle Lampe [MSFT]" wrote:
> Developers are seeing a number of these type issues. Microsoft is compiling
> a response to all of these, including this "How To" guide.
>
> In the meantime, please send me any issues you are seeing. We want to make
> sure we address as many issues as possible. My email address is shown but
> doesn't actually include the word "online" (to prevent spam).
>
>
> --
> Kyle Lampe
> Lead Software Design Engineer
> ActiveSync
> Windows Mobile
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Este mensaje esta mandado "COMO ES" sin guarantias y no da derechos
> ningunos.
>
> "Marvin K. Bellamy" <Marvin.Bellamy@gmail.com> wrote in message
> news:1172874692.861086.162090@30g2000cwc.googlegroups.com...
> > Herbert, can you clarify what you mean by "NULL interface pointer" and
> > what the exact resolution is to this problem? I'm also trying to
> > migrate my ActiveSync service provider to Vista.
> >
> >
> > On Feb 26, 5:36 pm, "hfann" <hhf...@rogers.com> wrote:
> >> Hi Jean,
> >>
> >> Microsoft support told me that all the interfaces are the same as in
> >> ActiveSync. Custom providers should work as is. A bug that causes my
> >> provider to crash onVista(but works in XP) is calling a NULL interface
> >> pointer. Apparnetly, the call is ignored without causing a crash on
> >> Windows
> >> XP. Once I corrected this bug, my provider works.
> >>
> >> Regards,
> >> Herbert
> >>
> >> "Jean G." <J...@discussions.microsoft.com> wrote in message
> >>
> >> news:2206D999-ED7B-40DC-AE3D-EDB1DDA746E3@microsoft.com...
> >>
> >> > Has anyone come across useful information about upgrading ActiveSync
> >> > service
> >> > providers (SSP) to make them compatible with WMDC/Vista? In one single
> >> > instance, I was able to synchronize all my custom data via my service
> >> > providers (upon creating a partnership). That was on a
> >> > cleanVistaPremium
> >> > laptop with WMDC freshly downloded and installed (I don't know the WMDC
> >> > build
> >> > back then, on Feb 2). All my data flawlessly synchronized from my PPC
> >> > to
> >> > that
> >> > laptop. Boy, was I happy... But that was short-lived. For some reasons,
> >> > at
> >> > this moment, none of my custom data synchronizes. In fact, I experience
> >> > all
> >> > sorts of issues (e.g. WMDC crashing, not synchronizing, etc) when my
> >> > service
> >> > providers are activated on the device (i.e. synchronization registry
> >> > entries
> >> > set). I've tried re-creating partnerships, re-downloading/re-installing
> >> > WMDC,
> >> > shutting down anti-virus/firewall, using WM 2003, SE and 5.0 devices,
> >> > etc.
> >> > Same exact results. All I can say at the moment is that my sync
> >> > providers
> >> > do
> >> > not work underVista/WMDC, whereas they've been working fine on XP for
> >> > 3+
> >> > years.
> >>
> >> > Any pointer to a WMDC service provider ref guide/doc/info/tip/help
> >> > would
> >> > be
> >> > immensely welcome. That's a critical issue for me (i.e. our customes)
> >> > at
> >> > the
> >> > moment.
> >
> >
>
>