[Docs][Updating][Server] Update the Docs about the provided Server Project from Templates & explain difference between Server and Bootstrapper itself

[DevTKSS]

Which Page: https://github.com/unoplatform/Uno.Wasm.Bootstrap/blob/de09e235be22ce72ec70a0324045f24ccd3f5321/doc/using-the-bootstrapper.md

• As the Uno App Templates are providing the Microsoft.NET.Sdk.Web for the Server Project instead of WebAssebly like this docs page advises us
  there should be some information about:

  • the difference between the Bootstrapper itself and the specification of the *.Server we are getting from this templates at the version 6.x onwards
  • when does this apply to avoid confusement on the reader/user side ("this" implying WebAssembly instead of Web for the Project Management in our csproj

• The Upgrading guide up from Line 21 should then clarify, that the Server from net9 onwards, we need to:

  • Replace eventual old WebAssembly Sdk with Web sdk there, because our Server Project would otherwhise fail on trying to get build.
  • add the now with OpenApi not longer in the AspNetCore Package itself included SwaggerUI/Swashbuckle

Any other Information?

• As soon as I find time in the future, I could add the second part, the updating information, but I think those would make much more sense to add on the General Updating docs, which does indeed point to this page linked above, so I think this is why I thought that both Packages are the same, while the server Package only adds those extensions for the Server Project.
• The Part for the Difference between this Packages, I do not understand myself, so this should maybe then do someone who knows about those parts.

[jeromelaban]

Overall, for now, using the server project is working as it is. There's not much to change aside from the upgrade docs, which is mostly about using a new blank template project and copy the contents.

The Templates are providing the Web instead of WebAssebly and this doc recommends us to do the opposite?

The bootstrapper docs are specific to using the bootstrapper itself without the uno.sdk. There's nothing to change here.

[DevTKSS]

@jeromelaban alright, if them both are not the same, sorry for me not knowing, but it would be greatly helpfull from user side, if there would be any information to the used nuget on the provided server project, and any maybe wasm target related information about the how to use it?
I would have guessed that it is the same indeed! 😯
I only found information including the server project here:

• the bootstrapper tooling guide
• the silverlight to uno migration guide
  (remark: outdated guide for multiple elements of it like identityserver and uno head structure + version as well requested updating it on another issue, someone could maybe check on?)
• uno.templates docs info, that we can opt into getting the server project, nothing more

Please, if I missed the guide you assume me or any user to know about for using or getting future information about it, please feel free to hint me! Maybe I did miss it!

In general, of course the server project we are getting is 95% a normal asp.net core project, thats true! But the 5% it is not.
Here the differing things we might would need some information for this project if you say its not equal to the bootstrapper here:

• What are we expecting to get using the Uno.Wasm.Bootstrapping.Server NuGet
• What is the app.UseUnoStaticFiles() at the lower part of the server projects Programm.cs meant to do?
  • Using "Peek Definition" on this looks like, its calling the normal app.[...]StaticFiles()command internally again, which we can find in a realdotnet new webapi` (the asp net core web api template in vs2022) also, so that's making me think about this later one could be duplicated call?
• As asp net core 9 does not longer support the Swagger/swashbuckle like in net8, I was searching for at least a info about this if we are updating from net8-9, because(!) the updating net8-net9 uno docs are guiding us to the bootstrapper docs right here, which made me open this issue here via "edit this file" > "Issues" > "New" 🤷 now that you saying, thats not same, I have question marks in my head how the user should differ those maybe internally known details noone tells us? 😅

[DevTKSS]

@jeromelaban if the listed points above (hoping the list is good to understand and better than my first try on the maybe wrong repo Uno.Templates), you can see this as closing: unoplatform/uno.templates#1569

[jeromelaban]

My comment was specifically about the issues related to the uno.wasm.bootstrap docs, not for the rest.

Could you explain what your issue root is, in a single sentence? It would be easier to understand what's blocking you. I understand it has to do with the server project, but I can't figure out what's blocking.

[DevTKSS]

@jeromelaban I think to make it a one sentence I am missing the correct words in English 🥺

Let me give you some references of what I am trying to reach form the ms docs maybe?

• https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore%2Fsecurity%2Fauthentication%2Fcookie%2Fsamples%2F6.x%2FCookieSample%2FPages

• https://github.com/dotnet/AspNetCore.Docs/tree/main/aspnetcore%2Fsecurity%2Fcors%2Fsample%2FCors

• https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore%2Fsecurity%2Fauthentication%2Fcookie.md

(Remark that is not limited to cookies, then more about this is telling us to set up those pages in blazor/razor which then connects the redirect routes in our api)

---

Trying to word it:

• How to: Using uno (wasm?) for serverside ui like Blazor can do using razor pages
• How to use this migration told auth+server things in uno sdk 6.0+ (see doc request for exactly this in the main uno repo)
  This docs are about doing this in uwp and frame nav wich takes in uri routes. Can we somehow use that nowerdays with extensions nav? If yes, then how?
• How to: Set up LinkerConfig for a serverside WebAssembly to connect minimal api to our in app routes/pages (I think I opened a issue to this already just not finding it currently)

---

Hope this helps you understand? Most points I am missing are also filed at the opening comment on the top in bullet points 😅 I don't know how I should word it better to understand sorry

[DevTKSS]

and just to the docs you told me that request seems to not be for that repo, thats why I assue it to be: https://github.com/unoplatform/Uno.Wasm.Bootstrap/blob/main/src/Uno.Wasm.Bootstrap.Server/AspNetExtensions.cs
These are the functions the Package in the provided Server Project is using in Programm.cs file. So could you think of someone could actually give us some information about those in the docs and tell us:

• what is this doing
• when should we use them (chefs.api project does NOT use them)
• How should we use them?

[jeromelaban]

Thanks, this is easier to understand.

This is a mix of different issues that would need to be discussed independently to avoid creating confusion.

How to: Using uno (wasm?) for serverside ui like Blazor can do using razor pages

Server side rendering is not supported by Uno, if this is what you're referring to. If you have a specific question about this, please open a separate discussion.

How to use this migration told auth+server things in uno sdk 6.0+ (see doc request for exactly this in the main uno repo)

I'm not sure of what's missing there, the auth docs are the ones from extensions. If you have an existing issue, let's discuss there.

How to: Set up LinkerConfig for a serverside WebAssembly to connect minimal api to our in app routes/pages (I think I opened a issue to this already just not finding it currently)

If you have a specific problem with the linker and how it behaves, please open an issue with specific errors and a repro.

and just to the docs you told me that request seems to not be for that repo, thats why I assue it to be: https://github.com/unoplatform/Uno.Wasm.Bootstrap/blob/main/src/Uno.Wasm.Bootstrap.Server/AspNetExtensions.cs
These are the functions the Package in the provided Server Project is using in Programm.cs file. So could you think of someone could actually give us some information about those in the docs and tell us:

The xml docs exactly explain what it does, it's a support feature to host an uno wasm app inside an ASP.NET Core app (Blazor has the same support method for the same reasons). Chefs.API does not use it because it does not host the uno app, it's hosted independently.