Switch to file-scoped namespace

[AndrewKeepCoding]

Issue type

enhancement

Which version of the app?

WinUI 3 Gallery

Description

File-scoped namespace will improve readability.
IMHO, it's something that will be done in the future, so why not now? The sooner, the better.
I'd be happy to do this.

Screenshots

No response

Windows version

No response

Additional context

No response

[Jay-o-Way]

Got an example? :)

[AndrewKeepCoding]

For example, App.xaml.cs:

Block-scoped namespace

namespace WinUIGallery
{
    /// <summary>
    /// Provides application-specific behavior to supplement the default Application class.
    /// </summary>
    sealed partial class App : Application
    {
        private static Window startupWindow;

File-scoped namespace

namespace WinUIGallery;

/// <summary>
/// Provides application-specific behavior to supplement the default Application class.
/// </summary>
sealed partial class App : Application
{
    private static Window startupWindow;

[Jay-o-Way]

If you let Visual Studio create such a new file, what does it initially look like? Why would VS prefer one over the other?

[AndrewKeepCoding]

Yeah. VS's item templates haven't been updated (yet?).
I'm bringing this up because, in the CommunityToolkit/Labs-Windows repo, I saw they are switching to file-scoped namespaces (CommunityToolkit/Labs-Windows#148), and I thought it might be a good idea to apply the same change here too. They also updated the editor.config to issue warnings for block-scoped namespaces.

[karkarl]

Thanks for filing this issue. Would you want to take a stab at it?

[AndrewKeepCoding]

Thanks for filing this issue. Would you want to take a stab at it?

@karkarl Of course!🙂