release

I've encountered the following paragraph: “Debug vs. Release setting in the IDE when you compile your code in Visual Studio makes almost no difference to performance… the generated code is almost the same. The C# compiler doesn’t really do any optimization. The C# compiler just spits out IL… and at the runtime it’s the JITer that does all the optimization. The JITer does have a Debug/Release mode and that makes a huge difference to performance. But that doesn’t key off whether you run the Debug or Release configuration of your project, that keys off whether a debugger is attached.” The source

Possible Duplicate: How to tell if a .NET application was compiled in DEBUG or RELEASE mode? I'm sure this has been asked before, but google and SO search failed me. How can I identify if a DLL is a release build or debug build? this. __curious_geek The only best way to do this is to check the compiled assemblies itself. There is this very useful tool called '.NET Assembly Information' found here by Rotem Bloom. After you install this, it associates itself with .dll files to open with itself. After installing you can just double-click on the Assembly to open and it will give you the assembly

I'd like to publicate my app to GooglePlay but first i would like to do a last testing with the signed apk to ensure that all of the used API keys are working correctly with the release version (GMaps, Facebook, etc) So i just made a signed version of my app with our release key and when i try to install the app to the device i got an error: I have tried to copy the apk to the device and install it with an apk installer app. Strange thing is when i do the same process with debug signing key, all is well, I can install and run the app. Here are the steps of the procedure: I select the release

I think it's better to release the version of the software which your developers actually tested; I therefore tend to delete the 'debug' target from the project/makefile, so that there's only one version that can be built (and tested, and debugged, and released). For a similar reason, I don't use 'assertions' (see also Are assertions always bad? ...). One person there argued that the reason for a 'debug' version is that it's easier to debug: but, I counter-argued that you may eventually want to support and debug whatever it is you released, and so you need to build a release which you can if

I am making an app that processes sensitive credit card data. If my code is running in debug mode I want to log this data to the console and make some file dumps. However on the final appstore version (ie when it is running in release mode) it is essential all of this is disabled (security hazard)! I will try to answer my question as best I can; so the question becomes 'Is this solution path the right or best way to do it?' // add `IS_DEBUG=1` to your debug build preprocessor settings #if( IS_DEBUG ) #define MYLog(args...) NSLog(args) #else #define MYLog(args...) #endif Damo Check your project