-1

Please consider the following scenario: I have a C++ file and we call that C++ code from the C#. In C++ file, there is a flag

#define HasFeature

I would like this flag to be undefined in the production code, and in only my test code I want to activate them. After the finalization of the test, I want it to be undefined again.

I know it is a compile-time feature and editing it in runtime won't be possible. I cannot convert the #define to something like class member because of another reason.

One thing that I can think of adding two files, in one of them the flag is defined and one of them the flag is undefined and in test.proj use the file with flag defined and production.proj use the file with flag undefined. Is that possible in Visual Studio? If so how can I do it? (Maybe using some feature in csproj etc.?)

Jonathan Leffler
  • 730,956
  • 141
  • 904
  • 1,278
Barış Akkurt
  • 2,255
  • 3
  • 22
  • 37
  • If a macro is the only option (it isn't) then you must create multiple builds of the project. Add a new configuration beyond the built-in Debug and Release configurations, like "ReleaseProduction". Deploying the correct flavor of the executable file is up to you. – Hans Passant Feb 07 '17 at 13:08
  • What are other options to macro? – Barış Akkurt Feb 07 '17 at 13:17

1 Answers1

0

You can define your flag with a command line parameter in the build:

/p:DefineConstants="HasFeature"

In this way you just need to set this only in your test build and remove this parameter in your production build definition.

GôTô
  • 7,974
  • 3
  • 32
  • 43