Hi All,
I have created a Brokered Windows Runtime Component and a Brokered Proxy Stub in my solution using this tutorial. The solution hierarchy is like
![]()
I have everything working fine on my development machine which has 64bit Windows 8.1 installed too. But the app crashes everytime I run it on Surface Pro.
The exception thrown is "Requested Windows Runtime type 'BrokeredComponent.Class' is not registered. at
System.StubHelpers.StubHelpers.GetWinRTFactoryObject(IntPtr pCPCMD) at BrokeredComponent.Class..ctor() at WinRTBrowserPOC.MainPage.d__0.MoveNext()".
I understand the problem is with component registration which is done on the dev machine by setting Linker/General/Register Output –> YES on ProxyStub project(given VS is running in admin mode) but I can't figure out why this step is required on a real device and how do I do it.
Do I need to manually transfer the dll and winmd files generated on dev machine to the device at the location mentioned in ActivatableClassAttribute?
Do I need to manually register the dll on device using regsrv32?
Please let me know how do I resolve this issue.
Regards,
Vinay
I have created a Brokered Windows Runtime Component and a Brokered Proxy Stub in my solution using this tutorial. The solution hierarchy is like
I have everything working fine on my development machine which has 64bit Windows 8.1 installed too. But the app crashes everytime I run it on Surface Pro.
The exception thrown is "Requested Windows Runtime type 'BrokeredComponent.Class' is not registered. at
System.StubHelpers.StubHelpers.GetWinRTFactoryObject(IntPtr pCPCMD) at BrokeredComponent.Class..ctor() at WinRTBrowserPOC.MainPage.d__0.MoveNext()".
I understand the problem is with component registration which is done on the dev machine by setting Linker/General/Register Output –> YES on ProxyStub project(given VS is running in admin mode) but I can't figure out why this step is required on a real device and how do I do it.
Do I need to manually transfer the dll and winmd files generated on dev machine to the device at the location mentioned in ActivatableClassAttribute?
Do I need to manually register the dll on device using regsrv32?
Please let me know how do I resolve this issue.
Regards,
Vinay
No comments:
Post a Comment