KeenMate.FluentlySharePoint.OnPremise 0.5.0-beta.1

.NET Framework 4.5.1
This is a prerelease version of KeenMate.FluentlySharePoint.OnPremise.
Install-Package KeenMate.FluentlySharePoint.OnPremise -Version 0.5.0-beta.1
dotnet add package KeenMate.FluentlySharePoint.OnPremise --version 0.5.0-beta.1
<PackageReference Include="KeenMate.FluentlySharePoint.OnPremise" Version="0.5.0-beta.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add KeenMate.FluentlySharePoint.OnPremise --version 0.5.0-beta.1
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: KeenMate.FluentlySharePoint.OnPremise, 0.5.0-beta.1"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install KeenMate.FluentlySharePoint.OnPremise as a Cake Addin
#addin nuget:?package=KeenMate.FluentlySharePoint.OnPremise&version=0.5.0-beta.1&prerelease

// Install KeenMate.FluentlySharePoint.OnPremise as a Cake Tool
#tool nuget:?package=KeenMate.FluentlySharePoint.OnPremise&version=0.5.0-beta.1&prerelease
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

Sentence-like CSOM programming experience for SharePoint 2016 OnPremise using original SharePoint 2016 RTM CSOM NuGet package

Product Versions
.NET Framework net451 net452 net46 net461 net462 net463 net47 net471 net472 net48
Compatible target framework(s)
Additional computed target framework(s)
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
0.5.0-beta.1 518 8/8/2018

- Initial version of this library. Originally we have not planned to have two libraries of FluentlySharePoint but here we are. CSOM libraries for Online and OnPremise are different enough for having two separated NuGet packages