I've written a UITypeEditor and it works when the editor lives in the same assembly (or one of the referenced assemblies) as the types using it. Then I can use something like:







However, I'd like to move this to a separate assembly, one that is not referenced by the assemblies with types that use it, because I don't want to have to distribute the code that is solely to for the VS designer. I know this can be done, as SF does this quite nicely. I've attempted to figure out how it was done (looked at SF code) and then I tried this:







with the extensibility assembly copied into the bin\debug folder with the main project. No joy.



How is this done? What am I missing? Can this be done if the assembly isn't strong-named?

I'm a bit slow. This is like the 100th time this has been explained to me, but with this post, the light bulb finally went off. I had another question and Paul explained how to do this exact thing, but I didn't quite get it. Then I realized that I needed a separate solution for the extensibility project (duh!) (not strictly required, but then it is just setup and ready to go) and it all made more sense and I got it to work!



Here is Paul's post that explains how to actually do what Trent just said!



http://forum.strataframe.net/FindPost24961.aspx

Guess that comes with the aging process



It is happening to me more frequently

Edhy Rijo

I prefer to think of my aging process as something more like fine wine, just getting better with age....



My mother used to say senility was hereditary....you get it from your kids! I'm starting to believe her (I have a 13yr old daughter...and the gray hairs are multiplying!).



Oh, and fortunately, for y'all, no web cams were present during the jig!