NFC: incorrect message passed with PeerFinder.Start
-
Mittwoch, 14. März 2012 12:11
David,
I'm using latest VS11 with released Windows 8 beta.
I compiled and run the proximity sample and the proximity driver from the driver samples.
I started first scenario from the sample that actually calls: PeerFinder::Start().
It triggers subscription for message in the driver.
Here comes the problem: The message received in the driver is "Windows."some junk symbols".
Do you have an idea why this can happen or whom should I ask about it.
Thank you,
Evgeny.
- Geteilt Rob CaplanMicrosoft Employee, Moderator Mittwoch, 14. März 2012 16:00 new question
Alle Antworten
-
Donnerstag, 15. März 2012 02:29Moderator
Evgeny,
I will look into this for you.
Best Wishes - Eric
-
Montag, 7. Mai 2012 23:29
What are you trying to accomplish and what are you expecting to happen? What you've described sounds expected; calling PeerFinder::Start() will cause several internal publications and subscriptions. These internal publications and subscriptions often have some randomly generated names. If you can help us understand what you are trying and what other problematic symptoms you are seeing, we can hopefully help resolve you issue.
Thanks,
Mike (MSFT)
- Als Antwort vorgeschlagen Alan J. McFarlane Dienstag, 15. Mai 2012 16:08
- Als Antwort markiert Eric Hanson-MSFTMicrosoft Employee, Moderator Montag, 11. Juni 2012 22:21
-
Mittwoch, 6. Juni 2012 20:12Moderator
Evgeny,
Were you able to resolve this issue?
Best Wishes - Eric
-
Montag, 11. Juni 2012 22:21Moderator
Evgeny,
What you've described sounds expected; calling PeerFinder::Start() will cause several internal publications and subscriptions. These internal publications and subscriptions often have some randomly generated names
Best Wishes - Eric
- Als Antwort markiert Eric Hanson-MSFTMicrosoft Employee, Moderator Montag, 11. Juni 2012 22:21

