By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,185 Members | 1,420 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,185 IT Pros & Developers. It's quick & easy.

LINQ

P: n/a
Hello NG,

we are currently beginning to port our Software from
VB6 to .NET. At the moment I am looking for an object
oriented way to do data-access. LINQ to SQL came in
my mind as a very good approach. As Orcas is still
available only as a preview we want to write our new
code for the .NET Framework 2.0. The problem is,
there is no LINQ support so we would have to do another
port at the time Orcas is released.

What i am looking for, is an intermediate approach. Like
implementing a small subset of the DLINQ interface on the .NET 2.0
Platform for switching to .NET 3.5 with as less effort as
possible. We already have built a Framework for dynamically
generating SQL Queries for different databases with convenience, so this
would be easy at least for simple CRUD operations.

Does anybody know if there is a simple way to parse LINQ
queries so we could now do something like :

Query<Customer= QueryParserWhateverNameYouHave.Parse<Customer>("fr om c
in customers select c")

and later on just skip to

var q = from c in customers select c

via text replace ?? I know we could create a parser with tools
like ANTLR.

Or do you have any other idea on how to solve the problem ? Any ideas ?
Perhaps you can provide a better way or do think that this intermediate
step is crap. Arguments ?

Thanks in advance,
Philipp


Jul 9 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Free or for a price?

For a price, you can pick up Genome. While not precisely LINQ they use a
query language (OQL) that will make it easier to move to LINQ.

NOTE: There should be a go live for VS 2008 (Orcas) by fall. It is your
decision whether or not to release on a supported beta or not, of course.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
Co-author: Microsoft Expression Web Bible (upcoming)

************************************************
Think outside the box!
************************************************
"Philipp Brune" <he****@gmx.dewrote in message
news:eT**************@TK2MSFTNGP06.phx.gbl...
Hello NG,

we are currently beginning to port our Software from
VB6 to .NET. At the moment I am looking for an object
oriented way to do data-access. LINQ to SQL came in
my mind as a very good approach. As Orcas is still
available only as a preview we want to write our new
code for the .NET Framework 2.0. The problem is,
there is no LINQ support so we would have to do another
port at the time Orcas is released.

What i am looking for, is an intermediate approach. Like
implementing a small subset of the DLINQ interface on the .NET 2.0
Platform for switching to .NET 3.5 with as less effort as
possible. We already have built a Framework for dynamically
generating SQL Queries for different databases with convenience, so this
would be easy at least for simple CRUD operations.

Does anybody know if there is a simple way to parse LINQ
queries so we could now do something like :

Query<Customer= QueryParserWhateverNameYouHave.Parse<Customer>("fr om c
in customers select c")

and later on just skip to

var q = from c in customers select c

via text replace ?? I know we could create a parser with tools
like ANTLR.

Or do you have any other idea on how to solve the problem ? Any ideas ?
Perhaps you can provide a better way or do think that this intermediate
step is crap. Arguments ?

Thanks in advance,
Philipp


Jul 10 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.