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
It's a common pattern in .NET apps for one "app" to contain several projects. Like this test fixture. Often, when users first attempt to build these apps with buildpacks, they struggle to correctly use BP_DOTNET_PROJECT_PATH and set the build context for their build (e.g. with pack build myimage --path to/src). Users may mistakenly:
not set BP_DOTNET_PROJECT_PATH, making it ambiguous which project they wish to build
It would be a better user experience if the buildpack provides better advice to users about whether to adjust their build context and/or change the value of BP_DOTNET_PROJECT_PATH.
Possible Solution
Motivation
The text was updated successfully, but these errors were encountered:
Describe the Enhancement
It's a common pattern in .NET apps for one "app" to contain several projects. Like this test fixture. Often, when users first attempt to build these apps with buildpacks, they struggle to correctly use
BP_DOTNET_PROJECT_PATH
and set the build context for their build (e.g. withpack build myimage --path to/src
). Users may mistakenly:BP_DOTNET_PROJECT_PATH
, making it ambiguous which project they wish to buildBP_DOTNET_PROJECT_PATH
to the wrong proj fileIt would be a better user experience if the buildpack provides better advice to users about whether to adjust their build context and/or change the value of
BP_DOTNET_PROJECT_PATH
.Possible Solution
Motivation
The text was updated successfully, but these errors were encountered: