# \[FB 8.6.3666\] dotnet publish is missing portable target runtime

**URL:** <https://www.finalbuilder.com/forums/t/fb-8-6-3666-dotnet-publish-is-missing-portable-target-runtime/7840>\
**Category:** Bugs\
**Created:** [October 26, 2026, 9:31am UTC](https://www.finalbuilder.com/forums/t/fb-8-6-3666-dotnet-publish-is-missing-portable-target-runtime/7840 "2026-10-26T09:31:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tinus](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/tinus/32/33_2.png) [@tinus](https://www.finalbuilder.com/forums/u/tinus)\
**Post date:** [October 26, 2026, 9:31am UTC](https://www.finalbuilder.com/forums/t/fb-8-6-3666-dotnet-publish-is-missing-portable-target-runtime/7840/1 "2026-10-26T09:31:36Z")

</div>

VS 2026 supports a target runtime “portable” setting for publishing framework dependent .Net 10 code. In fact, this setting removes the RuntimeIdentifier from the publish profile.

I can’t use the FB dotnet publish action to replicate this. FB dotnet publish has no entry for “portable” and always forces a specific target runtime.

Please add this setting in FB!

---

<div class="post-metadata">

**Author:** ![tinus](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/tinus/32/33_2.png) [@tinus](https://www.finalbuilder.com/forums/u/tinus)\
**Post date:** [October 26, 2026, 9:43am UTC](https://www.finalbuilder.com/forums/t/fb-8-6-3666-dotnet-publish-is-missing-portable-target-runtime/7840/2 "2026-10-26T09:43:23Z")

</div>

Please ignore this – I’ve just realised that the runtime property can be cleared.