1

I have written a Visual Studio C# project and I have the need to create two executable, one for a "lite version" and one for a "full version" of the same project.

The "lite version" will be a stripped down version of the full one so I want to share everything (code, resources, etc.) and, if possible, use compiling directive to isolate code blocks.

Can you tell me a way to do this in a clean way?

DreamOfMirrors
  • 2,147
  • 1
  • 21
  • 34
  • I suggest you think of other ways to do this. It would take very little effort to decompile your code to avoid your compile directives. Just a fair warning before you go to the hasle of actually trying to do this. – Security Hound Aug 27 '12 at 14:56
  • 1
    To be honest, with a compile directive I want the compiler not to compile some lines or files so there is no way to discover "the full code" because "the full code" is part only of the "full version" binary (distributed elsewhere). – DreamOfMirrors Aug 27 '12 at 15:01
  • Even if do implement BigYellowCactus's solution the code will still be there. – Security Hound Aug 27 '12 at 16:44

3 Answers3

2

You can create a new Conditional compilation symbol in your project (say FULLVERSION). Create a new Solution configuration (say ReleaseFullversion) using the Configuration Manager, and in this configuration, define the FULLVERSION constant.

You can then wrap code block with

#if FULLVERSION
 ...
#end if

or use the Conditional atrribute

[Conditional("FULLVERSION")]
void MyMethod()
{...}

to create a stripped down version your application.

Code within these #if-blocks and these Conditional attributes won't be compiled into your assembly if the FULLVERSION constant is not set (the Conditional attributes just removes the call to that code block, actually).

Then you would either build a lite version of your solution, or a Fullversion, which includes the full code.

sloth
  • 99,095
  • 21
  • 171
  • 219
  • This looks the best solution but I see a little problem: how can I conditionally change the binary name, icon, description, etc. in this way? – DreamOfMirrors Aug 27 '12 at 15:19
  • Have a look [here](http://stackoverflow.com/questions/893003/change-assembly-name-based-on-configuration-visual-studio-2005-2008) – sloth Aug 27 '12 at 15:20
  • Or [here](http://stackoverflow.com/questions/208084/how-to-use-a-different-assembly-name-for-different-configurations) – sloth Aug 27 '12 at 15:20
  • For icons, see [here](http://stackoverflow.com/questions/6612363/how-do-i-set-different-application-icon-for-different-configurations) – sloth Aug 27 '12 at 15:22
1

You can use Visual Studio Post Build events, where from the batch call DEVENV.EXE to your project with some special parameter that makes it compile in a different way.

DevEnv explanation

Using Devenv at the command prompt to build projects

Tigran
  • 61,654
  • 8
  • 86
  • 123
1

To do this all within visual studio, you require something of a strange ritual that is a little non-obvious to anyone simply looking at your project, so it is important to figure out a training regimen to make sure everyone knows what is going on.

First, right-click on the solution you have and go to properties. Click on "Configuration Manager" and make a new configuration. Call it "Lite" or whatever pleases you.

You may then right-click each project in your solution to set the conditional compilation properties you need. You may then use Conditional Compilation Symbols to isolate what is 'full' and what is 'lite'.

After this has been fully configured, it will appear in the top of visual studio's UI - where you normally see Debug and Release, you will now see Lite or whatever you just configured.

tmesser
  • 7,558
  • 2
  • 26
  • 38