For example if the API definitions has ExcludeInSchema set, the autogenerated DTOs do not compile due to unrecognized field on the annotation.

Add built-in basic/digest authentication to the android JsonServiceClient/AndroidServiceClient

Hi, currently WebServiceException does not override to string , so that the base ToString() implementation which returns quite "unusefull" info

I suggest to override the ToString method of WebServiceException
to add info such as errorCode, errorMessage, StatusCode, .Responsestatus.Errors .. etc ..

That would turn usefull, expecially when logging, since most logging mechanism dump the ex.ToString() ..

according to this http://stackoverflow.com/questions/22072109/is-there-a-way-to-have-a-servicestack-metadata-page-show-all-the-options-for-an

it's not possible to have enum information show up in the metadata page, but only in swagger .. it would be nice to have such allowed enum values in metadata page as well.

Can you either shelve or update docs.servicestack.net? They appear to be very out-of-date, but keep showing up in search results. While most of the information is relevant, its incomplete and occasionally misleading.

Microsoft's ASP.Net MVC allows users to set breakpoints in Razor views and debug them in Visual Studio. It would be splendid if ServiceStack could do the same

It's possibile to make inheritable some methods in OrmLiteAuthRepository class, to allow custom logics?

For example CreateUserAuth, UpdateUserAuth, CreateOrMergeAuthSession, GetPermissions/Role, Has Permission/Roles, etc

Would like to replicate the functionality from this feature request in LoadSingleById: http://servicestack.uservoice.com/forums/176786-feature-requests/suggestions/6656885-allow-loadselect-to-selectively-load-references

There are bug-fixes and improvements made to the original fluent validation source at:

https://github.com/JeremySkinner/FluentValidation/

The Load* methods already do this internally (sort-of), but allow explicitly creating Where expressions that use a sub-select to get the IDs, instead of the Sql.In() utility. Or possibly reworking Sql.In to support a Select with a single column.

Something like this:
var customers = Db.From<Customers>().Where( ... my complex expression ... ).Select("Id");

var orders = Db.Select<Orders>(q => Sql.In(q.CustomerId, customers);

We use the ServiceStackVS extension to generate TypeScript code for our service.
During development (when the API might still change) it would be really nice is we could generate the TypeScript code as a step in the build process to make sure our TypeScript projects are always build against the latest API (and fail when there are breaking changes).

Although we currently only use the TypeScript generator I assume the same applies to the other languages as well.

It would be nice to be able to take advantage of the Geography type in Sql Server... even better, I wonder if there would be a way to allow "us" to define custom classes for these more advanced data types that are built into a database.

Joining on the same table multiple times results in incorrect SQL being generated by OrmLite.

Table aliases need to be added automatically by OrmLite so the correct SQL is generated when joining on the same table multiple times.

Similar to ServiceStack Bundler, it'd be fantastic to have a node.js-powered email templating system for generating transactional emails with custom data payloads out of a SS app.

It'd be great if the engine worked with simple html templates and CSS so that non-C# people can get involved. Something super simple to use and set up, but powerful in execution.

This would make emails:

• testable
• collaborative (e.g. with frontend engineers)
• iterable (easy transactional email multivariate testing?)
• CSS automatic inlining
• optional integration with litmus.com?

OrmLite T4 templates should generate Views,

ParameterizedSqlExpression.cs not in ServiceStack.OrmLiteV45 Project, It affected use oracle provider in net framework 4.5.

I'd like to have the DTO required(set at DTO and/or service level using current attributes) Authentication & Authorization(roles+permissions) showed within the metadata page, among other operation/dto details.

See SO question http://stackoverflow.com/questions/29693572/how-to-show-authentication-authorization-within-metadata-operation-page.