Microsoft Releases RESTier v0.5.0

Microsoft announces the release of RESTier 0.5.0-beta and it is now available on NuGet.
 
The company states,
 
“We are happy to announce that the RESTier 0.5.0-beta is released and available on NuGet.”
 
0.5.0-beta is a big release and it adopts dependency injection in order to provide several flexibilities to users. It also adds numerous new features and fixes some kinds of issues.
 
Microsoft states,
 
“Note beta is used in version is caused by the dependency injection package is not GAed yet, official version number cannot be used. And there is no plan to release 0.5.0.”
 
The company has also created a sample service, with the newest packaging used and which includes numerous new features referred to Trippin Samples for source code. 
 
API changes since 0.4.0-rc2 as per the official blog
  • The concept of hook handler now becomes API service after DI integration.
  • The interface IHookHandler and IDelegateHookHandler are removed. The implementation of any custom API service (previously known as hook handler) should also change accordingly.
  • AddHookHandler is now replaced with AddService from DI.
  • GetHookHandler is now replaced with GetApiService and GetService from DI.
  • All the serializers and DefaultRestierSerializerProvider are now public. But we still need to address #301 to allow users to override the serializers.
  • The interface IApi is now removed. Use ApiBase instead. We never expect users to directly implement their API classes from IApi anyway. The Context property in IApi now becomes a public property in ApiBase.
  • Previously the ApiData class is very confusing. Now we have given it a more meaningful name DataSourceStubs which accurately describes the usage. Along with this change, we also rename ApiDataReference to DataSourceStubReference accordingly.
  • ApiBase.ApiConfiguration is renamed to ApiBase.Configuration to keep consistent with ApiBase.Context.
  • The static Api class is now separated into two classes ApiBaseExtensions and ApiContextExtensions to eliminate the ambiguity regarding the previous Api class.
Microsoft welcomes it’s users by stating,
 
“You and your team are highly welcomed to try out this new version if you are interested in the new features and issues fixed.