- Updated templates to .NET 8 and latest Giraffe
- Updated templates to .NET 7 and latest Giraffe
- Removed log filter
- Improved default CORS policy
- HTTPS redirection not during Development
- Updated to Giraffe 5.0.0-rc-6 with Ply
- Updated all templates to .NET 5 and Giraffe 5.0.0-rc-1
- Changed all templates to make use of the passed in
args
when composing the ASP.NET Core web host.
- Updated Giraffe to version
4.1.x
- Set
netcoreapp3.1
as default target framework - Upgraded all templates to use .NET Core's generic host
- Updated Paket to use
dotnet tools
distribution - Fixed cyclic dependency issue when
dotnet new giraffe
is run from within a folder namedGiraffe
- Added
paket.references
files to*.fsproj
files when-UsePaket
is enabled - Creating a
.sln
file referencing the created projects as part of the template - Fixed bug where hyphens in project name caused builds to fail (e.g.
dotnet new giraffe -n foo-bar
) - Renamed
IncludeTests
flag toExcludeTests
and inverted logic - Renamed
UsePaket
flag toPaket
so that the default abbreviation is-P
instead of-U
- Added new
Solution
flag, which determines if a complete solution withsrc
and (optional)tests
folder should get created or not. Default value is set tofalse
- Fixed build some warnings
For more information please visit the updated documentation regarding the latest template options of the Giraffe template.
- Added shebang and fixed shellcheck warnings
- Updated Giraffe to version 3.4.x
- Updated TestHost to version 2.1.x for test projects
- Updated Giraffe to version 3.2.x
- Updated Giraffe.Razor to version 2.0.x
- Added TaskBuilder.fs as dependency to all templates
- Updated all templates to latest Giraffe version
- Updates all templates to .NET Core 2.1 apps
- Updated paket to latest version
- Fixed minor bugs with the generation of the
None
view engine template - Fixed line ending issue in *.sh files
- Added post action to set read permissions to the build.sh file
Updated paket.exe to latest Paket release (fixes #12).
Updated all templates to use the latest Giraffe 1.1.*
release.
Updated all templates to use the latest Giraffe 1.0.0
release.
- Added the ASP.NET Core default developer exception page when environment is development.
- Added a default
web.config
file to all templates to support Azure deployments.
- Added
none
as a new option to the--ViewEngine
parameter, which will create a Giraffe web application without any view engine (Web API only). - Added a new parameter called
--UsePaket
which will use Paket instead of NuGet as the package manager for the Giraffe web application.
- Updated the default Giraffe template to the latest version of Giraffe and made use of the new HTML attributes from the
GiraffeViewEngine
.
Added an additional parameter called IncludeTests
which can be added to auto generate an accompanying test project to your Giraffe web application.
Default Giraffe web application with the GiraffeViewEngine
and no tests:
dotnet new giraffe
Default Giraffe web application with the GiraffeViewEngine
and a default test project:
dotnet new giraffe --IncludeTests
Giraffe web application with the Razor view engine and a default test project:
dotnet new giraffe --ViewEngine razor --IncludeTests
The Giraffe template supports three different view engines now:
giraffe
(default)razor
dotliquid
You can optionally specify the --ViewEngine
(or short -V
) parameter and select one of the supported options when creating a new Giraffe project:
dotnet new giraffe --ViewEngine razor
When you run dotnet new giraffe
it will automatically create a new Giraffe project with the default GiraffeViewEngine
engine.
Previous releases of this library were documented in Giraffe's release notes.