Is there any ToDo app that have .NET api for server side adding tasks.
Since there is no API for Goggle Tasks, I am looking for something that I can feed
from my own custom Tasking Web App.
Here in our company We are using our custom madded Web App for tasking and organizing our work.That app is written in .NET with C#. Now I looking for some Android apps for tasking which is able to on server side receive task by .NET and C# api.
Remeber The Milk looks nice and have IronCow as API but that app is commercial for android devices.
Is there others similar services as Rember The Milk that have this both, C# api for server side adding tasks and good looking Android client
In case you missed the Google I/O announcement, now there is an API for Google Tasks, with .NET and Android/Java support.
Related
I need to develop an ASP.NET MVC website that takes information from ArcGIS to show maps and other data. ArcGIS is currently running on a local PC so ArcGIS data would need to be exported to some format and uploaded to the server where the website runs so the ASP.NET MVC application takes it and do its job. After some research I found that there are (at least) 3 different ways to interact with ArcGIS: Javascript API, SDK for .NET and ArcObjects.
What would be a solution in order to take the ArcGIS exported data and work with it in ASP.NET? Is this a feasible or possible approach?
Every ooption of the listed by you, has an specific target:
ArcGIS Javascript API: it is designed to be used in webbrowsers, it shows geographic information using javascript, mainly it is intended to connect to ArcGIS Servers, as well as OGC Servers.
ArcGIS Runtime SDK for .NET: if you plan to develop a desktop application with WPF, this is your tool. Last versions of this SDK is also intended for Windows Presentation Foundation (WPF) apps, Universal Windows Platform (UWP) apps, native mobile apps in C# for Android, iOS
ArcObjects:The classic one, this SDK allows you to create WinForms applications with geographic information, also allows to create console applications for automate operations that involve geographic information or maps, it runs over .NET Framework.
ArcGIS Server is a proper way to achieve what you are trying to do. I assume you don't have and don't intend to have one.
You can go with a poor man's GIS server implementation as you described above: put files on server, then write services which would parse those files and provide geometries in a format that your client side can understand. There are various libs for working with esri shapefiles so you could find what suits you.
If you plan to use ArcGIS Runtime to implement your own server I would advise to check licensing because usually it won't allow you as it is licensed per client deployment.
I would advise you to check what ArcGIS Online can offer. Upload you data to their cloud and consume it with your Javascript API. Look at the pricing and maybe free plan will suit your needs. https://developers.arcgis.com/pricing/
I am interested in developing a Windows Forms application that periodically checks if my database has new entrances for a table that abstracts event scheduling.
If new events have been added to the database, my application should get those events and post them to the Office 365 Calendar.
I've been researching for a while and have not found a proper way to call Microsoft Graph API services from within a Windows Forms application.
Is it possible to do so?
There is a Microsoft Graph .Net Client Library available but you will first need to upgrade the version of .NET you're currently targeting to at least v4.5.
Alternatively, you can call into Microsoft Graph using either WebClient or HttpWebRequest. This will require you to construct all your calls and handle serialization/deserialization on your own however. You can find some additional details in this answer as well: HttpClient does not exist in .net 4.0: what can I do?
My guidance would be that unless you're very familiar with HTTP and Serialization, I would focus on upgrading your .NET target and use the SDK. Hand-crafting REST and OAUTH calls is typically not a very enjoyable experience.
I am working in application have iOS native application as front end and c# .net as back-end.
Currently I am using WCF REST API for any communication between iOS client and server.
In my application there hare two types of user "Administrator" and "Simple User".
Application have some features those should enabled for admin user only and for "Simple User".
I just need help to create application structure so I can easily maintain features as per end user role.
Also, feature are dynamics and will be added new features in future.
If you are starting with a new service, try switching to Web Api instead of WCF REST API as it is no longer supported by Microsoft.
http://www.asp.net/web-api
You could start using authorization module provided by Asp .Net. This is similar to what you use in an Asp .Net MVC application.
I'm planning to develop a SharePoint 2010 native iOS solution with some basic features like login and fetch content. Are there any RESTFul web services exposed by SharePoint to work on, which lists the RESTFul web services that we can use?
Is there any initial steps that I need to follow to start up, provided the RESTFul web services are available?
Thanks
Sudheer
I am very new to IOS development.I wonder which language/framework everyone is using to create RESTFUL web services for high traffic, scalable IOS app backend.
The solution requires:
1. Secure Login
2. Restful web services (JSON)
3. High traffic
4. File upload/download
5. Quick search result from large volume database
I am from .NET and MSSQL background. I heard people are using PHP, Java, Python, RoR with IOS webservice development. I understand every language can have pros and cons, just want to know what is prefered in today's trend.
And for database, is NoSQL database a prefered choice than RDBMS for scalable large volume databse? I am checking MongoDB.
Apologies if I am asking wrong questions. I am investigating the technologies for this new project, and any input will be greatly appreciated!
Thanks
I have worked in three major projects that all of them have desktop clients, web clients, and mobile clients (Android, iOS). The 3 have completed different server side approach, and all of them make me and the users happy:
Project 1:
Server: Delphi + RemObjects
Clients: Delphi desktop apps, PHP Web apps, Java applets, Android apps, iOS apps
Why Delphi? Because the existent project was already a Delphi multi-tier app, the development team have domain of Delphi platform, ans was easy with RemObjects (or even with the standard DataSnap) to return JSON, SOAP or XML-RPC to be invoked by the clients;
Project 2:
Server: PHP
Clients: ExtJS Web apps, Android apps, iOS apps
Why PHP? The development team was experienced with PHP, the projects was originally a PHP web app with some classes well defined and not coupled with the UI. Some new classes in the server that reused the existing code base, just converting to/from JSON were enough to allow the clients to talk to the server, with minimum effort.
Project 3 (initial development):
Server: C# ASP.NET
Clients: ASP.NET apps, Android apps, iOS apps
Why C#? Again: the development team was experienced with C# and ASP.NET, the projects was originally an ASP.NET app. We are refactoring some app logic into web services that will be consumed for both the ASP.NET app and the clients.
As you see, there is no need to make the team learn something completely new on the server side.
I'd suggest you to keep your development in .NET with MSSQL, taking advantage of your current skills.
If the application traffic grows you can move the server app to an IaaS server (like Amazon AWS EC2) that supports SQLServer, or even better to a PaaS server, which in this case Windows Azure will probably be your best friend.
These are all loaded questions that can't be answered without more information about what you're making, etc. I use a combination of Ruby with Sinatra and DataMapper (and SQLite/PostgreSQL) for most of my projects, but that's my personal preference and probably won't be of much help to you.
Rather than choosing a technology stack based on trends, why don't you just pick something with a good user base for help and go from there?