Hi meek Wayne :) I'm sad to hear that you had problems with DbLinq and VB. DbLinq works (in theory) just like Linq to SQL, so any simple sample code you can find in MSDN should do the trick. What database do you work with? If it is not Oracle or SQLite (note to Thomas: that's the second non-working vendor), then you can use the latest SVN sources. We currently have problems with insert on Oracle and SQLite, but everything else should work fine.
And if you feel like meekly contributing to DbLinq, you're welcome. We are lacking of VB developpers, and VB generates some strange expressions that sometimes DbLinq doesn't know how to parse. We have a unit test project in VB.NET working on MySQL, so if you have examples of problems, you can add them there and make required changes in ExpressionLanguageAnalyzer class (which handles all special constructs and translates them to standard ones). It's up to you. Any contributor is always welcome (even the meek ones ;)) (proud) Pascal. On Tue, Sep 9, 2008 at 05:41, Wayne Pedersen <[EMAIL PROTECTED]> wrote: > Hey all - > > My name is Wayne - I was introduced to DBLinq via some Googling only about > a month ago. I could not get it to work, but that did not discourage me (I > do not think it was producing all the correct code in VB.Net). I've been > developing small client/server apps in VB.Net since 2002 and I see the huge > benefit of DBLinq. I would not want to see this project die or shelved. > > LINQ is just too awesome for developers to leave alone, but the only tools > available bind one to Microsoft only database world. > > I am by no means an expert developer, and I am learning C# on my own. I > would be willing to test and bang on the code, developing minor patches. I > don't want to get in over my head, or make myself out to be an awesome > database junkie - I am not. > > But, if I can help in some little way - I would like to see this project be > able to achive true VS 2008 integration. I have never helped in an open > source project, and I believe the experiance would be a great one, but I > will need guidance. > > The meek are here to learn and help; are there mentors to guide and teach > the meek in this project as well? > > Wayne > > > > On Sat, Sep 6, 2008 at 3:36 PM, Pascal Craponne <[EMAIL PROTECTED]> wrote: > >> Hi everyone, >> I write this message as a kind of blog post. Since I have no blog and it >> relates to DbLinq, the right place to publish seemed to be here. >> >> it's been a long summer, with thoughts and expectations. >> >> VS2008SP1 came out, along with Linq to entities (a.k.a. the ADO.NETentity >> framework). I've read the documentation, gave it a try, and it >> appears to be insufficient (at least to me). There is a higher abstraction >> level, but you need to start from an existing database, leaving all initial >> modeling useless, and the extensibility isn't that great. Apparently, a lot >> of people are disappointed by the entity framework (see >> http://efvote.wufoo.com/forms/ado-net-entity-framework-vote-of-no-confidence/) >> so let's just forget it for now. >> I also took a look back at NHibernate, which is a great product too. >> Anyway, the linq support is late, and some major performance problems were >> found. >> In fact, I realized this summer that I love Linq to SQL: it is a simple >> and quite complete product. >> >> I had a chat with George Moudry (DbLinq's owner) and there was the >> question to freeze the project, since George has other plans, and I was a >> bit tired of spending my nights on DbLinq. >> >> But I just can't give up. Some projects are still waiting for DbLinq, and >> we're not far from something usable (for a professional use). >> Leaving the project would also be unfair for people like Pablo and the >> mono team. >> Beside this, it is easy to extend, and was sometimes fun to write. >> So I'm probably going to code less, and work more as a project manager, if >> you contributors agree. >> >> So the next steps are: >> 1. Releasing a version with new engine. This requires some fixes on the >> "insert" code (Thomas, if you read this, please let me know). >> 2. Add the missing essential features and get a product close to Linq to >> SQL. >> 3. Extend (I have the strong problem of generating only one source file >> from the dbml, so the code can not be used in a lose coupled n-tier >> architecture). >> 4. Support a zillion databases (that's the fun part). >> 5. Be rich, famous, and let naked girls come to us. >> >> Are you here guys? We've got some work :) >> >> -- >> Pascal. >> >> jabber/gtalk: [EMAIL PROTECTED] >> msn: [EMAIL PROTECTED] >> >> >> >> > > > > -- Pascal. jabber/gtalk: [EMAIL PROTECTED] msn: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
