matt cole wrote: I have a situation where I have a class which I would like to be visible within its assembly, but only to be able to be created by a single other class. Create an interface representing the functionality of the first class. Have the first class implement that functionality as a private class to the second class: public interface ISomeInterface { void DoSomething(); } public class MyClass { private class MyPrivateClass : ISomeInterface { public void DoSomething() { // Do stuff here... } } public ISomeInterface Create(); { return new MyPrivateClass(); } } Maybe not exactly what you're looking for; you have the interface in your namespace which may not be implemented any where else, but that may not be a problem.

Yeah my actual code does deal with it as a stream but it generates the same string as the Image.Save(memoryStream) method. Basically I'm using a third party charting component which has a save method which is able to save to a stream, I assume it uses the same method as the Image.Save does as it generates the same base64 string. I was hoping if i could get to the bottom of the reason I am getting two different strings I could take that solution to my actual code. I can see now that the string is exactly the same, except the file IO method has more bytes on the end that are missing from the other method.

Thanks Jon, That works perfectly :)

I have Xml File like the follwing : 1220200054 Chetan Ranpariya IT Ahmedabad and I had a .xsd file for that in which I set the datatype for "RegNo" as "long" and set it as a primary key column. Now problem is when ever I tried to ented text data int RegNo the error is given. It's Ok. But if I enter duplicate value in RegNo field then it does not give any error and accepts data. So how can I make primary to work like in sql, and access. Can any one help me? Thanks in advance for help. Chetan Ranpariya

Not possible. Because of the Common Type System (CTS) - part of the .NET Framework - the type must be known at compile time or the necessary IL instructions cannot be emitted as part of the module that gets embedded into the primary assembly. The best alternative is to develop a base class from which all of your loaded types (common, especially in plug-in style applications) and cast to that base class, relying on polymorphism to define your distinct types' functionality (that derive from that base class, of course). Microsoft MVP, Visual C# My Articles

lol dagnammit :) i didn't think so but thought i'd check.