Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out a good way to distribute the new duality template #788

Closed
Barsonax opened this issue Apr 18, 2020 · 1 comment · Fixed by #825
Closed

Figure out a good way to distribute the new duality template #788

Barsonax opened this issue Apr 18, 2020 · 1 comment · Fixed by #825
Assignees
Labels
Discussion Nothing to be done until decided otherwise Usability Related to API and UI usability

Comments

@Barsonax
Copy link
Member

Barsonax commented Apr 18, 2020

Summary

A new duality template was made that uses the default .NET tooling in #786. The first step was to release this as a simple zip file. The source of the template can be found here https://github.com/Barsonax/DualityProjectTemplate

However there might be better ways to distribute this template

Analysis

  • Ability to replace tokens
  • Nice integration with visual studio or command line tooling
@Barsonax Barsonax added Discussion Nothing to be done until decided otherwise Usability Related to API and UI usability labels Apr 18, 2020
@Barsonax Barsonax self-assigned this Apr 18, 2020
@Barsonax Barsonax linked a pull request May 24, 2020 that will close this issue
@Barsonax
Copy link
Member Author

A dotnet new template seems to be the way to go. Its quite simple to make (so less maintenance) but has some nice features:

  • Ability to replace strings with parameters
  • Ability to run post actions (such as dotnet build)
  • Commandline!

No Vsual studio integration yet but this is planned I believe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Nothing to be done until decided otherwise Usability Related to API and UI usability
Development

Successfully merging a pull request may close this issue.

1 participant