Discussion:
hiding code from the winform designer
(too old to reply)
RipT
2007-05-12 17:51:01 UTC
Permalink
I have set up an inheritance tree for my winforms (.net2.0) to expose common
functionality. The winform designer in vs2005 will not load these forms
unless the base type has a default constructor (no args).

Right now I'm simply creating a default constructor but its use at run-time
would create an invalid object. At design-time I don't care.

It would be nice if I could throw an exception from this default constructor
at run-time but not at design-time. Or possibly hide the default constructor
from the compiler but not the designer.

Is there a good workaround?
Bryan Phillips
2007-05-13 00:22:31 UTC
Permalink
You can test for design-mode by using the following code:

public InheritanceTree(){
if (this.Site==null || !this.Site.DesignMode){
throw new Exception(""); // Because we are in run-time mode.
}
}

--
Bryan Phillips
MCT, MCSD, MCDBA, MCSE
Blog: http://bphillips76.spaces.live.com
Web Site: http://www.composablesystems.net
Post by RipT
I have set up an inheritance tree for my winforms (.net2.0) to expose common
functionality. The winform designer in vs2005 will not load these forms
unless the base type has a default constructor (no args).
Right now I'm simply creating a default constructor but its use at run-time
would create an invalid object. At design-time I don't care.
It would be nice if I could throw an exception from this default constructor
at run-time but not at design-time. Or possibly hide the default constructor
from the compiler but not the designer.
Is there a good workaround?
Linda Liu [MSFT]
2007-05-14 04:58:42 UTC
Permalink
Hi,

Let's say we have a base form and an inherited form. When the inherited
form is opened in the designer, an instance of the base form is created --
the designer calls the default constructor of the base form to create the
instance and this is why a default constructor is needed.

Generally speaking, we could judge whether it is at design-time or run-time
through the DesignMode property of the form. The DesignMode property
depends on the Site property to determine design-time or run-time (at
run-time, the Site property is null; otherwise, the Site property has a
value).

Note that it's early to judge design-time or run-time using the DesignMode
property in the constructor, because the instance has not finished the
construction and the Site propery has NOT been assigned at this time.

I suggest that you add a public field of type bool in your project to
denote design-time. The default value of this field is false. Set the
field's value to true in the static Main methd. The following is a sample.

class Program
{
public static bool IsDesignTime = true;

[STAThread]
static void Main()
{
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
IsDesignTime = false;
Application.Run(new derivedform());
}
}
public partial class baseform : Form
{
public baseform()
{
if (!Program.IsDesignTime)
{
throw new Exception("this construtor can't be called at run
time!");
}
else
{
InitializeComponent();
}
}
}

Hope this helps.
If you have any question, please feel free to let me know.

Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
Linda Liu [MSFT]
2007-05-16 08:52:55 UTC
Permalink
Hi Rip,

How about the problem now?

If the problem is still not solved, please feel free to let me know.

Thank you for using our MSDN Managed Newsgroup Support Service!


Sincerely,
Linda Liu
Microsoft Online Community Support
RipT
2007-05-18 20:57:01 UTC
Permalink
Thank you for your very thorough reply! I read about and implemented this
approach after referencing other sources, but I was not sure this was the
best solution because no one covered the issue completely. Thanks again!
Post by Linda Liu [MSFT]
Hi Rip,
How about the problem now?
If the problem is still not solved, please feel free to let me know.
Thank you for using our MSDN Managed Newsgroup Support Service!
Sincerely,
Linda Liu
Microsoft Online Community Support
Andreas Ländle
2007-07-18 06:51:51 UTC
Permalink
What about using private/protected default constructors for your
controls/forms?

This is enough for the designer and you can't instantiate the control/form
in runtime via the default constructor.

Best regards,

Andreas Ländle
Post by RipT
Thank you for your very thorough reply! I read about and implemented this
approach after referencing other sources, but I was not sure this was the
best solution because no one covered the issue completely. Thanks again!
Post by Linda Liu [MSFT]
Hi Rip,
How about the problem now?
If the problem is still not solved, please feel free to let me know.
Thank you for using our MSDN Managed Newsgroup Support Service!
Sincerely,
Linda Liu
Microsoft Online Community Support
Loading...