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
The SDK support for publishing .net core apps as a single-file generates bundles with unique IDs every time. This behavior is by design, so that files from apps with different build configurations/versions do not get their extracted files mixed up.
However, in some circumstances, the user may want to re-generate bundles with the same ID for testing purposes. So add a facility to facilitate this behavior.
In this case, it is the user's responsibility to clean out extracted files before using the new build with the same ID -- otherwise files previously extracted will be reused.
The text was updated successfully, but these errors were encountered:
The SDK support for publishing .net core apps as a single-file generates bundles with unique IDs every time. This behavior is by design, so that files from apps with different build configurations/versions do not get their extracted files mixed up.
However, in some circumstances, the user may want to re-generate bundles with the same ID for testing purposes. So add a facility to facilitate this behavior.
In this case, it is the user's responsibility to clean out extracted files before using the new build with the same ID -- otherwise files previously extracted will be reused.
The SDK support for publishing .net core apps as a single-file generates bundles with unique IDs every time. This behavior is by design, so that files from apps with different build configurations/versions do not get their extracted files mixed up.
However, in some circumstances, the user may want to re-generate bundles with the same ID for testing purposes. So add a facility to facilitate this behavior.
In this case, it is the user's responsibility to clean out extracted files before using the new build with the same ID -- otherwise files previously extracted will be reused.
The text was updated successfully, but these errors were encountered: