That's what I was looking for. I seem to recall seeing those constants in the SF source, so I can use those to get started (obviously pointing to my extensibility assembly of course).



Thanks!

Well, this is one of those things that we could spend a lot of time on, but here are a few tips.

1. Your Extensibility project will reference your UI assemblies, etc. but your UI assemblies WILL NOT reference the extensibility.
2. When assigning a type editor to a property within a class in your UI assembly, you will want to use a constant defined somewhere within your UI assembly that has the full name to the assembly and class that you want to use.  This prevents the need to the reference within the UI assembly to the Extensibility assembly.

Basically if you follow these two rules (which were the hardest to get through our heads initially) you will be in good shape.

I've done a couple of type converters and am now thinking about trying a UITypeEditor. None of this code needs to be distributed though, so I'm thinking about putting it into an extentibility project. However, I'm unclear how references/distribution work. I know that it can be done, as SF does this...just not sure how. How does this work? (The referencing of an extensibility project so it's available at design time, but not required to be distributed.)