You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you're currently using a nightly build, your current configuration will break when you update to the next nightly build.
Despite the name, the nightly build is unlikely to happen for a few days so consider this a warning.
If you have customized profiles, you are advised to export them so they are not lost. You may need to manually re-enter them after the update though. Please let me know if this is going to cause you a big problem. (Comment below and I'll see what I can do to help.)
The reason this is happening is part of the changes made for #150.
When these changes are released, they will
remove the need to configure an active profile before using the generation functionality. (This is to help the OOB experience.)
allow setting different active profiles for UWP, WPF, and Xamarin.Forms. (Useful if you use more than one of them so you don't need to keep changing the active profile.) This will be possible because
Automatically detect which type of project you're working on and so chose the appropriate profile.
Allow setting a "fall back" profile which will be used if it's not possible to determine which profile to use. (Yes, you can set the fallback as an active profile.)
Sorry that this is being announced in this way, but there is currently no other method of communicating with people who may be using the nightly builds. Hopefully, you will all see this in time.
The text was updated successfully, but these errors were encountered:
If you're currently using a nightly build, your current configuration will break when you update to the next nightly build.
Despite the name, the nightly build is unlikely to happen for a few days so consider this a warning.
If you have customized profiles, you are advised to export them so they are not lost. You may need to manually re-enter them after the update though. Please let me know if this is going to cause you a big problem. (Comment below and I'll see what I can do to help.)
The reason this is happening is part of the changes made for #150.
When these changes are released, they will
Sorry that this is being announced in this way, but there is currently no other method of communicating with people who may be using the nightly builds. Hopefully, you will all see this in time.
The text was updated successfully, but these errors were encountered: