search

ChrisHammond / DNNTemplates

Christoc's DotNetNuke Extension Development templates for Visual Studio
http://www.christoc.com/Products/DNN-Development-Templates
Other
97 stars 38 forks source link

Allow a different default namespace for skins vs modules. #48

Closed swalker1595 closed 6 years ago

swalker1595 commented 6 years ago

I would like to have a different default root namespace when using the theme template vs using the module template. For example, when creating a new module, I’d like the namespace to be: Walker.Dnn.Modules. When creating a theme I would like the default root namespace to be Walker.Dnn.Skins.

Do you know of anyway that we can detect the template type in the Project Setup Wizard?

swalker1595 commented 6 years ago

I have been unable to find any way to detect the project template inside of SetupWizard. The only way I see implementing this is to create 2 classes that inherit from SetupWizard. One could be called ModuleSetupWizard and SkinSetupWizard or something.

We would then have to extract the properties RootNameSpace, OwnerName, etc. into the SetupWizard. They would need to be, atleast, protected so that the derived classes could change them on initialization.

Finally, in the .vstemplate, we could specify which class to use, SetupWizard, ModuleSetupWizard, or SkinSetupWizard.

swalker1595 commented 6 years ago

Can we close this issue? PR #47

ChrisHammond commented 6 years ago

Closing issue for now as it will be included in the next release of the template project. Thanks for your contribution!