Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Whitelisting assemblies to scan for addin roots
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Lluis Sanchez Gual  
View profile  
 More options Dec 19 2011, 12:56 pm
From: Lluis Sanchez Gual <sll...@gmail.com>
Date: Mon, 19 Dec 2011 18:56:19 +0100
Local: Mon, Dec 19 2011 12:56 pm
Subject: Re: [mono-addins] Whitelisting assemblies to scan for addin roots

El 30/11/2011, a las 17:26, Weeble escribió:

> I would like to prevent scanning for addins and addin roots of DLLs in
> my application directory except for those that I explicitly whitelist.
> Right now I have to add <exclude> entries for every *other* DLL in
> that directory. I see that AddinFileSystemExtension can be used to
> provide a virtualized view of the file-system to the scanner, so it
> seems theoretically possible that I could just provide it with a view
> that hides all DLLs except for the ones in my whitelist. However, I
> can't see a way to use this correctly. I can register this with an
> AddinRegistry with RegisterExtension, but AddinEngine.Initialize
> creates a new AddinRegistry and then immediately starts scanning with
> it, before I have an opportunity to register any extension with it. So
> even though I can eventually register the extension, it's too late,
> because the registry has already scanned all the DLLs in the
> application directory.

> 1. Aside from this issue, is AddinFileSystemExtension suitable for
> this purpose?

Not really. I added AddinFileSystemExtension with the intention to use it in a MonoDevelop add-in for building add-ins (which is not finished).

> 2. Is there a way around this problem without a change in Mono.Addins?

I fear not.

> 3. If not, I could probably change Mono.Addins to achieve what I want,
> but how can I maximize the chance that my patch would be accepted back
> into the project?

The best solution would be to extend the .addins file format to allow specifying a whole directory to exclude, and a set of files to include (the white list).

Lluis.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.