Support to use @helper not only to call functions in an external assembly (which I think is already supported by SS), but also to call helper functions inside very the same .cshtml template like describied in this link:http://stackoverflow.com/questions/6531983/how-to-create-a-function-in-a-cshtml-template5 votes
Apologies for the delayed notification, this was added over a year ago, here’s an example: https://github.com/ServiceStack/ServiceStack/blob/master/tests/RazorRockstars.Web/Helper.cshtml
One of the most enticing aspects about ServiceStack is that it is incredibly fast. I suggest that all major aspects of SS (web services, text, ormlite) get thoroughly tested in the upcoming versions just to make sure the code base is as fast as it could be.3 votes
v4.5.6 was a perf-focused release: http://docs.servicestack.net/releases/v4.5.6#performance-improvements
The benchmarks framework used to measure ServiceStack performance is at: https://github.com/NetCoreApps/Benchmarking
Change how OrmLite stores complex type properties so they can be stored in formats other than JSV like JSON.56 votes
Support for pluggable complex type serialization was added in v4.0.11, see:
Much of the existing code implements IHttpRequest and IHttpResponse interfaces and writes complete code for implementing these. That was necessary before the redesign in 4.5 implemented mockable versions of the non-inheritable old HttpResponse classes.
I think it can reduce the amount of code in SS and enable use to not need to use global items like HttpContext.Current.Request which results in - non-testable controllers.
The change to help the above situation I implemented grew out of scope, but thought it worthwhile to explore for a later version.1 vote
ServiceStack’s ASP.NET wrapper classes now depend on HttpContextBase, HttpRequestBase and HttpResponseBase.
Details on latest v4 update:
"In the case where you define your DTOs in a portable class library, you won't be able to use IReturn or the NewApi. Perhaps IReturn should be defined in a PCL in ServiceStack. Just a thought."8 votes
PCL Support was added in v4.06, example project at: https://github.com/ServiceStack/Hello
Added in v4.06. See PCL examples for different client platforms at:
v4.06 Release notes at:
An option would be to open the access to Routes.
This would allow to separate the concerns of application workflow in services (describing next operations if required) from route resolution (which could be done in a filter or in the appconfig).13 votes
This would be very nice to have, in both the ServiceStack client AND server. The server part would be preferred, obviously :)108 votes
ServiceStack’s HTTP Caching story has been greatly improved in v4.0.56 which transparently improves the behavior of existing ToOptimized Cached Responses, provides a typed API to to opt-in to HTTP Client features, introduces a simpler declarative API for enabling both Server and Client Caching of Services and also includes Cache-aware clients that are able to improve the performance and robustness of all existing .NET Service Clients – functionality that’s especially valuable to bandwidth-constrained Xamarin.iOS / Xamarin.Android clients offering improved performance and greater resilience.
For more details please refer to the v4.0.56 Release Notes: https://github.com/ServiceStack/ServiceStack/blob/master/docs/2016/v4.0.56.md#http-caching
Add first-class integration for hosting on Amazon cloud services (like MS does with Azure), e.g. adapters for Amazon cloud services, docs on automated deployment/hosting strategies.40 votes
We’ve just released our AWS support in v4.0.48: https://github.com/ServiceStack/ServiceStack/blob/master/docs/2015/release-notes.md#servicestackaws
We’ll continue to expand support for AWS in future, please file separate feature requests for other support for AWS you’d like to see.
Research optimal deployment strategies for hosting ServiceStack on Linux (e.g. nginx FastCGI/ nginx + reverse proxy / self-hosting inside linux daemon) with the best performance, that best supports CI deployment with no downtime, auto restart/recovery when Mono process dies.105 votes
We’ve published our recommended Setup for hosting ASP .NET sites on Linux and Mono is to use nginx/HyperFastCgi. We’ve published a step-by-step guide going through creating an Ubuntu VM from scratch complete with deploy / install / conf / init scripts at [mono-server-config]1.
As well as a guide for hosting ServiceStack with Mono on Docker at: https://github.com/ServiceStackApps/mono-docker-config
Although hosting on Mono is only a Stop Gap as the future and supported option for running .NET on Linux is CoreCLR which will be a priority for us to look at supporting as soon as it’s released. You can vote for the feature request to keep updated on progress: https://servicestack.uservoice.com/forums/176786-feature-requests/suggestions/10286952-support-dnx
Add more MQ Adapters, e.g: Rabbit MQ, Amazon SQS, Azure Service Bus, ZeroMQ/nanomsg.70 votes
Support for Azure ServiceBus was added in v4.5.14 in new ServiceStack.Azure NuGet package:
Please create separate Feature Requests for other MQ brokers.
Add better support for Joins and fetching related records.100 votes
Support for AutoQuery has been added in v4.0.23 which enables instant querying support on RDBMS tables behind clean self-describing APIs, full docs for AutoQuery is available at:
Support for joins have been added to typed SqlExpressions in v4.0.22:
Going to mark off this broad feature as completed as we’ve just completed what we set out to do for this. Please open up new feature requests for more specific features.
Provide better support and testing around Android/iOS builds. iOS's AOT restrictions would likely require code-gen to minimize NoJIT errors.62 votes
Android and iOS PCL client support added in v4.06. See PCL examples for different client platforms at:
v4.06 Release notes at:
Instead of sharing binary dlls with client projects, provide the option for being able to generate DTO's on the client using metadata from a remote ServiceStack instance. The result to be equivalent to sharing the binary DTO dll on the client, where you can continue to use them with generic .NET Service Clients.
Add ServiceStack Reference was added in v4.0.30 which is available in ServiceStackVS VS.NET extension, full docs for this feature is at:
Add a starter template showing how to get started with a Single Page App with AngularJS + Yeoman + GruntJS working together.38 votes
We’ve added a new AngularJS optimized Single Page template with integrated npm and Gulp support at: https://github.com/ServiceStack/ServiceStackVS/blob/master/docs/angular-spa.md
Add optional Strong-named Server and Client NuGet packages so they can be added in the GAC and used inside Enterprise products requiring signed dlls.12 votes
Change NuGet packages so they map 1:1 with ServiceStack projects. So 'Install-Package ServiceStack' doesn't bring in OrmLite and Redis automatically, and we can 'Install-Package ServiceStack.Interfaces' to bring in the minimum dependencies DTO's need.20 votes
The NuGet packages have been refactored in v4 which has the following deps:
Change ServiceStack to be based on IHttpAsyncHandler so services have the option to be non-blocking by returning a Task<T>.75 votes
This has now been done, details on latest v4 update:
Upgrade all projects to .NET 4.0 and change Async APIs on the Service Clients to use .NET 4.0's Task/Future so it can work with C#'s await/async38 votes
All Async ServiceClient API’s now return Task with all tests passing.
- Don't see your idea?