I am developing a winform application.I want to provide support for Dropbox in my application. Since my application is .net 3.5 based. I can't use the Dropbox SDK. So, I will be using the rest API. But there are two sets of Dropbox API V1 and V2 for Dropbox. So, are V2 API's stable enough, so that I develop my application using them or should I use the V1 API's.
Answering your question is not that easy since you have to factor in a number of considerations you do not provide information on. Skill level, product time constraints etc all play a role here.
That being said, I have used API V2 but there are some teething issues at times and support / updates are not always lighting quick. API V1 on the other hand have plenty of examples and community support is readily accessible. So my answer would be to use V1 if you favor stability and support over being on the latest release. Even if you use V1 I dont believe you have to fear the API being depreciated very soon, Dropbox has in the past given plenty of notice before they drop support for a API version.
Related
I will explain briefly my situation before asking for recommendations:
Context
Among other topics* I have been asked to develop a REST api that will be on the cloud (Azure)
The current (soon legacy) application works with windows service.
Behind this web API/windows service that receive the data and deserialize it (before serializing again when sending the response) there is Pricing Library which is used to compute data provided by custom-xml format.
The problem
I am quite concerned with compatibility issues as I keep encountering errors due to uncompatibilities from external libs with .NetCore 2.0
I had an issue with log4net as the Pricing Lib is using 1.2.13 version while 2.0.8 is already available. I solved this but I now encounter RealProxy in dotnet core? issue
I feel I will keep encountering new issues and it will be really time-consuming to fix them each time. But perhaps I am wrong since I only want to revamp the web API with .netcore 2 (not the pricing lib) ?
My question
Is it really profitable, performance wise, or functionally-wise, to switch now the web API to .NetCore 2.0 knowing that we call a Pricing Lib in 4.6.2 .Net Framework ? Is it worth to bother that much just to be using the trending framework while the former one is rather mature ?
Many thanks for your answers~ !
PS: I have already googled and read the relevant documentation, I am asking about experience from other users
https://learn.microsoft.com/en-us/dotnet/standard/choosing-core-framework-server
*code optimization, configuring automatic build and deployment, markdown doc etc.
I am trying to determine whether or not to start using ServiceStack V4 for development purposes. I currently use ServiceStack V3 which I am pretty familiar with. My question is though, what are the big differences, aside from licensing costs and ongoing support, between ServiceStack V3 and V4? I know V4 added support for Async funcitons, and Ormlite has improved joining abilities, AutoQuery. Is there anything else that would really be worth making the investment and switching from V3 to V4? It would really be helpful to have a list of improvements and or side by side comparison between the 2 versions of the framework.
The features that are added in each release are now being maintained at: http://docs.servicestack.net/release-notes-history
I m working on a facebook ap with Facebook C# SDK and MVC 3.
One of the problem I m having is: multiple versions of Facebook SDK API with several inconsistent versions. Almost every version there is a change in the API and something that works in one version doesnt work in another. There are also major changes between API versions.
I m using the latest version. (6.0.12). I cant find any documentation on how to use the API.
API website has lot of TODO pages. (http://csharpsdk.org/) and documentation is not concise.
Should I use another SDK ? What do you recommend? or are there any samples I can use for this version?
Thanks.
I'm much in the same boat as you.
I've followed the blog posts from the members of the Facebook c# SDK team, and their reasoning behind doing the latest major re-work of the API. I'm optimistic and think it's a healthy decision, leveraging the majority of the work from the server to the client instead.
In the end, I think it will benefit our applications with a much more scalable and performant solution than before with the earlier SDK. A good thing if your application gets viral.
The earlier versions had good and plenty samples and documentation, I only hope that in time the team will be able to provide that with the newer version as well.
For me, I currently have a v5.0x solution in prod, and I'm very eager to jump on the newer SDK, but I'm holding on for good samples as well, hoping for some magic during the upcoming months.
It's really a question on how long you can wait, I think it's the best SDK out there at this point.
If anyone is having problems with FB breaking old versions like I did, here is a small and brief tutorial I created
http://theocdcoder.com/tutorial-integrating-facebook-authentication-asp-net-mvc-3/
I found one .net wrapper for google maps api v3 here.
But in that link it has not mentioned weather it supports API V3 or not.
Also can some one point me towards using this dll in asp.net mvc 2 application?
Not sure how useful this answer is but here I go.
I wouldnt choose any wrapper out there without doing some research about the same. From the url that you shared looks like there is only 1 contributor to the project, also the dwnld count on the latest api is 117 which I dont think is a great number to warrant its use, there have only been 3 issues reported so far and from the looks of it they are inquiries or feature requests (not sure if it means that there are no bugs in the project or it hasn't been used).
Anyways having said that there are commercial wrappers out there which support google maps. I can think of ThinkGeo for one. see if that is within your budget.
Now to your dll question. Just adding a reference in your web project should do the trick and then probably creating a seprate controller that serves your map. Is that what you wanted?
.NET wrapper libraries for the Google Maps API :
GoogleApi
google-maps
https://stackoverflow.com/a/61531795
Does anyone know, how I can use OpenStreetMap inside my Compact Framework application? Is there a Framework or something like that? All I can find in their wiki is how to contribute to their project and to user their software to map data. But I want to use their maps to show the users location inside my own app. I could not find anything about using their web service or whatever I have to use to show their maps inside my application.
There is a project on Google Code that wants to create a .NET library for the OpenStreetMap API. The website states that there currently is an alpha release, so it might be worth checking that out: code.google.com/p/openstreetmapnet
And there are two similar projects on CodePlex as well:
osmscout.codeplex.com
gmap4dotnet.codeplex.com
Maybe those can be used in the Compact Framework as well, or you could ask the project teams to add that feature (or get involved yourself, it is opensource after all).
CloudMade provides APIs for embedding OpenStreetMap maps in many languages - but not .NET as of the time of writing. There are plain HTTP APIs for map tiles available that you could call from .NET programs, but this is of course fairly low-level.
The CloudMade APIs are designed for developers who want to embed OSM output in their projects, rather than the OSM API which is geared towards map creation, so I think you might be interested in the CloudMade stuff.
See http://developers.cloudmade.com/projects for more.
They don't appear to have any CF libraries, but the API specification is well documented, so there's no reason you couldn't integrate with it.
I've developed a CF component that can download OpenStreetMap tiles, and also plot points of interest and basic routes. Depending on your requirements, and any restrictions on licences that you're permitted to use, then it may be of use to you?
Brutile looks quite promising. It is a library designed for C# to connect to OpenStreetMap sources. (Silverlight demo available Here.
The wiki also has a listing of all .NET related pages. Of the documented projects, OpenStreetMapViewer looks like it fits your needs the best. It's designed to display a portion of OpenStreetMap within a .NET app. I'm sure at least one of these will work for windows mobile.