-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why some conputer run AOT exe show error dialog,but others not? #61
Comments
I belive you miss call to
|
Other option is that you have some IME tools or other apps which provide accessibility service. Any ideas what can it be? |
Thanks for your replay, I know need add ComWrappers.RegisterForMarshalling(WinFormsComInterop.WinFormsComWrappers.Instance); But I want to know, why not add this code, after publish, some conputer run AOT exe show error dialog,but others not Another question : I add richTextBox to my Form, then Vistual Studio show error dialog : Built-in COM has been disabled via a feature switch. See https://aka.ms/dotnet-illink/com for more information. Although, I still can publish my program |
Another Question: I found you publish WinFormsComInterop.SourceGenerator in NUGET |
Another Question: Is it AOT not support System.Management ? If I not open AOT, that code return true. But when I use AOP , and add myClss in rd.xml, still return false public static bool IsWmiServiceOpen()
|
There no support for |
Thank you very much . One Question, Is rd.xml could be generate automatic ? I don't know the WinFormsComInterop.SourceGenerator is do for that ? |
i think you can using command line to get it |
my computer show error dialog like this,but my another computer not
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NotSupportedException: COM Interop requires ComWrapper instance registered for marshalling.
at System.Runtime.InteropServices.ComWrappers.ComObjectForInterface(IntPtr) + 0x59
at System.Windows.Forms.UnsafeNativeMethods.CreateStdAccessibleObject(HandleRef, Int32, Guid&, Object&) + 0xbb
at System.Windows.Forms.AccessibleObject.UseStdAccessibleObjects(IntPtr, Int32) + 0x4a
at System.Windows.Forms.ButtonBase.ButtonBaseAccessibleObject..ctor(Control) + 0x35
at System.Windows.Forms.Button.CreateAccessibilityInstance() + 0x23
at System.Windows.Forms.Control.get_AccessibilityObject() + 0x60
at System.Windows.Forms.Control.GetAccessibilityObject(Int32 accObjId) + 0x14
at System.Windows.Forms.Control.WmGetObject(Message& m) + 0x84
at System.Windows.Forms.Control.WndProc(Message& m) + 0x141
at System.Windows.Forms.ButtonBase.WndProc(Message& m) + 0x17d
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Interop.User32.WM msg, IntPtr wparam, IntPtr lparam) + 0x70
The text was updated successfully, but these errors were encountered: