See issue: https://forums.servicestack.net/t/should-csv-respect-dto-datamember-order-value/1799

Help Pluralsight update their videos on Servicestack and/or show how to update their example solutions to the latest version of Servicestack.
Another alternative is to offer an updated version of the videos example code localy (somewhere at servicestack.net/github.com).

I tried to do a update to the latest versions myself and I ran into loads of problems. To the extent that i gave up.

At present, the AspNetWindowsAuthentication is not supported in .NET Core. ASP.NET Core does allow for Windows Authentication (through IIS reverse proxy), so it would be great to have support for this in ServiceStack.

I made an attempt at porting it myself, and it kind of works, though I'm sure I'm missing some subtleties on how it works, as I sometimes get "header already set" errors on some requests. In case this never gets picked up, here's a gist of my attempt:

https://gist.github.com/darkonejr/7bcdcf7aea9fee7d21329fd58de5d43d

Support change MaxLimit of query feature for specific dto

The NativeTypesFeature is used by ServiceStackVS does a great job of looking at all types exposed by Services. However, it fails to include (or exclude via options) any type only referenced via a "ReferencesAttribute" data annotation. This forces me to either create a complete clone of the type just for automatic client DTO generation, or to create an additional dummy service route that exposes this type.

Can the NativeTypesFeature be enhanced to also include Reference(TYPE) and/or References(TYPE)?

We have an application that always return an AppContentResponse<T>. AppContentResponse contains some properties that are present in every response of every method we have, while the T is the actually Type of the response.

When we look at the metadata documentation, ServiceStack generates the documentation for AppContentResponse<T> without also documenting T. The strange thing is that if I create a class that actually implements AppContentResponse<TypeOfThatResponse>, both types get automatically documented.

I filed an issue at https://forums.servicestack.net/t/expand-generic-type-when-documenting-responses/5676 if you are looking for more details.

While some methods of SqlExpression<T> supports up to 15 generic parameters (Where, And, Or) others like Select, SelectDistinct and GroupBy only supports a couple. When building complex queries, it's easy to select data from more than 7 tables, or group by fields from more than 4 tables.

Could you implement more Select, SelectDistinct and GroupBy overloads like you did for Where, And and Or?

There is no specific number of parameters needed, but I think that the default 15 is a good start.

I didn't find support of client side sharding with sentinels in your Redis API. It will be a nice to have feature. I asked this question on stackoverflow, if you have some solution for the problem, it would be great to hear: https://stackoverflow.com/questions/50107173/servicestack-redis-is-sharding-supported-in-sentinel-mode

The generated code does not conform to company rules so I get a bunch of useless warnings when I run code analysis on my solution.

Just adding a

// <auto-generated>
// This code was generated by ServiceStack.
// </auto-generated>

block above or below the /* Options: */ block would be enough to exclude the generated file from code analysis.

The Redis client supports distributed locks, which is a really useful feature, the same is possible using DynamoDB.

Reference Implementation:
https://github.com/awslabs/dynamodb-lock-client

Support Condition Expressions for PutItem, UpdateItem and DeleteItem operations.

https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Expressions.ConditionExpressions.html

I'd like to be able to incorporate my Cognito User Pool as an authentication and role provider.

I think that ServiceStack TypeScript client does not work in NativeScript + Angular2 applications, as I am getting a bunch of weird errors when trying that (in Fetch module).

I installed the module as this:
npm install --save @servicestack/client

Is there support for the TypeScript client in NativeScript applications? If not, Id like there to be =)

Storage Queues are cheaper and more performant than azure service bus if guaranteed first-in-first-out, etc is not required.

They do offer 'At-Least-Once' guaranteed delivery, where Redis is 'fire and forget'.

Combining this with full featured CosmoDb caching instead of Redis would make a compelling low-cost option.

The ServiceStack Stripe library currently doesn't support retrieving of Stripe Events. It would be nice to have this feature especially when working with webhooks.

As it currently stands, I either have to install both the Stripe.net and ServiceStack.Stripe packages in my project, or switch to using just the Stripe.net package.

Some older release notes https://github.com/ServiceStack/ServiceStack/blob/net40/docs/2015/release-notes.md states that Mini Profiler async support is there, but unless I am missing something, using v5.0, I cannot get it to work. Looking at ProfiledCommand, it does not actually overload the async overloads and call IDbProfiler methods.

MiniProfiler integrated this last februari: https://github.com/MiniProfiler/dotnet/commit/8973afb7bd418a37ce38e0805dc3636942ea7788

Two Factor Authentication is a pretty standard thing nowadays, it even comes baked into the typical ASP.NET Core Identity system. It would be nice if Service Stack had this feature as well. We are working on porting a legacy application from ASP.NET to ServiceStack and this is a requirement for government applications (some form of TFA).

ADOMD.net Cubes as a source of data. I think this would be huge in adding a provider to the mix and utilize Analysis Service cubes to return faster data/query's for warehouse service use.

Right now, bools are serialized uppercase since that's the default ToString behavior of .NET.

Consider changing this behavior by checking for bool when serializing and using .ToString().ToLower(), or introduce a setting to control this. It's web standard to use lowercase bools in query strings.

More info/discussion:
https://github.com/ServiceStack/Issues/issues/586