Overloaded Constructor Problem

Question

I am having a problem compiling code that instantiates a common custom object (CommonClass) with an overloaded constructor. One of the available constructors takes a custom object as an input parameter (SomeObject). The problem is that when I try to compile code that uses the CommonClass but does not have a reference to the dll for the SomeObject I get a compile error stating that a reference is missing even when the application is not using the constructor with the the SomeObject input parameter. I am new to C#. Is there some modifier I am missing which will allow apps to use my CommonClass without having a reference to the SomeObject dll? When I build the solution for the application the SomeObject dll is copied down to the bin folder which does not present a problem I just do not want the users of my CommonObject to have to set a reference to the SomeObject when they have no intention of using it. //Call CommonClass oCommonClass = new CommonClass(); //Common Constructors public CommonClass() : base() { } public CommonClass(SomeObject object) : base() { }

gasmith.fla · Answer

So far users have just been adding the refererence. I was hoping that I was overlooking something that would not require them to set the reference being it was not directly used. The frustrating thing is that the dll for the unused object is being included in the application's bin folder when the app is built even though the object was never directly used. Thanks anyway.

bilnaad · Answer

Then I think the only thing you can do is place the SomeObject class in the same project as the CommonClass. This way you won't have that problem. It's unwise to spread shared objects over several libraries.

gasmith.fla · Answer

The SomeObject dll is common code used by several applications and has 2 constructors one with no input parameters and one that has another object as an input parameter. The problem that I am having is that when some applications want to use the SomeObject dll using the constructor that does not require an input parameter their application will not compile because they have not explicitly set a reference to the object that is an input parameter for SomeObject for the constructor they are not using. Users are forced to explicitly add a reference to the object in the SomeObject constructor that requires an input parameter even though they are using the constructor which does not require any parameter.

bilnaad · Answer

I don't understand the question well. I read it 4 times and I don't have a clue what the real problem is... Do you want to use a dll without a reference? Why would the 'user' mich not use SomeObject? Who is the user? If SomeObject is just a class and nothing very special why not just declare the class in the same project?

gasmith.fla · Answer

That is the way I have it I am sorry I was not clear in the post. SomeObject is the Type and object refers to the name. Actually it should read (SomeObject oName) All is well if I have a reference to the SomeObject dll in the application code even if it is not used. I do not want users to have to set the reference if they have no intent on ever using SomeObject. I appologize for the bad naming in my example.

bilnaad · Answer

Try to switch 'SomeObject object' to 'object SomeObject' First declare the type and then the variable ^_^