-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fat Portable apps not publishing native assets. #559
Comments
@ramarag Please clarify with full repro steps and spell out which files you expect to be somewhere that aren't. |
when the app is published: bin\debug<tfm>\publish<managed_assets> that is |
This works already. Native assets go to |
…RYPOINT for Self Contained Builds * Fixed existing integration test that tested that ContainerEntryPoint can be deferred (it wasn't actually testing anything, due to a bug in the test) * Changed the test to test that we defer ContainerAppCommand instead (ContainerEntryPoint is not deferred anymore on .net 8) * Added runtime identifier dimension to the test (linux vs windows) * Fixed integration test ProjectInitializer to take into account Windows vs *nix when setting executable extension (.exe or nothing) * Fixed Microsoft.NET.Build.Containers.targets so that the behaviour is as expected on both Windows and linux containers
…RYPOINT for Self Contained Builds * Fixed existing integration test that tested that ContainerEntryPoint can be deferred (it wasn't actually testing anything, due to a bug in the test) * Changed the test to test that we defer ContainerAppCommand instead (ContainerEntryPoint is not deferred anymore on .net 8) * Added runtime identifier dimension to the test (linux vs windows) * Fixed integration test ProjectInitializer to take into account Windows vs *nix when setting executable extension (.exe or nothing) * Fixed Microsoft.NET.Build.Containers.targets so that the behaviour is as expected on both Windows and linux containers
…RYPOINT for Self Contained Builds * Fixed existing integration test that tested that ContainerEntryPoint can be deferred (it wasn't actually testing anything, due to a bug in the test) * Changed the test to test that we defer ContainerAppCommand instead (ContainerEntryPoint is not deferred anymore on .net 8) * Added runtime identifier dimension to the test (linux vs windows) * Fixed integration test ProjectInitializer to take into account Windows vs *nix when setting executable extension (.exe or nothing) * Fixed Microsoft.NET.Build.Containers.targets so that the behaviour is as expected on both Windows and linux containers
…RYPOINT for Self Contained Builds * Fixed existing integration test that tested that ContainerEntryPoint can be deferred (it wasn't actually testing anything, due to a bug in the test) * Changed the test to test that we defer ContainerAppCommand instead (ContainerEntryPoint is not deferred anymore on .net 8) * Added runtime identifier dimension to the test (linux vs windows) * Fixed integration test ProjectInitializer to take into account Windows vs *nix when setting executable extension (.exe or nothing) * Fixed Microsoft.NET.Build.Containers.targets so that the behaviour is as expected on both Windows and linux containers
If we publish a fat portable app, we expect the rids specified in the project to be published under rid split folders in the app bin directory.
This bug is present in both project.json based cli and msbuild based cli
dotnet --info
cc @schellap @gkhanna79 @livarcocc @nguerrera @dsplaisted @eerhardt @piotrpMSFT @srivatsn
Sample project.json :
The text was updated successfully, but these errors were encountered: