maf

Broken tab navigation in popup with WPF user control hosted inside Winforms in default AppDomain

主宰稳场 提交于 2021-02-18 19:54:22
问题 I have a WPF user control that uses a Popup. This control is a plugin and can be loaded in the main AppDomain or in a separate AppDomain, and it is hosted in a Winforms form using ElementHost. When the plugin is loaded in the main AppDomain, and the popup is opened, tabbing between the fields of the popup instead moves focus to the first control of the popup windows parent. When it is loaded in a new AppDomain, the tab behavior works as expected/desired (it cycles through the controls in the

Broken tab navigation in popup with WPF user control hosted inside Winforms in default AppDomain

巧了我就是萌 提交于 2021-02-18 19:53:13
问题 I have a WPF user control that uses a Popup. This control is a plugin and can be loaded in the main AppDomain or in a separate AppDomain, and it is hosted in a Winforms form using ElementHost. When the plugin is loaded in the main AppDomain, and the popup is opened, tabbing between the fields of the popup instead moves focus to the first control of the popup windows parent. When it is loaded in a new AppDomain, the tab behavior works as expected/desired (it cycles through the controls in the

Give MAF plugin which run as separate process a custom name

僤鯓⒐⒋嵵緔 提交于 2020-01-24 09:49:47
问题 I activate my plugin using MAF[Managed Add - In Framework] in a separate process. The problem is that it gives default name "AddInProcess32" to the each plugin which run as a separate process. Can i give a custom name to the process which MAF create? If so how ? PS: Why i want to give custom name? Because i do not want user to kill process by mistake... I want to give process a name which shows it is part of my app clearly. 回答1: While desirable indeed, this is unfortunately not possible, as

Give MAF plugin which run as separate process a custom name

荒凉一梦 提交于 2020-01-24 09:49:05
问题 I activate my plugin using MAF[Managed Add - In Framework] in a separate process. The problem is that it gives default name "AddInProcess32" to the each plugin which run as a separate process. Can i give a custom name to the process which MAF create? If so how ? PS: Why i want to give custom name? Because i do not want user to kill process by mistake... I want to give process a name which shows it is part of my app clearly. 回答1: While desirable indeed, this is unfortunately not possible, as

C#, MAF, Unhandled Exception Management in separate AppDomain

两盒软妹~` 提交于 2019-12-23 16:25:22
问题 Okay, so I have a MAF application which loads up each addin inside of a separate appdomain. This is working fantastic for what I need as it allows me to dynamically unload and reload my addins at runtime. The problem is, I need to be able to take an unhandled exception in the child appdomain, catch it, and then let that appdomain fail gracefully without taking down the parent appdomain How do I go about doing this? It seems like a trivial task and one of the main benefits of using isolated

Can IoC and the Managed AddIn Framework (System.AddIn) work together with isolated AppDomains?

孤街浪徒 提交于 2019-12-21 20:59:09
问题 If I use Managed AddIn Framework (System.AddIn) and set it up to use separate AppDomains, can I use a centralized IoC container that is in the primary/default AppDomain? Can the IoC container resolve across the AppDomains? 回答1: I'm going to approach this answer by ignoring the MAF part of the equation, and concentrating on the AppDomain issue. An IoC container could theoretically do what you describe, assuming that the IoC entry point inherits from MarshalByRefObject or is wrapped by a class

Looking for a practical approach to sandboxing .NET plugins

≯℡__Kan透↙ 提交于 2019-12-17 08:01:22
问题 I am looking for a simple and secure way to access plugins from a .NET application. Although I imagine that this is a very common requirement, I am struggling to find anything that meets all my needs: The host application will discover and load its plugin assemblies at runtime Plugins will be created by unknown 3rd parties, so they must be sandboxed to prevent them from executing malicious code A common interop assembly will contain types that are referenced by both the host and its plugins

Can IoC and the Managed AddIn Framework (System.AddIn) work together with isolated AppDomains?

守給你的承諾、 提交于 2019-12-04 12:13:09
If I use Managed AddIn Framework (System.AddIn) and set it up to use separate AppDomains, can I use a centralized IoC container that is in the primary/default AppDomain? Can the IoC container resolve across the AppDomains? I'm going to approach this answer by ignoring the MAF part of the equation, and concentrating on the AppDomain issue. An IoC container could theoretically do what you describe, assuming that the IoC entry point inherits from MarshalByRefObject or is wrapped by a class that in turn inherits from MarshalByRefObject. With a 29K+ rep score, I am sure you know this but: 1)

How to specify AddIn process names?

蓝咒 提交于 2019-12-01 16:37:19
问题 I am using the Microsoft AddIn Framework to load AddIn assemblies. I am running them in their own process as to separate them from the service. The thing I don't like it that every AddIn process shows up as AddInProcess32.exe in the task manager. When using process isolation, how can we rename the name that shows in the taskmanager so that it's more descriptinve for users? 回答1: Unfortunately you can not. Filename for that process is hardcoded in private method GetProcessName(Platform platform

Looking for a practical approach to sandboxing .NET plugins

和自甴很熟 提交于 2019-11-27 05:52:41
I am looking for a simple and secure way to access plugins from a .NET application. Although I imagine that this is a very common requirement, I am struggling to find anything that meets all my needs: The host application will discover and load its plugin assemblies at runtime Plugins will be created by unknown 3rd parties, so they must be sandboxed to prevent them from executing malicious code A common interop assembly will contain types that are referenced by both the host and its plugins Each plugin assembly will contain one or more classes that implement a common plugin interface When