Good details about what errors to log.
For logging requests, check out the RequestLogsFeature:
Yep, something we can look at providing a nicer story around in future.
ok cool, I just moved it over to SS.Interfaces in master:
Hi Mike, Can you provide more info on the dependency issue? All the Swagger Attributes are in ServiceStack.Interfaces.dll which is the only reference your DTOs should need. The Swagger Feature/Implementation itself is a ServiceStack plugin so it needs a reference to ServiceStack, but none of your DTOs should.
Great points, thx Chris!
Awesome, great to hear - thx for the feedback! Releasing signed-builds should improve the SP story too - sounds like you're the point of reference to talk about SP as well :).
Funny story is in my last job as a financial contractor where a whole team of WCF devs couldn't get WCF to work within an existing (old) IIS+SharePoint installation, only vanilla ASP.NET would work, so we ended up going with SS instead which as it was just based on standard ASP.NET IHttpHandler's, pretty much works everywhere.
Just another tale of the complexity of merging 2 tech behemoths products together - not even the same company can provide a working solution.AdminDemis J Bellot (Developer, ServiceStack) shared this idea ·
It looks like I'm going to have to go over this use-case with you when I have time Matthew. Issues with this feature is not losing the "auto match" Request/Response DTO with Razor Views and not forcing users to require knowledge of any rules or complex configuration for views structure and layout.
So any solution should be opt-in and not affect existing behavior, I'll have to explore being able to provide an injectable strategy - it might work like you say by just being able to provide a custom fallback strategy for un-matched routes.
This is more an overall strategy than a single feature request, and is also something I would love to realize as I think a lot of this is the future, e.g. deploying stateless vagrant images to great-value clouds like DigitalOcean/Hetzner that encapsulates a stateless "blessed configuration" with redis / postgres / nginx (and maybe companion services like elastic search) pre-enabled, with extensibility hooks to enable CI deployments to the vagrant VM so they can be automatically updated and preferably without downtime.
Unfortunately this is going to have to wait till we're able to hire full-time System Administrators (dependent on whether SS ends up being successful) to be able to research, realize, document and productize re-usable/scriptable/automated solutions. Until then it would be good to farm the research out to the wider community to collect and collate a lot of information in the one place so others have some info to base informative decisions on.
I like it, we could have an admin dashboard with easy access to manage users / roles/permissions, monitor request history, etc.AdminDemis J Bellot (Developer, ServiceStack) supported this idea ·