Configure Debug Flag
See original GitHub issueSo the Azure Deployment Center, configured with a Github Source seems to use this script running on Github action to build app before using zip deploy.
My issue is that asp.net application built this way seems to have the debug flag on.
As in #if (Debug) .. #endif
preprocessor directive.
It doesn’t seem to be a slot setting, and it doesn’t seem to be aware of web.config > system.web>compilation>debug
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
GNU autotools: Debug/Release targets? - Stack Overflow
PS: I've read about the --enable-debug flag/feature, but in my current (simple) setup, using that is unrecognized by configure.
Read more >20.9 Debugging configure scripts - Autoconf - GNU.org
Debugging configure script execution may be done by sprinkling pairs of set -x and set +x into the shell script before and after...
Read more >Debugging flags usage in the configuration file (INI)
Below are valuable flags for debugging purposes which you can add to the INI file by adding them under the [MAGIC_ENV] section. ......
Read more >Set debug and release configurations - Visual Studio (Windows)
On the toolbar, choose either Debug or Release from the Solution Configurations list. toolbars build configuration. or · From the Build menu, ...
Read more >Set Up Debug Logging - Salesforce Help
To activate debug logging for users, Apex classes, and Apex triggers, configure trace flags and debug levels in the Developer Console or in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes I had same file as aspnet-windows.config.yml except for placeholder like
__sitename__
, they have been filled in.I was able to fix my issue by adding
/p:Configuration=Release
At the end of
run: msbuild /nologo /verbosity:m /t:Build /t:pipelinePreDeployCopyAllFilesToOneFolder /p:_PackageTempDir="\published\"
This follow same logic as dotnetcore-windows.config.yml
Where release is forced using
dotnet build --configuration Release
It is also the recommended usage for release on setup-msbuild
Without forcing the flag the configuration comes from .csproj file. But my csproj default to debug, this my dev env preference, not my deploy preference.
I think that not forcing the release may be a bug. I also think it’s harmless to force it, and it is done for some of your other actions. It was also the previous behavior when things where built on azure instead of github actions.
Closing the issue, feel free to create new issue.