Acessing TypeConverters in a separate Assembly

[Bob Powell [MVP]]

Try strong-naming your assembly and putting it in the GAC on the design
machine and using the form of the attribute that takes a type instead of a
string.
--
--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

Hi,
I am developing some components that make use of Visual Studio's DTE
services for their type converters. They all work nicely when the type
converters are located in the same assembly as the components themselves.
For obvious reasons I want to have the TypeConverters in a separate
design-time assembly that I don't deploy to the final application. In
theory
this should all be straight-forward if I decorate the respective property
[TypeConverter("Autag.M9.Design.DataContextNameConverter,
Autag.M9.Design")]
however, it does not appear to be able to get a hold of the
Autag.M9.Design
assembly, presumably its location or existance is not known to the
environment at that point in time.
My question is: How do I install/make the design time assembly known to
the
environment?
----
Martin

[MartinK]

Post by Bob Powell [MVP]
Try strong-naming your assembly and putting it in the GAC on the design
machine and using the form of the attribute that takes a type instead of a
string.

But doesn't that mean that I need to have a reference to the design
assembly? That's just what I want to avoid...

[Bob Powell [MVP]]

Well, ok, use the fully qualified name of the assembly in the string then.
--
--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

Post by MartinK

Post by Bob Powell [MVP]
Try strong-naming your assembly and putting it in the GAC on the design
machine and using the form of the attribute that takes a type instead of
a string.

But doesn't that mean that I need to have a reference to the design
assembly? That's just what I want to avoid...