ServiceStack Development Tooling? -

Not sure if this is the most effective place to ask this question or not.

I am currently making some tooling in Visual Studio 2013 (using NuPattern), which implements the standard REST service using the ServiceStacks Framework. That is, tooling helps you apply the comfort services, which meet the design rules and guidelines (in this case advocated by the API guidelines) for good comfort service design.

Service developers based on a few simple configurations, for each resource they want to expose as the other end point, with any number of named actions (type: GET, PUT, POST or DELETE) Tooling builds the following code files with the traditional name and folder structure in the project, with its own solution in Visual Studio (all at C # at this point):

• Service class, and each Named Action Service service interface
• Both requests DTO
• Each request validates the DTO field.
• A manager class (and interface) that handles real calls with unwanted data from DTO.
• Integration test that verifies each verb with common edge test cases, and verif
• The unit test for each service and manager category, which is the criteria and common thread cases Verify, and exception handling.
• etc.

Toolkit is proving to be very useful in directing directly to internal coding of the actual service, keeping in mind a consistent manner of SS Plumbing. From there it is basically up to you that what you do with the data supplied from the DTO. Basically, once the service developer names the resources, and chooses the rest of the tasks they want to support (usually any of these: get, list, update, delete) In addition to worrying about plumbing in all types of coding and SS infrastructure around web functions, they jump straight to the implementation of the actual code, do good things. Of course, we support nested routes and these good things so that your REST APIs can be developed appropriately.

The toolkit is evolving because more information is obtained about the rest of the services with service stacks, and as we want to add more flexibility,

Since our special projects are being searched for a lot of value with this toolkit, I have to see that other people in the Service Stack community (especially new or old hands on them) will see us Helping others to move forward with service stacks to help in developing its open source, and helping the community with its expertise? (And, of course, selfishly we have been given the opportunity to pay further for others; Out of respect for many contributions to others, service is made undoubtedly in the Stax Communities, who have helped us to move forward.)

Tell us what you think, we can post a video while displaying the Toolkit, because now it is you can experience the experience of the developers.

VS.N.T. Video Walkthrough of Extensions

A video that runs through a workflow is available here:

Toolkit Project

Toolkit is now available here:

< / Div>