Makes ConditionalAttribute can make attributes and methods remove from compilation, work as #if

[Flithor]

// debug only method. and this method won't exists in release binary file
[Conditional("DEBUG", RemoveFromCompilationWhenMissing = true)]
public void DebugMethod()
{
  // Do something in debug mode
}

// usage:
testObj.DebugMethod(); // the line won't compile to binary file

//it's works as:
#if DEBUG
// defination
public void DebugMethod()
{
  // Do something in debug mode
}
// invoking
testObj.DebugMethod();
#endif

It can make the conditional compilation code more concise, avoiding a lot of #if-endif blocks in code.
Can also prevent the implementation related to it from being compiled into the binary file.

[timcassell]

This attribute already exists. https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.conditionalattribute?view=net-9.0

I guess the only difference is you also want the method itself to be removed from compilation.

[Flithor]

Usually, debug output code may bring potential risks (such as unauthorized access, data leakage, etc.), so it is best not to include the debug code in the released binary file.

[Flithor]

Opps.. I just noticed that I typo the attribute name in the title. This attribute is what I'm talking about.

[HaloFour]

Why aren't conditional preprocessor directives sufficient here? They're not verbose. If anything, they're less verbose than this new attribute property you're suggesting.

[Flithor]

@HaloFour

Did you mean to put Debug.WriteLine in your example instead of Console.WriteLine?

However, the Debug.WriteLine method still exists in the released assembly binary file.
Taking this as an example, the ultimate goal is to make Debug.WriteLine disappear from the assembly as well.

[Flithor]

@HaloFour

Feature	Uses	Limitations
#if-#endif	Removed code from compilation	Used multiple times in complex code will be very noisy.
ConditionalAttribute	Removes the usage	Method or attribute still comiled into binary file.
Improved ConditionalAttribute	Remove the usage and declaration code from compilation, and no noise as #if-#endif.	When used on attribute, skip compile attribute may cause namespace missing, then cause compilation error on the using line. (Can be avoid by forcing to use the full name)

[HaloFour]

However, the Debug.WriteLine method still exists in the released assembly binary file.
Taking this as an example, the ultimate goal is to make Debug.WriteLine disappear from the assembly as well.

That might make sense for your own use cases, but the Debug.WriteLine method is part of the runtime. Regardless of what happens here that wouldn't change, that method will always be there.

[Flithor]

@HaloFour

That might make sense for your own use cases, but the Debug.WriteLine method is part of the runtime. Regardless of what happens here that wouldn't change, that method will always be there.

Uh.... I think you totally misunderstood what I meant. I meant that the improved ConditionalAttribute will make the attribute or method to which it is used be remove from compilation just like #if. "Remove Debug.WriteLine" is just an analogy.

[colejohnson66]

One pain point of "preprocessor" conditionals is that the symbol/code is entirely removed — It's not even available in IntelliSense. So, if you want a method to not be present in RELEASE, you must use preprocessor conditionals. But then you have to add preprocessor conditionals around the code that used said method. This means that if you're not careful, a code change might still compile in DEBUG, but fail in RELEASE. Nothing major, but it is an annoyance.

It would be nice if there was a way to have the symbol present, but not present in the compilation.