Releases: OSLC/oslc4net
[0.4.3] - 2024-10-19
Security
This release does not contain security updates.
Added
- ️⚡️ An example project using
OslcClient
and basic auth to retrieve a WorkItem (OSLC ChangeRequest) from Jazz. OslcClient::ForBasicAuth()
factory method.- ️️️⚡️
OslcClient.GetResourceAsync()
strongly typed async method that returnsOslcResponse<T>
with either a typed resource or an error. - Support for complex MIME type strings for content negotiation. Current
Accept
string is set totext/turtle;q=1.0, application/rdf+xml;q=0.9, application/n-triples;q=0.8, text/n3;q=0.7
by default. - OSLC Query results now expose a
.TotalCount
property.
Changed
- ❗️
OSLC4Net.Client
now requiresnetstandard2.1
(was:netstandard2.0
). No longer usable under .NET Framework 4.x. - Upgraded dotNetRDF to v3.3.0
Deprecated
- Some constructors on
OslcClient
were deprecated (around skipping TLS checks). - 👉 log4net logging will be replaced with the standard Microsoft ILogger in a future release.
- Direct use of
IEnumerator
properties onOslcQueryResponse
to iterate over response pages. - Multiple symbols on OSLC Query related code with Java-like signatures (various
Get*
methods) and string types. Prefer C# props of typeUri
.
Removed
This release does not remove any features.
Fixed
OslcClient
no longer overwrites most of the headers (#204). It was a similar issue to #19 (but happening withOslcRestClient
).- Ensure OSLC Query responses are processed correctly when they contain multiple
oslc:ResponseInfo
objects (!203).
The release build looks like it has failed, but the release was successful - an examples project failed to publish, which is actually good.
[0.4.2] - 2024-10-09
Security
- 🔒️❗️
OSLC4Net.Client
now defaults to strong TLS certificate checking. Skipping TLS checks now requires explicit configuration.
Added
- ⚡️ Support for .NET 6+ was added by migrating most of the projects in the solution to target
netstandard2.0
.
Changed
- ⚡️
OSLC4Net.Core
now targetsnetstandard2.0
, which allows it to be used under .NET Framework 4.7.2 or higher as well as .NET 6+. - ⚡️ dotNetRDF was upgraded from v1 to v3 to enable targeting
netstandard2.0
.- One of the key breaking changes is that
ITriple
andINode
no longer have the.Graph
property. - ❗️ This caused breaking changes to some of the method signatures in
OSLC4Net.DotNetRdfProvider
to allow theIGraph
instance to be passed.
- One of the key breaking changes is that
OSLC4Net.Client
now targetsnetstandard2.0
.- ❗️ The main breaking change is the replacement of the legacy
WebRequestHandler
withHttpClientHandler
. This caused some method/constructor signatures to change. - ❗️
RemoteCertificateValidationCallback
was replaced with a lambda function.
- ❗️ The main breaking change is the replacement of the legacy
OSLC4Net.Query
now targetsnetstandard2.0
. The Antlr3 runtime package targeting PCL was replaced with a package targeting NETStandard1.0 (Antlr 4 targets NETStandard2.0).- ❗️
JsonMediaTypeFormatter
was renamed intoOslcJsonMediaTypeFormatter
to better reflect its purpose (support a bespoke OSLC JSON format) and avoid conflict withSystem.Net.Http.Formatting.MediaTypeFormatter
. - Test projects were migrated from MSTestV2 to xUnit (except for integration tests for OSLC CM)
Deprecated
- .NET 6 support is deprecated as the EOL is approaching soon. Given that all non-Framework libraries target
netstandard2.0
, this should have no impact on the users.
Removed
- .NET 7 support was removed since the SDK has reached EOL.
Newtonsoft.Json
package was only used in the StockQuoteSample ASP.NET MVC project. Its references were removed from all other projects.
Fixed
This release does not contain bug fixes.
[0.4.1] - 2024-10-09
YANKED
[0.4.0] - 2024-10-09
YANKED
OSLC4Net 0.3.0-alpha
Changelog: https://github.com/OSLC/oslc4net/blob/master/CHANGELOG.md#030-alpha---2023-04-29
Now Available on NuGet: https://www.nuget.org/profiles/OSLC4Net
Full diff: v0.2.3...v0.3.0-alpha
OSLC4Net Core SDK 0.2.3 Snapshot
This is an initial snapshot zip of the OSLC4Net Core SDK. It includes libraries for OSLC provider and consumer development and an RDF/XML provider to assist with marshalling and un-marshalling of RDF/XML to and from .NET objects.
The 0.2.2 release also includes more advanced client libraries, query facilities and OAuth support.
The 0.2.3 release added Turtle serialization and deseralization support.