The Mobile.BuildTools makes it easier to develop code bases in a clean, consistent, secure, and configurable way. Determine at Build which environment your app needs to run on, and what Client Secrets it should have. Plus many more amazing features!
There is currently a pretty loose connection between Mobile.BuildTools and Mobile.BuildTools.Configuration. This kept all of the build props/targets as part of the Mobile.BuildTools... it also results in a pretty annoying inclusion of the app.config on the iOS/Android project even when the file does not exist. This updates the props so that it is now part of the Configuration project, and you will only get the Include when you actually have the Configuration package referenced.
There isn't really anything I can do for the file showing up. The legacy project sdk's for Android/iOS aren't as capable of dynamic includes like the newer MSBuild Sdks
Description
There is currently a pretty loose connection between Mobile.BuildTools and Mobile.BuildTools.Configuration. This kept all of the build props/targets as part of the Mobile.BuildTools... it also results in a pretty annoying inclusion of the app.config on the iOS/Android project even when the file does not exist. This updates the props so that it is now part of the Configuration project, and you will only get the Include when you actually have the Configuration package referenced.
There isn't really anything I can do for the file showing up. The legacy project sdk's for Android/iOS aren't as capable of dynamic includes like the newer MSBuild Sdks