How can I tell if I am running in design mode?

[newscorrespondent]

What is the "if" to tell if my code is running in design mode?

Thanks

[Nicholas Paldino [.NET/C# MVP]]

Your component has to be derived from the Component class. From that,
you can check the DesignMode property. If it is true, then you are in
design mode, false otherwise.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

<ne***************@charter.netwrote in message
news:FF*****************@fe03.lga...

>
What is the "if" to tell if my code is running in design mode?

Thanks

[Peter Bromberg [C# MVP]]

newscorrespondent,
Do you mean in ASP.NET as with a Custom Control on a page? If so, then the
HttpContext.Current will be null.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"ne***************@charter.net" wrote:

>
What is the "if" to tell if my code is running in design mode?

Thanks

[Nicholas Paldino [.NET/C# MVP]]

Peter,

That's not a good idea, IMO, since all classes that derive from Control
(in the System.Web.UI namespace) have a protected property called DesignMode
which exposes whether or not the control is hosted in the designer.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Peter Bromberg [C# MVP]" <pb*******@yahoo.nospammin.comwrote in message
news:06**********************************@microsof t.com...

newscorrespondent,
Do you mean in ASP.NET as with a Custom Control on a page? If so, then the
HttpContext.Current will be null.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"ne***************@charter.net" wrote:

>>
What is the "if" to tell if my code is running in design mode?

Thanks

[Peter Bromberg [C# MVP]]

Nick,
This is true but it is not always a complete solution to the potential
problems exposed here. MVP Rick Strahl's blog post illustrates:

http://west-wind.com/weblog/posts/189.aspx

Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Nicholas Paldino [.NET/C# MVP]" wrote:

Peter,

That's not a good idea, IMO, since all classes that derive from Control
(in the System.Web.UI namespace) have a protected property called DesignMode
which exposes whether or not the control is hosted in the designer.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Peter Bromberg [C# MVP]" <pb*******@yahoo.nospammin.comwrote in message
news:06**********************************@microsof t.com...

newscorrespondent,
Do you mean in ASP.NET as with a Custom Control on a page? If so, then the
HttpContext.Current will be null.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"ne***************@charter.net" wrote:

>
What is the "if" to tell if my code is running in design mode?

Thanks

[Bruce Wood]

Nicholas Paldino [.NET/C# MVP] wrote:

Your component has to be derived from the Component class. From that,
you can check the DesignMode property. If it is true, then you are in
design mode, false otherwise.

I should add that DesignMode is set only after your control has a
context handle in the designer, so in your constructor code it will
always be false, whether you are in the designer or not.

If there is code that you don't want run in design mode then you should
put it in your OnLoad method, where the DesignMode property does have a
valid value.

[Peter Bromberg [C# MVP]]

Bruce,
The issue I've come across with this - beside the fact that the property
doesn't exist in the ASP.NET 1.1 Framework -- is that if you have a
ServerControl that relies on the HttpContext to render it's DesignTimeHtml
(such as making an HttpWebRequest) then it would blow up in the designer even
though functioning perfectly well at runtime. Rick's blog post which I
referenced below solves this problem.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Bruce Wood" wrote:

>
Nicholas Paldino [.NET/C# MVP] wrote:

Your component has to be derived from the Component class. From that,
you can check the DesignMode property. If it is true, then you are in
design mode, false otherwise.

I should add that DesignMode is set only after your control has a
context handle in the designer, so in your constructor code it will
always be false, whether you are in the designer or not.

If there is code that you don't want run in design mode then you should
put it in your OnLoad method, where the DesignMode property does have a
valid value.

[Bruce Wood]

Peter wrote:

The issue I've come across with this - beside the fact that the property
doesn't exist in the ASP.NET 1.1 Framework -- is that if you have a
ServerControl that relies on the HttpContext to render it's DesignTimeHtml
(such as making an HttpWebRequest) then it would blow up in the designer even
though functioning perfectly well at runtime. Rick's blog post which I
referenced below solves this problem.

Sorry. I should have been more specific. I was talking WinForms.

[Peter Bromberg [C# MVP]]

Yep,
This is a constant problem here - people sometimes referring to ASP.NET
issues and not being explicit about it, and posting to the C# language group
because they are programming in C# (a good thing!) - and some even
programming in VB.NET (potentially also a good thing, with some provisos).
Cheers,
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Bruce Wood" wrote:

Peter wrote:

The issue I've come across with this - beside the fact that the property
doesn't exist in the ASP.NET 1.1 Framework -- is that if you have a
ServerControl that relies on the HttpContext to render it's DesignTimeHtml
(such as making an HttpWebRequest) then it would blow up in the designer even
though functioning perfectly well at runtime. Rick's blog post which I
referenced below solves this problem.

Sorry. I should have been more specific. I was talking WinForms.