ServiceStack to expose service to multiple clients? - servicestack

Recently I made the decision to move from Xamarin.Android to native Android development. In the previous Xamarin project I used their walkthrough to call a WCF service from Android with basicHttpBinding, primary purpose in this case to upload a DTO with an image byte array. I'm now trying to figure the best way to do the same (or better) from Android without Xamarin.
Can ServiceStack help me expose a WCF or ASMX service such that most any client (in my case WPF/Silverlight, iOS, Android) can connect to it with the most appropriate message format (SOAP, REST, etc)? If so please point to the best sample for quick adaptation of an existing WCF service hosted in IIS. I'm hoping to get implement quickly for a demo in one week, then circle back and spend more time learning it.
Sincere thanks
Mark

Related

Android studio library

My team and I just developed a web base system. Next, we are planning to build an android mobile app version of the system. But none of us have experience of creating a mobile app. I did some reading from google, I saw many posting about kotlin, volley, retrofit etc.
One thing I still don't understand, can someone tell me how kotlin, groovy are different with retrofit and volley?
Is it just like web base development where one is for front end development and another one is for backend?
My app would need to constantly fetch and submit data to phpmyadmin (which I put in my VPS hosting).
Can someone give me a suggestion which library is the best for me to use to create my mobile app?
Thank you in advance!

Hybrid Mobile App using Icenium

We are working on a Hybrid Mobile app using Icenium.
How do I start using SeriviceStack to develop backend services? Any direction is highly appreciated.
Thank you
Xyler
Here from ServiceStack Wiki
Create your first webservice
For self hosting
Here all the ServiceStack Wiki
and the knowledge base in StackOverflow under the tag ServiceStack
and the Google Groups
there is also a training course (with payment) from
PluralSight- An MVC4, iOS And Android App With ServiceStack, Xamarin and C#
I don't know if it is useful.
this is not real answer, only to point you the wiki.
Others can edit to make it better.

Convert Objective C project to Xamarin

We have an app written in Objective C. It uses CoreData, RestKit, about 10 viewcontrollers.
We would like to migrate it to Xamarin (so we can target Android and Windows).
I was hoping there was a way to bind the current code to a Xamarin solution and kind of rewrite features step by step within Xamarin (eg: replacing a viewcontroller at a time, and at the end replacing RestKit+CoreData, by SQLite + ServiceStack).
I am aware of the binding to Objective C option that they provide, however, it doesn't look to be the appropriate fit for this (way too complex, probably easier to rewrite the app from scratch).
Is there a way to migrate our current project to Xamarin so we can convert? or do we start from scratch?
Thanks.
Options:
Migrate full project - no;
Automatically create binding for libraries, rewrite business-code, UI-code - yes;
Rewrite from scratch using .Net/Mono classes - yes.
If code size is relatively small, you should rewrite the whole app. Moreover, thus you could have a chance to separate business-logic from UI code and tools libraries (RestKit, CoreData). In perspective, that code will be more reliable and cross-platformish.
This tool can help. It does Obj-c to C# translation (some manual cleanup required):
Automagical
Quite probably, a re-write, from scratch. One thing to keep in mind, if your back-end is .net.. and you are using DTO's.. like with AutoMapper from Entity Framework objects.. you'll be able to re-use those DTO objects on your mobile side with Xamarin. If you are using OData, I'm not sure if this is still a problem, but Xamarin studio wasn't generating OData service clients. So you had to generate them in Visual Studio, then take the generated client code and throw them into your Mobile projects.
sqllite-net is awesome. I've never had any problems with it.
https://github.com/praeclarum/sqlite-net
I currently have a project, with DTO Objects from an Azure WCF service, that I push directly down into SQLLite objects on IOS and Android with Xamarin. I use RestSharp, rather than Service Stack. I should probably go learn the difference.
If you are looking to use SQLCipher from the Component store, to encrypt your sqllite db locally on your device (Good advice to do so), you should be aware that there is an issue in android.. going to 2.2 or 2.3 with SQLCipher. Works for ICS and above though, if I remember right.
Just be careful on your security implementation for allowing clients to connect. I want to say.. don't take too much advice.. and don't take too little either. : )

Windows 8/RT + Phone 8 app - sync data

Hi im developing a todo/reminder app for both Windows 8 (RT) and Windows Phone 8.
I want to enable the user to sync their todo-items between these two.
I know there is a roaming application data storage for Windows 8, but is it possible to access it from the phone?
Another idea i had was creating an xml file and uploading it to skydrive, but then i would have no push functionality :(
And there is also Azure which seems to be the most complicated solution..
What way is the best to choose?
Thanks for your help
You can use Live SDK (SkyDrive) and Windows Azure Mobile Services to accomplish this. The Live SDK will allow you to upload and retrieve items from SkyDrive and you can use mobile services for push notifications. Here is an example of what you want to do.
I know that the thread is a bit old, but it still pops up in search results. So, here's the answer.
I had exactly the same problem. So, I have developed a small library which does exactly that - synchronizing the data between Windows Phone and Windows Azure. Code is on GitHub and here is a nicely packed NuGet package. You could easily port it to WinRT and use SQLite as local data storage.
API is very simple. You just call methods to do CRUD operations and when you are done, you call SynchronizeAsync to synchronize data with WAMS. The synchronization goes both ways. In case of conflict, the latest copy gets the preference.
In the meantime Windows Phone 8.1 is released and it changes the answer to your question - today there are universal apps and they share the same roaming storage on both Phone and regular Windows.
You're going to want to use Mobile Services (www.windowsazure.com/mobile) for this scenario. After you login at manage.windowsazure.com, grab the WinStore C# SDK and WP8 SDK. You're going to need to point both to the same SQL db and Mobile Service. Of course, if you need blob or table storage as well, that's supported. You'd just access those through scripts under the DATA tab.
To check out a production app that's already doing this, I'd point your to Slot Machine by the SeeSharpGuys.
Win Store: http://apps.microsoft.com/windows/en-US/app/slot-machine/7c60012a-00bd-4cae-a402-a9885ec11ea1
WP8: http://www.windowsphone.com/en-us/store/app/slot-machine-mobile/9fa24191-d08d-4073-8098-740975e41946

Can existing .net application be converted to MonoDroid?

Can existing .net application(in C#) be converted to MonoDroid? or
Can we port an existing .NET web app to Android using MonoDroid?
MonoDroid is intended to allow you to develop applications in C# as opposed to Java; not as a means to drop an existing application into place.
You asked about a web app, but I'm assuming you mean an ASP.NET web app, which wouldn't map to the Android API, and couldn't simply be copied over. Even taking your HTML and dropping it into something like Titanium would still require a lot of JS tweaking to make it work.
I have a feeling you're looking at a re-write. Maybe if you can provide more details (is this an ASP.NET app, etc.), I could give a better answer.
Yes no problem. But it wouldn't be an automatic process, nor a particularly simple one. All the UI elements, persistence stuff and so on (the platform specific parts of your application) will need to be redone. Depending on your app, and how it is written, this may be a major part, or a relatively small one. The more corners that were cut originally, the more it will cost to port over.
In addition to Tom's answer, I would say it has some limitations(link 1 and link 2) . I blogged some other interesting moments here.
Here is a good example of cross-platform mobile application (monoDroid, monoTouch, WP7).

Resources