I am trying to run Google Earth in a c# application. I did some research and found that the Google Earth API will stop working on December 12, 2015, however, my c# application needs to work longer than that. Is there a way to import Google Earth into a C# Application without using this API?
There are several alternatives. As stated in this thread, you can use:
Cesium
D3js
Kartograph
Another alternative is Google Maps API.
These may not be a perfect match, but depending on your requirements, they may suit your needs well enough.
As to the C# aspect of it, you will need to dig deeper into whichever option you prefer, but I doubt it will be much more complicated than dealing with Google Earth API.
Note: The "Plug pulling" on Google Earth API happened due to security issues. For more info go here
Related
I have a company that needs a document management system.
I have looked at SharePoint but it has far to many bells and whistles. The company wants something that doesn't have intranet portals, app downloads and all the other waffle (they simple don't have the skill nor the inclination to spend thousands learning it).
I am finding that SharePoint is a little like a fork-lift bus truck car. It trying to be everything to everybody which usually ends up useless to all.
My question is does SharePoint Foundation work out of the box as a document management system or is it like an engine you put your own code upon.
The more I read through Google the more conflicting information I come across without any clear definitions.
What I want to end up with is a document management system that has authentication and a simple page / screen / whatever to link / admin to those documents.
As per usual Ill probably end up having to write my own but it would be nice to not keep re-inventing the wheel.
SharePoint definitely has a learning curve, there's no getting away from that. However you don't need to set up all the "bells and whistles" if you just want a basic DMS.
To answer your question, you don't need your own code to get a SharePoint site up and running. You will however need to spend quite a lot of time figuring out what configuration you need for your needs.
We're using SharePoint 2010 Foundation as a simple document repository in a couple of web apps and it works fine. No Wikis, no versioning, no custom pages. That stuff is availablem but we don't need it so we don't enable it. The nice thing about it is the security which hooks into AD so authentication can be set up easily and it is robust. Our DMS solutions are accessed via the internet by users, and internally by apps, and SharePoint can handle that fine by setting up alternate access mapping so that you can get to documents via internal and external URLs.
I won't lie; I've spend a lot of long days cursing SharePoint, but it's still a far better solution than what I could have come up with myself.
In case your wondering, we're using 2010 rather than 2013 because we had been using WSS 3.0 up until this year and you can't upgrade directly from WSS to 2013. But since we only need the basics, doing a second upgrade to 2013 wasn't worth the effort.
The truth is Sharepoint can be used as a sort of document management system (ish). But in truth it is far to over complicated and has gone rather off at a tangent from the demos I was original given when it first came about in the beginning. Alfresco an Nuxio are probably much better. (but even they have their issues). You simple have to look at all three and make your own decisions as now I know this is not a simple question. I personally went for Alfresco but for very exact reasons, even it has some issues but generally speaking it is the best(ish) out of the three. (Nuxio would of been best except for its 'purchase your admin interface' model.
I want to use one of this services for maps in my website. Which do you think I should go for provided that the application is writen in C#. Which is the best SDK for working with this services in C#.
use great maps api instead it is an open source project and very useful. You can change the maps from bing,yahoo to google maps.Of course you should take the api key for google and bing. The documentation is not enough but i think it is very easy to use. Hope this helps.
This is somewhat subjective; however, go for what you believe would provide the best service to your "customers" (whoever they may be). I would not let your determination be based on what "SDK is best" per se, as you can find a hundred examples out there to do both bing maps and google maps. As far as popularity, I would imagine google maps takes the cake:
Try this google maps example: here
I suggest taking a look at this:
http://www.jonasson.org/maps/
I had to make the same decision a couple of years ago, and when using this it was clear that Google Maps had much better satellite imagery, and road data than Bing Maps (specifically in the locations our customers would be using it)
The Bing Maps API is coded in a very familiar .Net fashion. Although its all JavaScript, the Google API feels more like a Java implementation (as you might expect). This take some time to get your head around, but shouldn't really be an issue.
I found the Maps Group on Google excellent as a resource for research and queries.
UPDATE:
Google released v 3 of their API recently and its supports street view as part of the maps API. Pretty compelling reason to use it.
For my needs (and yours may well be very different) the parts of the API I use are easiest to access via Javascript in both cases. The big win for me in the app I'm working on right now is the Silverlight control for Bing maps, and the ease of integration into a WP7 app.
There are various questions (mainly around 2009 to early 2010) discussing use of the Mono framework to write apps in C# and deploy them to iPhone. Also there is some discussion of the Unity Framework, but I'm more interested in a fairly standard UI app.
Has anyone successfully developed and released a commercial quality app using C#/Mono? If so, what were the lessons learnt? Pain points? If you know of other people who have done so, how have they fared?
Thanks!
Mark
The basic answer is yes, there are a lot of applications out there that have been developed using MonoTouch. You can find some nice numbers on Novell's site but there are a ton of games and other application is the AppStore that were developed using MonoTouch.
I would start your investigation by going to review articles that walk through the good and bad of MonoTouch. For example, here is a good starting place:
http://www.bryanthankins.com/techblog/2010/01/17/monotouch-review-porting-an-obj-c-app/
http://www.devproconnections.com/article/mobile-development/review-monotouch-enterprise
Then I would look through some tutorials to see how exactly this is done so you can see if it will fit in your environment. There are a lot out there that show off how to use MonoTouch, including these:
http://vimeo.com/6689472
http://blog.keen-edge.com/category/monotouch/
Finally, I would look at what is happening currently with Attachmate and the takeover of Novell. There are some real issues there that may cause you to reconsider going with MonoTouch. For example, while Mono's future may be unclear at Attachmate, it seems that it might be continued through another company:
http://ostatic.com/blog/mono-continues-without-novell-attachmate
This uncertainty might not be what you want in a project you are counting on so you need to work through that before committing.
I have explored some of the features of LifeRay from past few months. But due to high on hardware and development resource I would not want to go with LifeRay. Is there any good alternative to liferay in asp.net c#. I have seen following CMS application similar to LifeRay. Just want to know if someone has used it.
AxCMS.Net
Umbraco CMS
DotNetNuke
Thanks,
Piyush
We've been throwing around a few of those terms in our office and nearly settled for Umbraco. I think we were satisfied with it but in the end decided to go towards Drupal because of it's wider user-base and support.
I'm trying to figure out how to access the calendar of Exchange 2003 from a remotely hosted ASP.NET/C# page (I only need to read and display calendar appointments/meetings etc.). As I understand it, I'm mainly down to two options - using WebDAV or the Exchange SDK.
I have found some good examples of how to use WebDAV, although I've not yet gotten it to work properly. I haven't looked too close at the SDK yet, and before I spend time on that, I'm wondering if anyone's got any pros and cons with the two different techniques, and any suggestions on which I should go for?
Any useful SDK links would also be greatly appreciated!
As you say there are a number of ways to do this, but webdav is the best bet, as it is supported by MS from managed code where as CDO tend to have greyer shades of support depending on what you are doing.
If you are new to webdav it may be an idea a looking at some of the wrapper classes around as that could speed your dev up. I have used a 3rd party one
http://www.independentsoft.de/webdavex/index.html their support is lighting fast !
The MSDN documentation is probally the starting point
http://msdn.microsoft.com/en-us/library/aa143161(EXCHG.65).aspx
here are others that i have had booked marked before show examples
http://msdn.microsoft.com/en-us/library/aa123570.aspx
http://www.msexchange.org/articles/Access-Exchange-2000-2003-Mailbox-WebDAV.html
http://blogs.technet.com/kclemson/archive/2004/01/23/62247.aspx
http://blog.mbcharbonneau.com/2006/10/26/using-net-and-webdav-to-access-an-exchange-server/