Re: conditional directives

Hi Peter,

This might be relevant to the discussion as well:

http://community.bartdesmet.net/blogs/bart/archive/2006/08/30/4368.aspx

The ConditionalAttribute goes beyond the capabilities of the #define
directive and might be considered useful as well. If you have additional
questions, I'll be more than happy to hear about it.

-Bart

-----Original Message-----
From: Discussion relating to the specifics of the C# and Managed C++
languages [mailto:[email protected]] On Behalf Of Peter Osucha
Sent: donderdag 15 maart 2007 13:56
To: [email protected]
Subject: Re: [DOTNET-CX] conditional directives

Brady,

Yes, once it becomes clear why you are using them.  The answers to my
question Dino and Bart gave have made this clearer to me.

Peter

-----Original Message-----
From: Discussion relating to the specifics of the C# and Managed C++
languages [mailto:[email protected]] On Behalf Of Brady
Kelly
Sent: Thursday, March 15, 2007 8:30 AM
To: [email protected]
Subject: Re: [DOTNET-CX] conditional directives

Peter Ouscha:

> Anyway, I have a need with my current development to limit some
> functionality while running from the IDE.  I figured I could use
> '#if..." to do such a conditional thing.  But there are a few things I
> don't understand about doing this.  If I have these #define IDE
commands
> all over my files, before a release build, I'd have to remove them,
> correct (which seems like a pain)?  Is there a better way to
> conditionally skip some things while running from the IDE?

Isn't that the point of these directives?  You shouldn't have to remove
them
when you change the conditions they depend on.

===================================
This list is hosted by DevelopMentor.  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com