This project is read-only.


stop having fun with the architecture


I think it is a really bad timing to update the architecture of this toolkit.stop having fun with linq and maintain the existing v1.x to support new features and breaking changes from facebook platform.
Closed Jul 31, 2008 at 8:58 PM by pwalke


midowazzan wrote Jul 23, 2008 at 11:15 AM

Are you kidding, mate?

Let them keep the good work.

You can create your own temporary classes for the new features.

ersin wrote Jul 24, 2008 at 10:36 AM

I don't mean the project is bad, I think what they guys did was great.
But as far as I know it is not backward compatible.

therefore I am concerned about if there is a bug:

is it from your application ?
is it from new/changed facebook api's ?
is it from facebook developer toolkit bugs ?

there are 3 unknowns which will cost everyone a lot.We will see, I would rather have the facebook updates to be done first.Once it is up and running, it would be nice to have a version 2 for the new technologies.

Time is short, facebook is released the new profile and we don't have a fully working toolkit at the moment, what is need for an updated version of the existing functions with the linq ?

tomten wrote Jul 24, 2008 at 2:02 PM

Ersin, perhaps you'd like some cheese to go with that whine?

wrote Jul 25, 2008 at 1:50 AM

wrote Jul 26, 2008 at 8:33 AM

wrote Jul 29, 2008 at 9:19 PM

wrote Jul 31, 2008 at 8:58 PM

Please take a look at the 2.0 RC that was just released.  Many of the issues we had with 1.X was how difficult it was to incorporate new changes.  We aren't using Linq2XSD just because it has the sexy name LINQ in the its name.  We are using it primarily because of its ability to generate objects and parsers.  We actually aren't writing using Linq to query the responses.  We could have used xsd.exe to do similar tasks, but the being able to use the backing store of an XDocument makes writing linq queries against our objects easier for future devs.  See this post for more details about Linq2XSD:
Going to your point of not knowing where a but is :
is it from your application ?is it from new/changed facebook api's ?is it from facebook developer toolkit bugs ?
Since the toolkit is a much smaller wrapper, the bug surface of the toolkit is much smaller, indicating that a bug is much more likely to come from either your app, or FB itself.

wrote Jul 31, 2008 at 8:58 PM

nberardi wrote Aug 6, 2008 at 5:09 PM

I have to agree what was the reason to make all the entity classes lowercase? seems like having fun to me.

wrote Feb 22, 2013 at 12:38 AM

wrote May 16, 2013 at 12:10 PM