Utah Code Camp

3 postsstarted by mkmurray 5,403 viewsoriginal topic

Senior Member
#1
Utah Code Camp is a grass roots technical conference by the developer for the developer. It is completely free and almost all code. Volunteer presenters give sessions about whatever topics they deem may be interesting. It's all about the community.

Utah Code Camp will be held November 1, 2008 from 9am - 5pm with many varying presentations provided througout the day. The schedule and sessions are still being finalized, so you have to keep checking back regularly. http://utcodecamp.com/

Many of the presentations are about .NET, but there are quite a few about Ruby, Java, and other prevelant technologies.

Anyway, the reason I bring this is up is because there is a session being presented by a few Church employees about the FamilySearch API and consuming it with .NET. There's even a free library built specifically for integration with Visual Studio. Here is an abstract from the site:
Developing .NET applications for the FamilySearch Platform

Preview the new FamilySearch Web Services (API) and best practices for consuming them with C# and VB using a free library built specifically for Visual Studio. In addition to learning about the FamilySearch Technical Platform and Developing Network, this presentation will show how to easily create your own FamilySearch software application. We will demonstrate how to access and update FamilySearch data, how to explore your family tree, search a large database of genealogy records, and display and update information about your ancestors.

Speakers: Gordon Clarke and Jimmy Zimmerman
New Member
#2

.NET Api MLS

Hi, I would like to know if there is an API for to extend MLS systems.


Regards.
Ernesto Herrera
Senior Developer
MCTS Web Applications 2.0
Community Administrator
#3
Ernesth wrote:Hi, I would like to know if there is an API for to extend MLS systems.
No, the MLS system does not publish any APIs for extending or modifying MLS functionality (and if it did, it would be a Java API, not a .NET API as the title of your post suggested).
Questions that can benefit the larger community should be asked in a public forum, not a private message.