canton7 / Stylet

A very lightweight but powerful ViewModel-First MVVM framework for WPF for .NET Framework and .NET Core, inspired by Caliburn.Micro.
MIT License
994 stars 143 forks source link

Why not use $rootnamespace$ instead of hard code "Company.WpfApplication1" namespace? #179

Closed GF-Huang closed 3 years ago

GF-Huang commented 3 years ago

image

references: https://docs.microsoft.com/en-us/nuget/create-packages/source-and-config-file-transformations

namespace $rootnamespace$.Models
{
    public struct CategoryInfo
    {
        public string categoryid;
        public string description;
        public string htmlUrl;
        public string rssUrl;
        public string title;
    }
}
canton7 commented 3 years ago

Are you seeing this on the latest version of Stylet.Templates? That should be fixed

GF-Huang commented 3 years ago

God, I don't know it has a update. 😢

GF-Huang commented 3 years ago

And why not post to https://marketplace.visualstudio.com?

canton7 commented 3 years ago

Isn't the Visual Studio marketplace just for Visual Studio extensions?

GF-Huang commented 3 years ago

Please check this, there are a lot of project templates.

image

canton7 commented 3 years ago

Stylet.Templates is dotnet new template, not a Visual Studio template (yes, there is a difference).

You can get dotnet new templates to show up in the list of templates in preview versions of Visual Studio, if you enable a preview option somewhere in settings: in the future I assume this will happen by default.

I have no intention of providing a Visual Studio template in addition to the current two templates.

GF-Huang commented 3 years ago

OK, thanks.