IntroductionIn this series of blogs, I will try to share my thoughts of using ServiceStack 3 in DotNetNuke 6, difficulties, limitations and how I finally solve each problem step by step.
Part 1 - Introduction
BackgroundI started looking at ServiceStack 3 years back when I was working with one of the client who provided ServiceStack services and asked me to use them as back end instead of storing data in DotNetNuke database.
At the end of project, I learned a lot about servicestack.client and associated facilities and then I invested some time using servicestack to deliver rest base services. Now a days ServiceStack and asp.net web API both are obvious options if you are planning to start any asp.net web services along with WCF. It depends on your experience, your team's experience an vision a lot.
After learning ServiceStack, I utilized it in couple of asp.net based projects which are either conversion of cold fusion to .net services or interoperable database independent service development with .net and I was very happy with the way I achieved best results because of ServiceStack
So, some time back, when I started architect a new web platform for one of my recent client, who was using DotNetNuke and wanted their platform to support APIs so that they can be used with navite mobile apps, I decided to use ServiceStack again in this scenario as well!
Try ServiceStack 3 Hello world!
- From Nuget Package Manager Console:
install-package servicestack -version 3
- Since I wanted the base url of the servicestack to start from /api/ instead of / I did some web.config modifications:
- In handlers section added following line:
<add path="api*" type="ServiceStack.WebHost.Endpoints.ServiceStackHttpHandlerFactory, ServiceStack" verb="*" />
- in modules section added following line:
<add name="ServiceStack.Factory" path="api*" verb="*" type="ServiceStack.WebHost.Endpoints.ServiceStackHttpHandlerFactory, ServiceStack" resourceType="Unspecified" requireAccess="Script" allowPathInfo="true" preCondition="integratedMode" />
- If you have webdev enabled, do following to support PUT, DELETE verbers ONLY if these verbs are not working in handlers section:
<remove name="WebDAV" />
I know change dotnetnuke core dll is not good practice. Suggestions are welcome to fix this in the best possible way!
In the next part we will start coding a real api!