New Development configuration where interpreter and XAML Hot Reload etc. are enabled, and Debug configuration is like Release

[janne-hmp]

.NET MAUI is currently using an interpreter for Debug build as default, which can potentially lead to large differences in the program behavior between Debug and Release configurations. Debug configuration should follow Release configuration as closely as possible, so that potential bugs in Release can be weeded out early. If the Debug configuration works very differently than Release, it sort of partly negates the point of the debug, at least for complicated errors arising from exact way the configuration is built, and as a way to ensure that Release configuration is stable if Debug is stable.

However, the goal of making the development quick via using interpreter, XAML Hot Reload etc. is understandable, but perhaps all such new features should be moved to a new configuration, which could be termed Development or something like that. Debug in turn should be as much like Release as possible.

[phillippschmedt]

@janne-hmp Ongoing discussion regarding the interpreter is here: #13019

[jonathanpeppers]

This idea is probably not very maintainable unless we had this feature in the .NET SDK:

• Better support for non-standard $(Configuration) names sdk#31918

We need a way to define a Debug-like configuration vs a Release-like configuration.

[janne-hmp]

There would be also a need for Publish configuration on iOS which would be like Release but signed with Apple Distribution provisioning profile, while Release would be signed with Apple Development provisioning profile to allow for testing on local devices.