Uno.Samples
                                
                                
                                
                                    Uno.Samples copied to clipboard
                            
                            
                            
                        Upgrade all samples to run with latest uno and latest VS 2022.
The last update in VS 2022 caused some samples to stop building, causing the canary to fail. The current non-canary CI is built around partial validation, which makes other samples miss validations.
Updating projects one by one to uno latest will force a rebuild with VS 2022, and will show which projects fail in an incremental manner.
Summary
PR #154 - To create the ArchiveProject folder and exclude projects from the CI build. PR #153 - WebRTC.Wasm - Updated Uno to the latest packages, after the project there is a runtime error to fix - ListViewSample - Already updated.
@jeromelaban , the project that still falls on canary is TimeEntryRia, which uses .NET 4.0. Is it updated?


@aesteves900 try upgrading it to net48 and see if it helps.
@jeromelaban , I tried with no success, because the project was created on Visual Studio 2010. I believe creating a fresh project and importing all objects is the only way. What do you recommend for the next steps?

@aesteves900 you should be able to create a net48 "sdk-style" project in place of the existing one.
@jeromelaban , I saw a lot of compatibility issues when trying .NET 4.8 migration, because TimeEntryRia (canary CI issue) uses a bunch of legacy libraries like WCF Services, RIA Services, and SilverLight. I'm a little confused it's the best way I just try migrating or rewriting the sample. Definitely, my option is not just to install some NuGet packages and we will be good to go. I need some direction on the next steps. Can you give to me more details about the expected results from this task? I'm stuck at this point.

Interesting, support for silverlight has been removed completely, it seems that we'll need to take this sample out of support (moved to a "legacy" folder), as we're not able to build it anymore. Let's create a "Legacy" folder at the root, and move the sample there.
@jeromelaban, There is one solution for each project. What is the correct way to disable the build for the new legacy folder?
Yes, like this


Do just I need to create a folder on the repo and move obsolete projects there?
The Samples are automatically built through here: https://github.com/unoplatform/Uno.Samples/blob/4ed28638d14c83b76f31868c87733e06e312da9a/.vsts-ci.yml#L33
We'll need to add an exclusion when the path starts with Legacy