User Control messes designer when used in other projects

P

pompair

Hello,

I've a VS 2005 solution that contains a few User Controls. The project
originated in VS 2003 .NET and was transformed into VS 2005. Some of
the user controls have been written in VS 2005 and some date back to VS
2003 .NET era.

There's also a tester app within the UserControl -dll, that works
perfectly with the user controls.
The PROBLEM arises when I'm trying to use the control in other
projects, outside the user control solution.

First, things work ok in the app I insert the user control to. But then
there are two possibilities:

1) If I save the current project and come back to it, designer is
messed up stating:

**********************************
at System.ComponentModel.ReflectPropertyDescriptor.SetValue(Object
component, Object value)
at
System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializeAssignStatement(IDesignerSerializationManager
manager, CodeAssignStatement statement)
at
System.ComponentModel.Design.Serialization.CodeDomSerializerBase.DeserializeStatement(IDesignerSerializationManager
manager, CodeStatement statement)
**********************************

or 2) When I make a change into the user control and re-insert it into
a app, then the app's designer suddenly breaks down stating the same
error as in option 1.

This is really annoying. Is there a fix for this? I mean, to be able to
re-use your user controls is the point why people makes them.

-pom-
 
P

pompair

Found the error myself. There was uninitiated public property in the
UserControl.

-pom-
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top