WoofStandard 1.0.2

.NET Standard 2.0 This package targets .NET Standard 2.0. The package is compatible with this framework or higher.
The owner has unlisted this package. This could mean that the package is deprecated, has security vulnerabilities or shouldn't be used anymore. 
dotnet add package WoofStandard --version 1.0.2
NuGet\Install-Package WoofStandard -Version 1.0.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="WoofStandard" Version="1.0.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add WoofStandard --version 1.0.2
#r "nuget: WoofStandard, 1.0.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install WoofStandard as a Cake Addin
#addin nuget:?package=WoofStandard&version=1.0.2

// Install WoofStandard as a Cake Tool
#tool nuget:?package=WoofStandard&version=1.0.2

WOOF Toolkit

.NET Framework extensions created by CodeDog Ltd.

Distributed under MIT License (see License.txt). (c)2018 by CodeDog Ltd., All rights reserved.

This toolkit is used in all CodeDog productions and contracted works. It's free, Open-Source and can be used, re-used and developed by anyone. Little code pearls contained in it are a part of what makes CodeDog special. Made to never reinvent the wheel and to keep simple things as simple and zen as possible.

Modules

Naming convention

Namespaces extending .NET Framework features are named similar, but with "Ex" suffix. There are good reasons for it: related features need related names but any part of the userspace namespace CANNOT match any part of Microsoft framework namespace or the name resolution in the project will break.

WinForms and WPF tools are exception because Woof Toolkit mixes the two to benefit from both. WPF rendering is faster, more flexible and easier to develop, however some core parts of Win32 subsystem intrnally use WinForms. System tray and system shell are WinForms only. WinForms is also faster and easier to develop for some particular cases.

Namespaces

Namespace Description
AssemblyEx Tools for dealing with current and other assemblies.
ConsoleEx Advanced console tools.
Core Tools for .NET Core server projects.
DeploymentEx Tools for building custom installers.
ProcessEx Advanced inter-process communication tools.
SystemEx Provides various information about computer system.

Usage

As project / DLL reference

Just reference the project Woof.

PROS:

  • You can forget about references, everything's in one place.

CONS:

  • Target project will require Woof.dll file as runtime dependency.

As linked dependencies

PROS:

  • Minimal build (target project will build only selected modules).
  • No runtime dependencies (at least from Woof).
  • If many projects in a solution use the same libraries, all point to the same files.

CONS:

  • You have to configure references manually.
  • The process of adding project links is tedious.

HOW:

  • Create directory "Linked" in target project.
  • Use "Add existing item..." option in VS (Shift+Alt+A).
  • Select relevant files, don't forget about XAML and RES files.
  • Use "Add as link" option.

As copied dependencies

PROS:

  • Easy to distribute the sources.
  • Separate, immutable library version for the project.

CONS:

  • Full manual configuration.
  • When used more than onece - many versions of the same code - could be a mess.

HOW:

  • Like with linked dependencies, but just use "Add" instead of "Add as link"

Disclaimer

This is a development version of the toolkit. The files are only versioned under the project or solution they are included in.

Please report any issues to the toolkit developer.

Woof Toolkit is a work in progress in constant development, however it's carefully maintained with production code quality.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated

Added HtmlEmail module, some TODO-s and FIXME-s, fixed metadata.