Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Configure Debug Flag

See original GitHub issue

So 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 GitHub Comments

1reaction

jeancroycommented, Feb 25, 2022

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.