Unable to build the solution

[jeromelaban]

From the addin Q&A

Hi, I tried to create the project via command line but I get errors, it is as if it did not find the necessary dependencies of Uno. I have checked the extensions and Uno Platform is found. What I could find is that the problem seems to be with the implementation with .Net 8, because I did a test with Uno Platform App (.Net 6, UWP) and I created it, I updated some packages, and the Xamarin SDK, I also enabled the Developer Mode on my PC and I could compile without problems.

[jeromelaban]

Could you post the errors you're getting from the command line? Thanks!

[SpiderArrow]

This is the command I'm running:
dotnet new unoapp -o unoapp2024 -preset "recommended" -markup "csharp" -platforms "maccatalyst" -platforms "windows" -platforms "desktop" -theme-service -pwa False -theme "material" -presentation "mvux" -config False -di False -log "none" -nav "blank" -http False -loc False -tests "none" -toolkit -dsp -id "com.companyname.unoapp2024" -pub "O=unoapp2024"
and these are the errors:

dotnet : Error: Opción u opciones no válidas:
En línea: 1 Carácter: 1

• dotnet new unoapp -o unoapp2024 -preset "recommended" -markup "csharp ...

•   + CategoryInfo          : NotSpecified: (Error: Opción u opciones no válidas::String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError
  
  

-preset
"-preset" no es una opción válida
recommended
"recommended" no es una opción válida
-markup
"-markup" no es una opción válida
csharp
"csharp" no es una opción válida

[jeromelaban]

Thanks for the update. Have you run uno-check?

[agneszitte]

I am not sure if you have already checked all the details for our get-started as well, but sharing it just in case:
https://aka.platform.uno/get-started

Are you able to create a project properly with the blank preset? (to check if there is a difference Vs the recommended preset).

Have you tried also with these commands?
dotnet new unoapp -preset=blank -o AppName
dotnet new unoapp -preset=recommended -o AppName
(cf. https://platform.uno/docs/articles/get-started-dotnet-new.html?tabs=windows#uno-platform-application)

[SpiderArrow]

I followed the steps to use uno-check and thanks to it I found installation problems, I followed the steps on the page but still it does not create the solution correctly. I tried to repair my VS 2022 but it did not work. Try to use VS Code and run the command :

dotnet new unoapp -preset=blank -o NEWAPP

But I got this information on the OUTPUT:

2024-05-17 17:51:25.744 [error] (C:\Users\USUARIO\Desktop\newApp\NEWAPP\NEWAPP\NEWAPP.csproj): Could not resolve SDK "Uno.Sdk". Exactly one of the probing messages below indicates why we could not resolve the SDK. Investigate and resolve that message to correctly specify the SDK.
  SDK resolver "Microsoft.DotNet.MSBuildWorkloadSdkResolver" returned null.
  Unable to resolve 'Uno.Sdk (= 5.2.132)' for '.NETStandard,Version=v0.0'. PackageSourceMapping is enabled, the following source(s) were not considered: Microsoft Visual Studio Offline Packages, NuGet official package source.
2024-05-17 17:51:25.775 [error] Failed to load project 'C:\Users\USUARIO\Desktop\newApp\NEWAPP\NEWAPP\NEWAPP.csproj'. One or more errors occurred. (The SDK 'Uno.Sdk' specified could not be found.  C:\Users\USUARIO\Desktop\newApp\NEWAPP\NEWAPP\NEWAPP.csproj)

The extensions are installed, so I don't understand the error.

[ToddGlodek]

Have y'all ever considered changing the New Project configuration utility so that it is cloud based & runs inside a browser using WASM ?? It seems people constantly have difficulty creating projects - especially since it requires having you run uno-check to keep the Templates up to date. It seems like running the new project setup wizard in the cloud ( rather than as a Visual Studio extension, for example) would streamline the entire process by ensuring that all the latest templates/netgets/etc were guaranteed every time I created a new project.

I, for one, would prefer downloading a ZIP achieve containing all the per project files.

[jeromelaban]

Thanks for the suggestion @ToddGlodek. This would not change much, as the creation of the project is running fine, it's building that causes issues here. This specific error happens after the project is created, during the restore.

We still need to know why this error happens, even if it's a pure .NET SDK issue.

[ToddGlodek]

Obviously, you know best - I just thought it might be a super cool way to demonstrate the WASM capabilities of Uno. Ya-know... going right to the Uno Platform Home/Getting Started page... running the project wizard in the browser... getting a Zip achieve download in a few seconds without having to go through the uno-check setup process.

For a new user investigating Uno Platform for the first time, it would eliminate a lot of hurdles. They could immediately see a familiar looking project structure that works on many different platforms - without having to do ANY previous development machine configuration/installation/customization. You could also include the "Next Steps: Configuring Your Machine instructions" inside the Zip file as well.

[francoistanguay]

ICYMI, the first half of this is done here: https://new.platform.uno

[ToddGlodek]

Yes, I have tried that before... But

1. There does not seem to be any obvious way to get to new.platform.uno from the Uno Home Page. The only place you can go is the Visual Studio Marketplace
2. A new user would still have to go through the uno-check setup process before pasting dotnet new command into the terminal. If they missed/ignored the "Our Documentation" instructions, and didn't do that first, it would simply error out. Whereas, if they got back a Zip Archive - they would have some immediate success and would be encouraged to continue exploring Uno Platform.
3. 

[SpiderArrow]

Hi, I followed the steps to create a binlog. Honestly it is the first time that I see files of this type, from what I can understand there are some tools that are being used that are being omitted, for practical purposes I attach the zip file with the solution that I generated through VS 2022 including the binlog file. Something that I could notice digging in the files that are in the folder Solution Items, is that in the global.json file the value of "Uno.Sdk" is in the version 5.2.132 the extension is in the version 5.2.49.
UnoApp4.zip

[jeromelaban]

Thanks for the update.

It is very curious that you're getting Uno.Sdk 5.2.49, as this is a version we never published on nuget.org. You find how to update the uno.sdk here.

This would indicate that somehow, nuget installed either a dev build, or something else incorrect.

If you ran uno.check, you should have had the latest templates installed automatically, but just in case, could you run dotnet new update on your command line? Can you also paste the output of that command, as it will tell which version of the templates were previously installed. It may help determine where the package you got comes from.

[jeromelaban]

@SpiderArrow Thanks (please make sure to answer in the same thread, it will be easier for other community members to follow through).

This particular message (PackageSourceMapping está habilitado) seems to indicate that there's a nuget.config file that prevents the download of the Uno.Sdk package.

Let's try a few things:

1. Could you paste the contents of the file %appdata%\NuGet\NuGet.Config here? I suspect that there's a configuration that prevents nuget restore from working properly. Make sure to review the contents before posting it here, in case there's private information.
2. Can you try adding the following in a file named nuget.config next to the sln of the project that was created:

   <?xml version="1.0" encoding="utf-8"?>
   <configuration>
     <packageSources>
       <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
     </packageSources>
   </configuration>

   Then try building the app with dotnet build /bl ?

[SpiderArrow]

Hello again, thank you for your reply. Here I share the Nuget.config file that I have on my computer.
NuGet.txt
I added the code in my nuget.config file in my project sln and then run the dotnet build /bl command and got this result:

C:\Program Files\dotnet\sdk\8.0.300\NuGet.targets(169,5): warning : Unable to find a project to restore! [C:\Users\USUARIO\source\repos\UnoApp4\Uno
App4\UnoApp4.sln]

Compilación correcta.

C:\Program Files\dotnet\sdk\8.0.300\NuGet.targets(169,5): warning : Unable to find a project to restore! [C:\Users\USUARIO\source\repos\UnoApp4\Uno
App4\UnoApp4.sln]
    1 Advertencia(s)
    0 Errores

Tiempo transcurrido 00:00:00.50

[jeromelaban]

Thanks. The global nuget.config that you have for your system is very complex, and it feels like there's something wrong with its contents.

The default one when installing a new machine should look like this:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
    <add key="Microsoft Visual Studio Offline Packages" value="C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\" />
  </packageSources>
  <packageRestore>
    <add key="enabled" value="True" />
    <add key="automatic" value="True" />
  </packageRestore>
  <bindingRedirects>
    <add key="skip" value="False" />
  </bindingRedirects>
  <packageManagement>
    <add key="format" value="0" />
    <add key="disabled" value="False" />
  </packageManagement>
</configuration>

In Visual Studio, without opening a solution, could you:

• Go to Tools, Options
• Go to NuGet Package Manager
• Then in Package Source Mapping

Could you show a screenshot of all that you're seeing?
Then could you try clicking the Remove All button, click OK to close the option dialog, and try creating an uno project again?

Thanks for the help in troubleshooting this!

[SpiderArrow]

EUREKA!
That was the problem, I was able to create the project without errors!
Thank you very much for the support, I will continue to explore the platform.

[jeromelaban]

Thank you! This is very valuable. We'll certainly extend uno.check to validate for those scenarios.

[agneszitte]

(Related issue for Uno.Check: unoplatform/uno.check#256)

[SpiderArrow]

I followed the steps to update Uno but didn't have much luck fixing the reference to the Uno Sdk. Install dotnet-outdated, run the command in the folder where the .sln file is and in the subfolder where the .csproj file is. I also ran the dotnet new update command but it tells me that the packages are updated. I attach the results of the console in the txt file.
test-dotnet-outdated.txt