[Uno Features][Docs] Complete List of available uno features?

[DevTKSS]

Would be cool if we would have a complete list of available UnoFeatures, not limited to the uno.extensions repo provided extensions like auth.

I did notice the uno.sdk project having a UnoFeatures.cs file which contains a lot more available names we might be able to use. As example: ExtensionsCore would be helpfull to know about as I am currently everywhere I am needing the Uno.Core.Extensions.Collections.Specialized Package manually and now it seems like the Uno.Sdk would have been able to do this for me the whole time?

[jeromelaban]

Thanks for the question.

We've documented the entries that are meaningful to users overall, sub features are not necessarily needed. About Uno.Core, it's not referenced by uno.sdk at all, you'll need to take a dependency through a normal package reference.

[jeromelaban]

What is the difference that we use the UnoFeatures in our csproj to get the Uno.Extensions provided things right from the sdk but we can not get the other ones? I mean, that the "old" Samples do use them, makes me think, there might be a good reason Uno had in mind, to not longer do this?

Can you tell which other ones?

[DevTKSS]

@jeromelaban mainly I would miss this

uno/src/Uno.Sdk/UnoFeature.cs

Line 46 in df246eb

ExtensionsCore,

to be mentioned as available somewhere, but generally I could think of, that for other Users the items Attributed with [ UnoArea(UnoArea.Core)] could be also interesting.
I would assume, that the ExtensionsCore would provide the Uno.Core.Extensions.Collections.Specialized Package without the PackageReference, just by using the Feat name

[DevTKSS]

checked right now, which of the tree packages exactly this function included:

https://github.com/unoplatform/uno/blob/df246eb5d53680d043ebeb2757e5131b915d60fc/src/Uno.Foundation/Uno.Core.Extensions/Uno.Core.Extensions/StringExtensions.cs

its the JoinBy coming from the <PackageVersion Include="Uno.Core.Extensions" Version="4.1.1" /> I am using for example and at work where I develop a library proj. solution, I am additionally using the <PackageVersion Include="Uno.Core.Extensions.Collections" Version="4.1.1" /> for the functions ForEach and Do on the Enumerables and so on. In my opinion those are very usefull for Library Projects and I would love to see them not requiring a PackageReference hopefully, because I readed somewhere that from the v6 release, Uno did improve and now support also Library Projects using the sdk👍

[jeromelaban]

Understood. You're free to add those libraries as you which, as you can for any other libraries, they're simply not part of the uno.sdk at this time.

I'm still getting why it's impacting your project and the use of the devserver. Could you provide more details about that?

[DevTKSS]

Understood. You're free to add those libraries as you which, as you can for any other libraries, they're simply not part of the uno.sdk at this time.

@jeromelaban Maybe you did not understand, what I ment with the Library Projects. Its not about to add them to the uno.sdk or any Uno Repository. I am creating them, like your Team for example is doing the Uno.Extensions, just that my Projects are extending the available functions for the CAD Engineering for example with Autodesk Inventor Software and not WinUI or Microsoft 👍 I currently use the Uno.Sdk only for one of the Projects in this repository for the UnoFeatures provided things like Hosting, Logging etc, because those are defining some ServiceCollectionExtensions I would plan to use for example in future Uno Apps interacting with the Inventor Application v2025 which has the minimum requirement of Net 8.
And for those Projects for example, where I am currently using the PackageReference Import of the Uno.Core.Extensions.Collections manually like this for example:

(I am creating also some Librarys, not specifyed to the Business Logic at work, which is what you see in this image for example)
I as user of the Uno.Sdk would be interested in knowing that the ExtensionsCore Uno Feature does exist, but no one told in the docs => maybe this could get added, alongside with a full list of the Available names which are [UnoArea(Uno.Core)] marked.

But hey 😄 if its a big secret no one should know of, that the Sdk is able to Provide them to our using Projects without maybe this import, lets keep it a secret only few or the team does know of 😄

---

the dev Server problem, I did respond some time ago in the DevServer not connecting in the Studio Feedback Repo, but no one seems interested in the details I provided there, 🤷 unoplatform/studio#68
You could easyily go to this commit DevTKSS/DevTKSS.Uno.SampleApps@0fcb6b1
and see what I did changed and this image of the app runned with the Tutorials-Only slnf did show the issue behaviour. As soon as I did remove the Condidtional Import of the Packages, it did work again just fine. If we would not need to add those Pack

https://github.com/DevTKSS/DevTKSS.Uno.SampleApps/blob/923c108df950e45ac5f50549518485de34e27ff8/doc/articles/images/DevTKSS.Uno.XamlNavigationApp.png

If we would not need to add those Packages of Uno.Core.Extensions, then this would maybe not even be happening.

[jeromelaban]

But hey 😄 if its a big secret no one should know of, that the Sdk is able to Provide them to our using Projects without maybe this import, lets keep it a secret only few or the team does know of 😄

There's no big secret at all. The ExtensionCore feature has nothing about Uno.Core.* it's a value that is not useful to developers and there's no need to document it.

the dev Server problem, I did respond some time ago in the DevServer not connecting in the Studio Feedback Repo, but no one seems interested in the details I provided there, 🤷 unoplatform/studio#68

We need detailed and precise information about an issue, a commit is generally not enough to diagnose an issue.

You could easyily go to this commit DevTKSS/DevTKSS.Uno.SampleApps@0fcb6b1
and see what I did changed and this image of the app runned with the Tutorials-Only slnf did show the issue behaviour. As soon as I did remove the Condidtional Import of the Packages, it did work again just fine.

I took the commit just before DevTKSS/DevTKSS.Uno.SampleApps@2b048c7, and everything's working fine on my side, I was able to run and see the dev server get connected.

In order to repro an issue, we need extensions logs, app logs and steps to repro, we otherwise cannot troubleshoot.