Add a command line parameter to select the Umbraco version.

by default the package/site should use a defined version but if you want you should be able to override it with a parameter.

e.g.
-umbVersion 8.7.0

Will need to put in a placeholder in the .csproj files, and add something to the template.config to do the search/replace.

We also need to review the names, descriptions, author, etc... used in actual templates too. One for the next package team meeting @jmayntzhusen?

This is how the project templates look in VS 2019 (prelease edition):

To see these you have to check:

These templates only appear if the templates are installed from nuget. If you install the templates from local source folder then they don't show up in VS Create New Project

Originally posted by @LottePitcher in #21 (comment)

We need a mechanism in the repo to keep the code in the item template folders in sync with that in the project template ones (e.g dashboards).

Something like a build event, or gulp script to copy the files between the two areas should be enough.

Moving the solution file to the root, means the package references in the website project are pointing to the wrong folder :(

When you create a package, and then open the visual studio solution and build the first request in a browser comes back with a YSOD

Could not find a part of the path 'C:\code\MyAwesomePackage\.website\bin\roslyn\csc.exe'.

If you clean and the then rebuild the solution in visual studio it then works.

there must be something in the solution or project file that is causing the first build not to work.

Some usage/reference docs for switches etc.

If we push the output of this repo to nuget then it will make allowing people to use the templates much easier.

Before asking people to contribute new templates we need guidelines on the process. I kept notes whilst working on #11 so have made a start. When that PR is finished I'll get these guidelines added.

Make the contribution template a bit more focused on making item templates.

we will build up a library of item templates, but not all of them will be copied over to the main "package" template as we don't want to overload it with switches -

but a library of item templates will still be useful.

When creating a package using the templates, the demo site is ignored via .gitignore.

What do you think would be the right approach in order to include the demo site?

Should I just include all the files, some of the files, or maybe just a zip including the sqlce db?

When running the GitHub actions, on the "Build Project" I get the following error:

Error: C:\Program Files\dotnet\sdk\3.1.402\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(241,5): error NETSDK1004: Assets file 'D:\a\DuugTest_Richard\DuugTest_Richard\src\DuugTest_Richard\obj\project.assets.json' not found. Run a NuGet package restore to generate this file. [D:\a\DuugTest_Richard\DuugTest_Richard\src\DuugTest_Richard\DuugTest_Richard.csproj]

I found by adding a /t:Restore to the build line it solved the issue:

run: msbuild ./src -p:Configuration=${{ env.CONFIG }} /t:Restore

This is a list of UI elements in the backoffice we'd like to cover in the UI Examples item template. Additionally we should have some contrib guidelines written up on how to contribute to this project!

• Section/dashboard to get us started
• List of icons - Lotte
  • Umb icon directive
  • Search for icons
  • Adding custom icons
• Buttons - Richard
  • Overlays (popup notifications, confirm)
  • Button states
  • Pop-outs (slide out from the right - infinite editor)
  • Showing notifications
  • Dialogs - media picker, content picker, etc.
• Tabs - David
• Umb-box
  • Collapse - Jesper
  • Buttons on right
  • Header
  • Content
• Layout - Kevin
  • Flex
  • Margin
  • Loading.
• Editor panels
  • Header
  • Content
  • Footer
    • Footer left/right/center
• Inputs (text boxes / selects etc)
  • Textbox
  • Area
  • Richtext
  • Checkbox
  • Toggle
  • DatePicker
• Tables/Lists/Pagination (dave)
• Localization
• Alerts

Advanced:

• Save and publish buttons
• Header menu item
• File download/upload
• SignalR (needs code)
• Tour of the section

If you install the Package project you get a package.xml file in the root of the solution that includes a file and folder that points to the dll and the app plugins folder of the package. Automatically replaces the name, and is a very nice touch!

https://github.com/umbraco/Package.Templates/blob/master/ProjectTemplates/UmbracoPackage.1/package.xml

Problem I've found though is that the dll is not exisiting when I build, it is found in the .website folder instead, so fx last time I had to edit from:

  <files>
    <folder path="src/Package.Workshop/App_Plugins/Package.Workshop" orgPath="App_Plugins/Package.Workshop" />
    <file path=".src/Package.Workshop/bin/release/Package.Workshop.dll" orgPath="bin/Package.Workshop.dll" />
  </files>

To:

  <files>
    <folder path=".website/App_Plugins/Package.Workshop" orgPath="App_Plugins/Package.Workshop" />
    <file path=".website/bin/Package.Workshop.dll" orgPath="bin/Package.Workshop.dll" />
  </files>

Are we expecting the dll to exist in the core project? Guess I may have needed to build as release instead of debug for that?

Maybe it's easier to change it to the website folder instead as we'd expect the testsite to have the correct files and be tested before packing it up, right?