带有附加DLL的软件开发

本文介绍了带有附加DLL的软件开发的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

您好，我正在尝试在.NET 2.0平台上使用Window Form编写一个可工作的基本程序，使其能够合并将来的附加库(DLL)，而不必重新编译原始基本程序.每个库都将包含一个窗口窗体，该窗体将以某种方式自动添加到原始基础程序的窗口窗体中，例如为每个DLL应用程序添加一个新选项卡.某些数据将在DLL和基础程序之间共享. 我的第一个问题是我应该使用什么和/或应该如何构造我的基本程序和附加库以按照上面描述的方式工作.我不想让它成为每个DLL应用程序的弹出窗口，因为它将使它成为两个或更多单独的应用程序，并且在它们之间共享数据似乎非常困难.另外，如果有很多附加的DLL，则为每个DLL应用程序添加一个新选项卡似乎并不实际.因此，我不知道了. 我的第二个相关问题是如何保存每个DLL应用程序和基本程序的状态而不必重新加载所有数据.

Hi, I am trying to program a working base program with Window Form on .NET 2.0 platform with the ability to incorporate future add-on library (DLL) without having to recompile the original base program. Each library will contain a Window Form that is somehow automatically added to the Window Form of the original base program like adding a new tab for each DLL application. Certain data will be shared between DLL and the base program. My first question is what should I use and/or how should I structure my base program and add-on library to work the way I described above. I don''t want it to be a pop up windows for each DLL application, because it would make it two or more separate applications and sharing data between them seems very difficult. Also, adding a new tab for each DLL application doesn''t seem practical if there are lots of add-ons DLLs. Thus, I am out of idea. My second related question is how do I save the state of each DLL application and the base program without having to reload all data.

推荐答案

您的应用程序将依赖于插件框架 [ ^ ]. 听起来您的主应用程序除了为一堆插件提供通用接口外，不会做任何事情.首先阅读发布链接后面的内容，并考虑所有插件之间将使用哪些数据和接口. Your application is going to depend on a Plugin Framework[^]. It sounds like your main application isn''t going to do much of anything, other than supply a common interface for a bunch of plugins. Start by reading the stuff behind the post link and think about what data and interfaces are going to be common between all of your plugins.