Ticket #363 (closed enhancement: fixed)
Plugin Code Review
| Reported by: | Joel | Owned by: | Joel |
|---|---|---|---|
| Priority: | critical | Milestone: | Eraser 6.1/6.2 |
| Component: | Core | Version: | |
| Keywords: | Cc: | ||
| Processor Architecture: | Blocked By: | ||
| Blocking: | #70, #147 | Operating System: |
Description (last modified by Joel) (diff)
Plugins should have a glue library that doesn't change, like a runtime for plugins that all plugins depend on (instead of a specific Eraser.Manager version)There should be a Tools menu for plugins to include themselvesPlugins should have alternative methods of declaring themselves as Core -- since Core plugins can't be disabled, these are plugins which are referenced directly within EraserChange the PluginInstance class to the PluginInfo? class
Blocking
| Id | Summary | Milestone |
|---|---|---|
| #363 | └ Plugin Code Review | Eraser 6.1/6.2 |
| #147 | └ Ballast File Creation. | Eraser 6.1/6.2 |
| #70 | └ Cleaning up of privacy leaks | Eraser 6.1/6.2 |
Blocked by
| Id | Summary | Milestone |
|---|---|---|
| #363 | └ Plugin Code Review | Eraser 6.1/6.2 |
Change History
comment:1 Changed 3 years ago by Joel
- Status changed from new to accepted
- Owner set to Joel
- Description modified (diff)
comment:2 Changed 3 years ago by Joel
- Description modified (diff)
Fixed in r2050.
Core plugins can now only be defined in the loading library (Eraser.Manager.dll) and the Loading Policy attribute is ignored if it is set as core, regardless of Authenticode signature and Strong Name key.
comment:5 Changed 2 years ago by Joel
- Description modified (diff)
PluginInstance? class was renamed to the PluginInfo? class in r2293
Note: See
TracTickets for help on using
tickets.
