#if DEBUG directive

Question

   #if DEBUG
                        mailMessage = new MailMessage("someEmail.com", "someEmail.com", subject, messsageBody);
   #else
                        mailMessage = new MailMessage(Membership.GetUser().Email, cppAccount.Email, subject, messsageBody);
   #endif

I have the above code but even when I publish on release it still uses the debug statement. This is an mvc4 c# project and this code is in one of my model classes.

My solution configuration is set to release if that's what you mean. In VB it greys out every time I switch the solution configuration. — user2117229, Jun 06 '14 at 21:20
Are you talking about this line in the web.config or do I need to do define it in my web.config? — user2117229, Jun 06 '14 at 21:25
When you publish you can choose a configuration, at least with vs2012, have you set your publish to `Release` in the publish window? — Silvermind, Jun 06 '14 at 21:48
Maybe your Release configuration is set to define the DEBUG constant? Right click your project, Build tab, Set Configuration Dropdown to Release, Ensure that "Define DEBUG constant" is not checked. — Kenneth Ito, Jun 06 '14 at 22:42

score 2 · Accepted Answer · answered Jun 06 '14 at 21:36

2

That is not the best way to do what you are trying. You should do this in web.config with an app setting for example.

<add key="MailMessageEnabled" value="true" />

And then in your cs file do something like -

bool isEnabled = bool.Parse(ConfigurationManager.AppSettings["MailMessageEnabled"]);
mailMessage = isEnabled ? new MailMessage(Membership.GetUser().Email, cppAccount.Email, subject, messsageBody) 
            : new MailMessage("someEmail.com", "someEmail.com", subject, messsageBody);

And you can have the value of the config to be true in default web config and false in release web config

answered Jun 06 '14 at 21:36

MoXplod

3,813
6
36
46

So basically what your saying unlike vb.net the compilier directives don't work very well. Or is this just because I can modify the setting from outside the deployed dll? – user2117229 Jun 09 '14 at 16:43
1

Compiler directives work, but IMO its more flexibility to have the control from outside the DLL than having to recompile everytime you have to test, If you do it this way you can quickly test ON vs OFF by changing the value. – MoXplod Jun 09 '14 at 16:59

score 1 · Answer 2 · answered Jun 06 '14 at 21:43

1

As MoXplod says, you should do that in the web.config file BUT I think it is better to use Transformation so you can have your web.config file for debug with the value that you require for development and in web.Release.config you can have the values that you need in PROD environment. Check http://msdn.microsoft.com/en-us/library/dd465326(v=vs.110).aspx for information about Transformation.

answered Jun 06 '14 at 21:43

rafail

11
1

If I do it in the webconfig it would be done with a transform any way. Like have done before with live and dev apps. Thanks. – user2117229 Jun 09 '14 at 16:41

#if DEBUG directive

2 Answers2