Develop Reference

Neo4j with C# in production

Is anybody using Neo4j with the REST API in production? I've been looking at different implementations of the REST API out there and noticed this one has been downloaded quite a few times
http://hg.readify.net/neo4jclient/overview

Ryan,
I'm one of the devs on the library. Our day-to-day project has a dedicated team of 5 developers, and uses Neo4j in production (on Azure, just for good measure). As we build out our solution, we have kept building the library along the way.
Our solution depends 100% on this library being reliable.
HTH,
Tatham

There are lots of production instances out there, basically anybody using one of the REST bindings, see http://docs.neo4j.org/chunked/snapshot/tutorials-rest.html, is running against it. Maybe ask on the mailing list, http://groups.google.com/group/neo4j/about

You can see a sample application that uses this library and is open source here:
hg clone https://bitbucket.org/romiko/frictionfree
HTH

Just to update this question with a more current option consider using the Neo4jClient from NuGet. The package and links to the project site are at http://nuget.org/packages/Neo4jClient

Accessing A MySQL Database In Silverlight (C#)

I am trying to access a MySQL database in a Silverlight application. I have tried to reference to System.Data.Services to access the SQLClient class, but it says:
You can't add a reference to
System.Data.Services.dll as it was not
built against the Silverlight runtime.
Silverlight projects will only work
with Silverlight assemblies.
I have also tried to add a reference to MySQL.Data, but received the same error.
I have read online that I will need to use a WebService, but I do not know how to make one.
I am using Visual Studio Ultimate 2010, I am targeting PHP and MySQL servers, not ASP, and would appreciate any help.

Alem, Silverlight is a client-side technology.
It will only work in browsers. You cannot just make direct call to a database from your Silverlight app.
First off, this would be a major security issue you don't want to deal so fortunately you are not even allowed to.
Use webservices, or even better: WCF services.
Try this link: http://chakkaradeep.wordpress.com/2008/05/31/silverlight-and-wcf/
Hope this helps.

you can access sql through php:
http://www.silverlightshow.net/news/PHP-MySQL-and-Silverlight-The-Complete-Tutorial.aspx

Which C# SOAP Client Library is easiest to use?

I would like to connect to a SOAP web service using C#. Before I jump right in, trying anything Google throws at me I would like to ask what is the cleanest and best way to do it where most of the work is done for me.
I would like a high level method, where I give it a WSDL and it will basically handle a lot of things for me. I of course don't want to have to do any of the XML, except to see what it is doing to debug.
What is the nicest fanciest library/method that Microsoft has for doing this? Notice that I'm more concerned with optimizing developer time over performance, though there probably isn't much difference in this situation.
Here is a better explanation of what I'm trying to accomplish.
a better OOP approach to multiple SOAP web services

What Assaf said. You have the choice between using a Web reference (wrapper around WSDL.exe) and using a Service reference (wrapper around svcutil.exe). Service references are .NET 3.0+ and part of the WCF way of doing things.
Personally I still use Web references most of the time, but YMMV.
Edit: screenshot of the two menu options :)

That's what Web References in C# projects do.
When you add a web reference it parses the WSDL and creates strongly typed classes for the API.

No need for any fancy library... This is built-in functionality...
Just add a Service Reference to your project right from the context menu in Visual Studio.

Background Intelligent Transfer Service In C#

Anyone successfully using this in c# or is there a better alternative to this? Also any good working project that I can look at and get a good feel? most projects i have come across is in C++ and was looking for a C# project

Yes, we're using it in a tool to let customers upload logs, dumps, etc. to our customer support department. You could use it directly via PInvoke/COMInterop, but I suggest to have a look at SharpBITS.NET, which wraps the BITS interface nicely.

I'm the PM for the BITS team at Microsoft -- and we have a new learn.microsoft.com page that talks about using BITS and C#, plus a brand-new C#/WPF sample on GitHub.

WCF Backward Compatibility Issue

I have a WCF service that I have to reference from a .net 2.0 project.
I have tried to reference it using the "add web reference" method but it messes up the params.
For example, I have a method in the service that expects a char[] to be passed in, but when I add the web reference, the method expects an int[].
So then I tried to setup svcutil and it worked... kind of.
I could only get the service class to compile by adding a bunch of .net 3.0 references to my .net 2.0 project. This didn't sit well with the architect so I've had to can it (and probably for the best too).
So I was wondering if anyone has any pointers or resources on how I can setup a .net 2.0 project to reference a WCF service.

One of those instances that you need to edit the WSDL. For a start a useful tool
http://codeplex.com/storm

What binding are you using - I think if you stick to the basicHttp binding you should be able to generate a proxy using the "add web reference" approach from a .net 2 project?
Perhaps if you post the contract/interface definition it might help?
Cheers
Richard

Thanks for the resource. It certainly helped me test out the webservice, but it didn't much help with using the WCF service in my .net 2.0 application.
What I eventually ended up doing was going back to the architects and explaining that the 3.0 dll's that I needed to reference got compiled back to run on the 2.0 CLR. We don't necessarily like the solution, but we're going to go with it for now as there doesn't seem to be too many viable alternatives

I was using the basicHttp binding but the problem was actually with the XMLSerializer. It doesn't properly recognize the wsdl generated by WCF (even with basicHttp bindings) for anything other than basic value types.
We got around this by added the reference to the 3.0 dll's and using the datacontract serializer.