A preview of AspNetWindowsAuthProvider was added in the v4.0.21 release, see:
@Steve I had some related issues with my users, esp. when they were using IE vs. Chrome. In IIS for the website, I went to "Authentication" module -> Windows Authentication -> Providers (on the right) and changed the order to [ NTLM, Negotiate]
I'm sure this can be implemented with appropriate AD config, but I'd add support for Azure Active Directory as well.
Do you mean to *generate* the primary key via stored proc, or truly have it as a calculated column? If generate, you could always decorate the property in the POCO with "[PrimaryKey]" ,then use an insert trigger to generate the value.
I'd love to see stats around route / DTO performance. I.e., for a given parameterized (ie, strip the parameters) route, show the number of requests, average / max times, etc. I can get some of that via IIS logs, but I have to manually massage out non-query string parameters.
Some other nice-to-have information would be Reids / Cache size, and, via mini-profiler or the like, some sense of DB IO (avg queries / request, queries /sec, DB vs. service time).
Do you mean via the JsonClient? Or within server-side ServiceStack?
Seems like the current problem is no ARM build in the NuGet packages
I've used SqlBulkCopy frequently, and I often have to "tweak" the load parameters. To make this effective, and cross-DB compatible, we'd have to make a BulkLoaderFactory(tablename) Further, I suspect we'd have to create DB-provider-specific "BulkLoader" class that abstracts the most common interfaces....
I've been poking some at this for my own use. The "easiest" approach is if there are two schemas (before & after) and you could migrate between them. However, that defeats some of the benefits of ServiceStack (resilient DTOs, sharing DTO with DB schema). The other approach is to infer the ModelDef from the database, but that could get gnarly quickly. Preference on approach?
The way ServiceStack and SignalR will be able to integrate in future will be through .NET Core’s IApplicationBuilder pipeline which by design supports running multiple frameworks within the same App that can now share the same default route namespace.
From the v4.5.2, ServiceStack now supports running on .NET Core, please see the guide in the full release notes which shows how to register ServiceStack’s AppHost in .NET Core: http://docs.servicestack.net/releases/v4.5.2.html
SignalR for .NET Core has yet to be released but it’s expected you’ll be able to access SignalR via its dependencies registered in .NET Core’s Startup which will also be injected in your Services like normal IOC dependencies.
We’ll update this feature request again with an example showing a demo of ServiceStack + SignalR together in the same App once SignalR is available on .NET Core in 2017.
I've completed an initial typed C# client implementation at https://github.com/jklemmack/ServerSentEvents4ServiceStack. This repo also has a lighter-weight server implementation, where the "data" elements are raw DTOs, and the "event" field is used to govern the categorization of messages.
Any plans on a JsonServiceClient-based C# EventSource client?
Lukas - You can always write a custom HTML template to implement this on your own.