Refactored file structure

* Now publishing docs from the docs folder directly to allow generation of the docs at build time without need of a distinct publish step.

Author: smaillet

.editorconfig

@@ -0,0 +1,54 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[BUG] - Title"
+labels: bug
+assignees: ''
+
+---
+
+Please provide the following information when submitting an issue. 
+
+> Where appropriate replace the `[ ]` with a `[X]` to mark an item as 'checked'
+
+**.NET Framework Used:**
+
+- [ ] .NET 8.0
+- [ ] .NET 9.0
+- [ ] Something else
+
+**OS Environment:**
+
+- [ ] Windows 10
+- [ ] Windows 10 IoT Core
+- [ ] Windows Server 2012
+- [ ] Windows Server 2012 R2
+- [ ] Windows Server 2016
+
+OS Version: `####.####...`
+
+**I have already...**
+
+- [ ] Reproduced the problem using the latest stable release.
+- [ ] Reviewed the [documentation](https://ubiquitydotnet.github.io/CommandLineParsing/).
+- [ ] Reviewed the [current issues](https://github.com/UbiquityDotNET/CommandLineParsing/issues) to check that the issue isn't already known.
+
+**Description:**
+
+Provide a clear and concise description of what the bug is.
+
+**Steps to reproduce the problem:**
+
+- [ ] Reviewed the [documentation](https://ubiquitydotnet.github.io/Llvm.NET/).
+- [ ] Included Sample code or link to repository/gist to reproduce the bug (This is the fastest way to a resolution as it reduces the time to reproduce the problem. The smaller the sample is the better.) 
+      
+**Expected Behavior**
+
+Please provide a clear and concise description of what you expected to happen.
+
+**Actual Behavior**
+
+Please provide a clear and concise description of what actually happens.
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: "[Feature] - Title"
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+> NOTE: 
+> Feature requests are intended to request a new feature or a change in the intended/designed
+> functionality (a.k.a. DCR). They should not be used to report bugs, which are incorrect
+> implementations of the designed functionality.
+
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/bug.md

@@ -8,12 +8,11 @@ jobs:
 
     steps:
     - name: Check Out
-      uses: actions/checkout@v1
-      
+      uses: actions/checkout@v4
     - name: Setup .NET Core
-      uses: actions/setup-dotnet@v1
+      uses: actions/setup-dotnet@v4
       with:
-        dotnet-version: 2.2.108
-    
-    - name: Build with dotnet
-      run: dotnet build --configuration Release
+        global-json-file: global.json
+    - name: Build with PowerShell
+      shell: pwsh
+      run: .\Build-All.ps1 -Configuration Release -ForceClean

.github/ISSUE_TEMPLATE/bug_report.md

@@ -40,11 +40,6 @@ TestResult.xml
 [Rr]eleasePS/
 dlldata.c
 
-# DNX
-project.lock.json
-project.fragment.lock.json
-artifacts/
-
 *_i.c
 *_p.c
 *_i.h
@@ -70,87 +65,24 @@ artifacts/
 *.svclog
 *.scc
 
-# Chutzpah Test files
-_Chutzpah*
-
 # Visual C++ cache files
 ipch/
 *.aps
 *.ncb
-*.opendb
 *.opensdf
 *.sdf
 *.cachefile
-*.VC.db
-*.VC.VC.opendb
 
 # Visual Studio profiler
 *.psess
 *.vsp
 *.vspx
-*.sap
-
-# TFS 2012 Local Workspace
-$tf/
-
-# Guidance Automation Toolkit
-*.gpState
 
 # ReSharper is a .NET coding add-in
 _ReSharper*/
 *.[Rr]e[Ss]harper
 *.DotSettings.user
 
-# JustCode is a .NET coding add-in
-.JustCode
-
-# TeamCity is a build add-in
-_TeamCity*
-
-# DotCover is a Code Coverage Tool
-*.dotCover
-
-# NCrunch
-_NCrunch_*
-.*crunch*.local.xml
-nCrunchTemp_*
-
-# MightyMoose
-*.mm.*
-AutoTest.Net/
-
-# Web workbench (sass)
-.sass-cache/
-
-# Installshield output folder
-[Ee]xpress/
-
-# DocProject is a documentation generator add-in
-DocProject/buildhelp/
-DocProject/Help/*.HxT
-DocProject/Help/*.HxC
-DocProject/Help/*.hhc
-DocProject/Help/*.hhk
-DocProject/Help/*.hhp
-DocProject/Help/Html2
-DocProject/Help/html
-
-# Click-Once directory
-publish/
-
-# Publish Web Output
-*.[Pp]ublish.xml
-*.azurePubxml
-# TODO: Comment the next line if you want to checkin your web deploy settings
-# but database connection strings (with potential passwords) will be unencrypted
-#*.pubxml
-*.publishproj
-
-# Microsoft Azure Web App publish settings. Comment the next line if you want to
-# checkin your Azure Web App publish settings, but sensitive information contained
-# in these scripts will be unencrypted
-PublishScripts/
-
 # NuGet Packages
 *.nupkg
 # The packages folder can be ignored because of Package Restore

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,94 @@
+<#
+.SYNOPSIS
+    Script to build all of the LLvm.NET code base
+
+.PARAMETER Configuration
+    This sets the build configuration to use, default is "Release" though for inner loop development this may be set to "Debug"
+
+.PARAMETER AllowVsPreReleases
+    Switch to enable use of Visual Studio Pre-Release versions. This is NEVER enabled for official production builds, however it is
+    useful when adding support for new versions during the pre-release stages.
+
+.PARAMETER ForceClean
+    Forces a complete clean (Recursive delete of the build output)
+
+.PARAMETER BuildMode
+    Specifies the build mode, which may be one of the following:
+
+    |Name    | Description                                                               |
+    |--------|---------------------------------------------------------------------------|
+    | Source | Builds only the source code. This is useful for local development.        |
+    | Docs   | Builds only the docs. Saves on build time when only updating docs topics. |
+    | All    | [Default] Builds everything                                               |
+
+.DESCRIPTION
+    This script is used by the automated build to perform the actual build. The Ubiquity.NET
+    family of projects all employ a PowerShell driven build that is generally divorced from
+    the automated build infrastructure used. This is done for several reasons, but the most
+    important ones are the ability to reproduce the build locally for inner development and
+    for flexibility in selecting the actual back end. The back ends have changed a few times
+    over the years and re-writing the entire build in terms of those back ends each time is
+    a lot of wasted effort. Thus, the projects settled on PowerShell as the core automated
+    build tooling.
+#>
+[cmdletbinding()]
+Param(
+    [string]$Configuration="Release",
+    [switch]$AllowVsPreReleases,
+    [switch]$ForceClean,
+    [ValidateSet('All','Source','Docs')]
+    [System.String]$BuildMode = 'All'
+)
+
+Push-Location $PSScriptRoot
+$oldPath = $env:Path
+try
+{
+    # Pull in the repo specific support and force a full initialization of all the environment
+    # as this is a top level build command.
+    . .\repo-buildutils.ps1
+    $buildInfo = Initialize-BuildEnvironment -FullInit -AllowVsPreReleases:$AllowVsPreReleases
+    $BuildSource = $false
+    $BuildDocs = $false;
+
+    switch($BuildMode)
+    {
+    'All' { $BuildSource = $true; $BuildDocs = $true; }
+    'Source' { $BuildSource = $true }
+    'Docs' { $BuildDocs = $true }
+    }
+
+    if((Test-Path -PathType Container $buildInfo['BuildOutputPath']) -and $ForceClean )
+    {
+        Write-Information "Cleaning output folder from previous builds"
+        remove-Item -Recurse -Force -Path $buildInfo['BuildOutputPath']
+    }
+
+    New-Item -ItemType Directory $buildInfo['NuGetOutputPath'] -ErrorAction SilentlyContinue | Out-Null
+
+    if($BuildSource)
+    {
+        .\Build-Source.ps1 -AllowVsPreReleases:$AllowVsPreReleases
+    }
+
+    if($BuildDocs)
+    {
+        .\Build-Docs.ps1 -AllowVsPreReleases:$AllowVsPreReleases
+    }
+}
+catch
+{
+    # everything from the official docs to the various articles in the blog-sphere says this isn't needed
+    # and in fact it is redundant - They're all WRONG! By re-throwing the exception the original location
+    # information is retained and the error reported will include the correct source file and line number
+    # data for the error. Without this, only the error message is retained and the location information is
+    # Line 1, Column 1, of the outer most script file, which is, of course, completely useless.
+    throw
+}
+finally
+{
+    Pop-Location
+    $env:Path = $oldPath
+}
+
+Write-Information "Done build"