Giters

ahmed605 / 10Mica

Mica but for Windows 10

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Does not work on Win 10 19045

Guerra24 opened this issue · comments

commented

Hello!

It works just fine on 22621, but I can't get it to work on 19045, it throws the following exceptions:

If declared in XAML

Exception thrown: 'Windows.UI.Xaml.Markup.XamlParseException' in LRReader.UWP.exe
An exception of type 'Windows.UI.Xaml.Markup.XamlParseException' occurred in LRReader.UWP.exe but was not handled in user code
The text associated with this error code could not be found.

Cannot create instance of type 'TenMica.TenMicaBrush' [Line: 12 Position: 64]

The program '[236] LRReader.UWP.exe' has exited with code 4294967295 (0xffffffff).

And if instantiated through code

Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))

You can find the project src here, if that is of any help. I'm trying to add it here.

commented

Hmm looks like the winmd isn't getting registered, I assume this is a nuget misconfiguration but not a problem in the library itself, will investigate the problem

commented

I just tried it on both a managed project and a native project and it works for both, are you sure that you are using version 1.0.0-beta (not alpha) and not using AnyCPU?

Also how are you trying it on 19045? via remote debugging or via a Release package?

commented

I'm sure it is 1.0.0-beta and not using AnyCPU.

Remote debugging on a VM, which so far has worked fine.

commented

Hmm, can you check if TenMica.dll and TenMica.winmd are copied to the package root on the VM?
And if possible can you show me the generated AppxManifest.xml from the VM?

commented

That's so weird, it's registered

<Extension Category="windows.activatableClass.inProcessServer">
  <InProcessServer>
    <Path>TenMica.dll</Path>
    <ActivatableClass ActivatableClassId="TenMica.TenMicaBrush" ThreadingModel="both" />
  </InProcessServer>
</Extension>
commented

I have tried using a Release package only, I will try again using remote debugging on a VM to see if I can reproduce the issue

commented

I just tried using remote debugger and it still works
tenmica

commented

did you use any kind of debloaters on the VM? and did you try with an actual device, maybe the problem is in the VM

commented

No, and I don't have any devices with Win 10 😅 just set up the vm for this... I will try on a new VM with multiple builds just in case, I'll let you know, thanks for your time!

commented

no worries, let me know the results!
BTW this is unrelated to this bug but in order for Mica to render under VMs you have to apply this Registry value

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm]
"ForceEffectMode"=dword:00000002

This won't fix the exception tho, this is just for it to render correctly after fixing the exception.

I would also recommend HyperV for the VM, it has a really good Windows integration.

commented

Well, figured out the issue. Turns out that on 19041-5 the manifest sometimes is not re-registered. Once I uninstall the app and redeploy it, it works just fine without issues. My guess is that this issue only happens when remote debugging, but I have not tested it with VS on the VM itself.

Windows being windows as always 🙃

Going to close the issue, thanks again!