Migrate (or fork) samples from Paper to Fabric

[chrisglein]

Suggestion

As part of RNW supporting Fabric, there will need to be good samples of Fabric apps that app authors can refer to. Maybe all the samples can be moved over. Maybe in some cases we need Paper versions as we support them in parallel.

Here's the whole list. Which of these make sense to migrate?

• AppServiceDemo - This sample is paired with a blog post and also makes less sense with a Win32 Fabric app. Recommend not porting.
• Calculator - This seems very appropriate to migrate to Fabric
• CalculatorCoreAppNuGet - Whether this makes sense to migrate depends on whether Fabric initially offers a golden path on both nugets and raw source (and how that corresponds to CoreApp's successor)
• CalculatorNuGet - Whether this makes sense to migrate depends on whether Fabric initially offers a golden path on both nugets and raw source
• ContinuousIntegration - Not a sample with UI
• NativeModuleSample - This is a non-UI sample, but has an app frame that could be migrated
• ReactNativeWinRT - Need to evaluate whether the UI here is meaningful

Also of note is this "min app" sample on Fabric today. Which likely is eclipsed by the new Fabric app template.

Platforms

Windows

Sample code

No response

[TatianaKapos]

closing, the current sample apps we have are Calculator, NativeModuleSample, and ContinousIntegration - all which have already been migrated to Fabric. The rest of the sample apps are in deprecated samples-old folder.

The only other app I could see us moving from samples-old to new-arch is CameraDemo (consuming a community module - would require adding fabric support to the repo). We could either migrate that app or create a new one that consumes a different community module to showcase the same functionality.