Uniquely identifying and referencing elements

Topics: Metadata Model
Feb 10, 2010 at 2:58 PM

Hi,

Is there an easy way to get an identifier for each metadata element (type, method, etc) which a tool can use to save analysis results, and search back for these items again?

 

Regards,

Matthijs ter Woord

Coordinator
Feb 10, 2010 at 3:26 PM

I'm afraid not. It would be a very useful addition to the infrastructure...

Feb 10, 2010 at 4:26 PM
OK.

Are you guys accepting patches from non-ms personnel?

If so.....

Are the order in lists (Typedefinition.Members, Namespace.Members, etc) garanteed to be always the same for a given assembly (assuming same version of the assembly)?



On Wed, Feb 10, 2010 at 5:26 PM, hermanv <notifications@codeplex.com> wrote:

From: hermanv

I'm afraid not. It would be a very useful addition to the infrastructure...

Read the full discussion online.

To add a post to this discussion, reply to this email (ccimetadata@discussions.codeplex.com)

To start a new discussion for this project, email ccimetadata@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com


Coordinator
Feb 10, 2010 at 4:45 PM

We do welcome contributions from the community. If you contribute a patch, please include a text file in the patch that states that you contribute the code under the terms of the Microsoft Public License (see the project's License tab for details of the license).

Regular contributors (people who get to check in) are asked to sign an agreement, to the same effect, which cuts down on the red tape per check in.

The order of the AllTypes collection and individual collections such as Methods, Fields and Properties do preserve the order that they appear in metadata, when using PeReader to construct an object model.

I would be wary, however, of basing a design on the assumption that order is maintained, especially since a feature like this might be useful to relate members from one version of an assembly with their equivalents from another version.

Feb 10, 2010 at 4:51 PM
Where should a discussion be held on the exact requirements of this feature?


On Wed, Feb 10, 2010 at 6:46 PM, hermanv <notifications@codeplex.com> wrote:

From: hermanv

We do welcome contributions from the community. If you contribute a patch, please include a text file in the patch that states that you contribute the code under the terms of the Microsoft Public License (see the project's License tab for details of the license).

Regular contributors (people who get to check in) are asked to sign an agreement, to the same effect, which cuts down on the red tape per check in.

The order of the AllTypes collection and individual collections such as Methods, Fields and Properties do preserve the order that they appear in metadata, when using PeReader to construct an object model.

I would be wary, however, of basing a design on the assumption that order is maintained, especially since a feature like this might be useful to relate members from one version of an assembly with their equivalents from another version.

Read the full discussion online.

To add a post to this discussion, reply to this email (ccimetadata@discussions.codeplex.com)

To start a new discussion for this project, email ccimetadata@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com


Coordinator
Feb 10, 2010 at 4:59 PM

This seems to be that discussion. ;-)

Your e-mail client seems to be fond of repeating everything, so please consider using the Web interface to keep the thread readable.

Feb 10, 2010 at 5:04 PM
Rgarding the repeating: that's me being too lazy to remove it..

What kind of data structure can be used as the identifier? a string? This is easiest to make from a "Give ID" point of view, but is very slow when looking up by the id.