Our clients wish to consume our services via PHP.

ServiceStack support for PHP via Service Clients, DTO generation and possibly 'Add Service Reference' would be great!

Would be nice to specify easy to remember alias for custom gist.

Since latest update of ServiceStackVS seems to introduce a bug in VS 2015, the option "Add ServiceStack Reference" is no longer appearing in project context menu. In addition, the ability to update ServiceStack References is broken too.

Where can I download previous version of this extension ?

VS2019 will be released tomorrow, but the current VSIX is not compatible with it. Aside from bumping the supported versions, it should also be updated to an AsyncPackage.

Per https://github.com/JeremySkinner/FluentValidation the latest version is 8.2.3 and it has numerous updates.

For a few of us, we are constrained with having to use mongodb or other nosql databases instead of an RDBMS.

It would be good if we have a some sort of native mongodb support or at least a few examples/patterns of how to go about a full mongodb/servicestack solution. I understand that we have examples of redis usage but, we do not have authentication and other similar aspects as examples.

Love the tooling still! yet hate to work with anything else now (you spoiled us!) that I have to work with mongodb.

Cheers!
-Simo

Support of HStores when using Dictionary<string,string> or as a new field attribute.

HStores (key values) are very good in certain scenarios (logging/auditing) and complex parsing is easier to do in .NET than in SQL.

Custom SQL that SELECT's data is easy, but not easy to insert/save hstore in custom sql.

Also Npgsql already supports them.

More info here:
https://forums.servicestack.net/t/cannot-insert-idictionary-string-string-into-hstore-column/6894

At the moment, the OAuth2 Providers for ServiceStack library does not support .net core, as explained by mythz in this StackOverflow answer:

> ServiceStack's OAuth2 depends on DotNetOpenAuth which unfortunately doesn't support .NET Core so there's currently no support for OAuth2 - https://stackoverflow.com/a/42344183/969613

Google Authentication is a feature requirement on my current project, so this one thing is preventing us from moving to .net core, support for this would be great.

I would like to have an OpenId and OAuth integration with Thinktecture.IdentityServer just like google and Facebook. I would like to implement my own SSO instead of relying on social networking OpenId

The new WebAssembly feature being added to mainstream browsers will download .dll files to the browser. To make it possible to serve static .dll fiiles by default, please add .dll files as mimeType application/octet-stream, and allow these types of files by default.

WebAssembly is a new binary format for static files. The official site has more info. https://webassembly.org/

Google for webassembly mimetype w3c will return many results showing the addition of this file extension and Mimetype in other mainstream servers.

I would like to get the batching support for the Typescript JsonServiceClient as it is supported by the C# JsonServiceClient.

Line 7: protected void Application_Start(object sender, EventArgs e)
Line 8: {
Line 9: new AppHost().Init();
Line 10:
Line 11: }

It'll be really useful to be able to define namespaces for DTO filtering. Currently I can specify Types to include or exclude but doing it by namespace will be much more useful in situations where there are too many types to include or exclude.

My server needs to be able to push messages to my app. Unfortunately, I'm running ServiceStack.Client.Core in a .NET Standard library, which means my app does not have access to ServerEventsClient. Having the ability to use ServerEventsClient in .NET Standard libraries would be amazing.

Asp.NET Core defaults to use a json base appsettings.json configuration. Right now SS has no support for the new standard. I would like to have an IAppSettings implementation for the new format. Maintain different configuration files is less than optimal.

I understand if this is changed it may break projects based on Typescript < 2.4. I propose a new flag or option to serialize enum strings as enum strings instead of string literals. This would minimally allow us to get access to the list of strings available for an enum which is not readily available with a string Literal.

Instead of this:

export type MessagePriority = "Normal" | "Low" | "High";

It would be:

export enum MessagePriority{

Normal = "Normal",

Low = "Low",

High = "High"
}