VS2008 Beta 2 and .NET 3.5 and LINQ [modified]
-
I spent my weekend refreshing and going in details on LINQ and looking at some new features in VS 2008. Beta 2 is the time (In my opinion) to take a look at a particular technology little more seriously in detail. One thing I did not know (confused with the naming .NET naming convention might be the better term) is that no new features where added to the core .NET assemblies like System.Data, System.WIndows.Forms, System.Web etc. These assemblies are still the old framework 2.0 assemblies. I did find a good diagram which expalins what .NET 3.5 here[^]. Now LINQ is present as a set of extension assemblies. The core is still untouched. Only the compilers are modified to provide LINQ support. So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it. Similarily, enhancements is ASP.NET like new controls have been done in an extension assembly: System.Web.Extensions. It includes ASP.NET AJAX and few new controls. I could not find anything new in WPF (apart from some bug fixes probably as some of the assemblies have changed) but seems like there is a new assmbly for some integration of WCF and Workflow: Workflow services (need to do more research on it). There is this System.AddIn framework to allow for custiom addins in applications Managed AddIn Framework[^] which I am not really crazy about. I ran a quick WindDiff on MFC and ATL sources to see if there is something new. MFC has bunch of new methods a a few new classes to support Vista. VC++ also has some new features to support Vista. ATL Server is gone (and now open source available in codeplex). Also there is this STL CLR which I think is one of the most useless thing. I have not done any VC++ development yet to see if there are any improvements to Intellisense. But tomorrow I will convert port a big VC++ solution to see how it works out. LINQ is probably the defining new feature of VS2008/.NET 3.5. Now how well it will be adopted remains to be seen. Also VS 2008 beta 2 is running under perfect harmony with VS 2005. I have not seem any issue so far. -- modified at
-
I spent my weekend refreshing and going in details on LINQ and looking at some new features in VS 2008. Beta 2 is the time (In my opinion) to take a look at a particular technology little more seriously in detail. One thing I did not know (confused with the naming .NET naming convention might be the better term) is that no new features where added to the core .NET assemblies like System.Data, System.WIndows.Forms, System.Web etc. These assemblies are still the old framework 2.0 assemblies. I did find a good diagram which expalins what .NET 3.5 here[^]. Now LINQ is present as a set of extension assemblies. The core is still untouched. Only the compilers are modified to provide LINQ support. So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it. Similarily, enhancements is ASP.NET like new controls have been done in an extension assembly: System.Web.Extensions. It includes ASP.NET AJAX and few new controls. I could not find anything new in WPF (apart from some bug fixes probably as some of the assemblies have changed) but seems like there is a new assmbly for some integration of WCF and Workflow: Workflow services (need to do more research on it). There is this System.AddIn framework to allow for custiom addins in applications Managed AddIn Framework[^] which I am not really crazy about. I ran a quick WindDiff on MFC and ATL sources to see if there is something new. MFC has bunch of new methods a a few new classes to support Vista. VC++ also has some new features to support Vista. ATL Server is gone (and now open source available in codeplex). Also there is this STL CLR which I think is one of the most useless thing. I have not done any VC++ development yet to see if there are any improvements to Intellisense. But tomorrow I will convert port a big VC++ solution to see how it works out. LINQ is probably the defining new feature of VS2008/.NET 3.5. Now how well it will be adopted remains to be seen. Also VS 2008 beta 2 is running under perfect harmony with VS 2005. I have not seem any issue so far. -- modified at
Rama Krishna Vavilala wrote:
Now LINQ is present as a set of extension assemblies. The core is still untouched. Only the compilers are modified to provide LINQ support. So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it.
It's an interesting question - I had thought that .Net 3.x was merely a bunch of extensions to 2.x anyways...
"It was the day before today.... I remember it like it was yesterday." -Moleman
-
Rama Krishna Vavilala wrote:
Now LINQ is present as a set of extension assemblies. The core is still untouched. Only the compilers are modified to provide LINQ support. So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it.
It's an interesting question - I had thought that .Net 3.x was merely a bunch of extensions to 2.x anyways...
"It was the day before today.... I remember it like it was yesterday." -Moleman
v. 3.0 is just a set of extensions (WCF, WPF, WF and CardSpace), but 3.5 will be what 3.0 should have been: new compilers, new features (the above mentioned LINQ, as well as P2P, SQL Compact Edition, anonymous methods, etc.) They did a nasty disservice with the whole 3.0 "version", IMO.
-------------- TTFN - Kent
-
I spent my weekend refreshing and going in details on LINQ and looking at some new features in VS 2008. Beta 2 is the time (In my opinion) to take a look at a particular technology little more seriously in detail. One thing I did not know (confused with the naming .NET naming convention might be the better term) is that no new features where added to the core .NET assemblies like System.Data, System.WIndows.Forms, System.Web etc. These assemblies are still the old framework 2.0 assemblies. I did find a good diagram which expalins what .NET 3.5 here[^]. Now LINQ is present as a set of extension assemblies. The core is still untouched. Only the compilers are modified to provide LINQ support. So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it. Similarily, enhancements is ASP.NET like new controls have been done in an extension assembly: System.Web.Extensions. It includes ASP.NET AJAX and few new controls. I could not find anything new in WPF (apart from some bug fixes probably as some of the assemblies have changed) but seems like there is a new assmbly for some integration of WCF and Workflow: Workflow services (need to do more research on it). There is this System.AddIn framework to allow for custiom addins in applications Managed AddIn Framework[^] which I am not really crazy about. I ran a quick WindDiff on MFC and ATL sources to see if there is something new. MFC has bunch of new methods a a few new classes to support Vista. VC++ also has some new features to support Vista. ATL Server is gone (and now open source available in codeplex). Also there is this STL CLR which I think is one of the most useless thing. I have not done any VC++ development yet to see if there are any improvements to Intellisense. But tomorrow I will convert port a big VC++ solution to see how it works out. LINQ is probably the defining new feature of VS2008/.NET 3.5. Now how well it will be adopted remains to be seen. Also VS 2008 beta 2 is running under perfect harmony with VS 2005. I have not seem any issue so far. -- modified at
Rama Krishna Vavilala wrote:
One thing I did not know (confused with the naming .NET naming convention might be the better term) is that now new features where added to the core .NET assemblies like System.Data, System.WIndows.Forms, System.Web etc.
There is a missing "not" in there, right?
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
My latest book : C++/CLI in Action / Amazon.com link -
v. 3.0 is just a set of extensions (WCF, WPF, WF and CardSpace), but 3.5 will be what 3.0 should have been: new compilers, new features (the above mentioned LINQ, as well as P2P, SQL Compact Edition, anonymous methods, etc.) They did a nasty disservice with the whole 3.0 "version", IMO.
-------------- TTFN - Kent
Kent Sharkey wrote:
They did a nasty disservice with the whole 3.0 "version", IMO.
Yes!
Co-Author ASP.NET AJAX in Action
-
Rama Krishna Vavilala wrote:
One thing I did not know (confused with the naming .NET naming convention might be the better term) is that now new features where added to the core .NET assemblies like System.Data, System.WIndows.Forms, System.Web etc.
There is a missing "not" in there, right?
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
My latest book : C++/CLI in Action / Amazon.com linkcorrected!:-O
Co-Author ASP.NET AJAX in Action
-
v. 3.0 is just a set of extensions (WCF, WPF, WF and CardSpace), but 3.5 will be what 3.0 should have been: new compilers, new features (the above mentioned LINQ, as well as P2P, SQL Compact Edition, anonymous methods, etc.) They did a nasty disservice with the whole 3.0 "version", IMO.
-------------- TTFN - Kent
Absolutly agree. But what can you do. Marketeers - Can't shoot them (unfortunately)
-- Always write code as if the maintenance programmer were an axe murderer who knows where you live. Upcoming FREE developer events: * Glasgow: Agile in the Enterprise Vs. ISVs, Mock Objects, SQL Server CLR Integration, Reporting Services, db4o ... * Reading: SQL Bits My website
-
I spent my weekend refreshing and going in details on LINQ and looking at some new features in VS 2008. Beta 2 is the time (In my opinion) to take a look at a particular technology little more seriously in detail. One thing I did not know (confused with the naming .NET naming convention might be the better term) is that no new features where added to the core .NET assemblies like System.Data, System.WIndows.Forms, System.Web etc. These assemblies are still the old framework 2.0 assemblies. I did find a good diagram which expalins what .NET 3.5 here[^]. Now LINQ is present as a set of extension assemblies. The core is still untouched. Only the compilers are modified to provide LINQ support. So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it. Similarily, enhancements is ASP.NET like new controls have been done in an extension assembly: System.Web.Extensions. It includes ASP.NET AJAX and few new controls. I could not find anything new in WPF (apart from some bug fixes probably as some of the assemblies have changed) but seems like there is a new assmbly for some integration of WCF and Workflow: Workflow services (need to do more research on it). There is this System.AddIn framework to allow for custiom addins in applications Managed AddIn Framework[^] which I am not really crazy about. I ran a quick WindDiff on MFC and ATL sources to see if there is something new. MFC has bunch of new methods a a few new classes to support Vista. VC++ also has some new features to support Vista. ATL Server is gone (and now open source available in codeplex). Also there is this STL CLR which I think is one of the most useless thing. I have not done any VC++ development yet to see if there are any improvements to Intellisense. But tomorrow I will convert port a big VC++ solution to see how it works out. LINQ is probably the defining new feature of VS2008/.NET 3.5. Now how well it will be adopted remains to be seen. Also VS 2008 beta 2 is running under perfect harmony with VS 2005. I have not seem any issue so far. -- modified at
Rama Krishna Vavilala wrote:
I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5.
Heh, i've been a bit curious about that too... would definitely improve my chances of using it for client apps.
every night, i kneel at the foot of my bed and thank the Great Overseeing Politicians for protecting my freedoms by reducing their number, as if they were deer in a state park. -- Chris Losinger, Online Poker Players?
-
I spent my weekend refreshing and going in details on LINQ and looking at some new features in VS 2008. Beta 2 is the time (In my opinion) to take a look at a particular technology little more seriously in detail. One thing I did not know (confused with the naming .NET naming convention might be the better term) is that no new features where added to the core .NET assemblies like System.Data, System.WIndows.Forms, System.Web etc. These assemblies are still the old framework 2.0 assemblies. I did find a good diagram which expalins what .NET 3.5 here[^]. Now LINQ is present as a set of extension assemblies. The core is still untouched. Only the compilers are modified to provide LINQ support. So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it. Similarily, enhancements is ASP.NET like new controls have been done in an extension assembly: System.Web.Extensions. It includes ASP.NET AJAX and few new controls. I could not find anything new in WPF (apart from some bug fixes probably as some of the assemblies have changed) but seems like there is a new assmbly for some integration of WCF and Workflow: Workflow services (need to do more research on it). There is this System.AddIn framework to allow for custiom addins in applications Managed AddIn Framework[^] which I am not really crazy about. I ran a quick WindDiff on MFC and ATL sources to see if there is something new. MFC has bunch of new methods a a few new classes to support Vista. VC++ also has some new features to support Vista. ATL Server is gone (and now open source available in codeplex). Also there is this STL CLR which I think is one of the most useless thing. I have not done any VC++ development yet to see if there are any improvements to Intellisense. But tomorrow I will convert port a big VC++ solution to see how it works out. LINQ is probably the defining new feature of VS2008/.NET 3.5. Now how well it will be adopted remains to be seen. Also VS 2008 beta 2 is running under perfect harmony with VS 2005. I have not seem any issue so far. -- modified at
I know next to nothing about .NET 3.x, but LINQ looks like a bunch of SQL commands in C# code, going to the extent of using keywords for the queries --> if this is wrong, sorry. Read no further and correct me :) I was brought up in the "Avoid inline SQL queries" school and taught to use stored procs instead. Have we come full circle? Are queries in code the "in thing" again? :confused:
Cheers, Vıkram.
Be yourself, no matter what they say. - Sting, Englishman in New York.
-
I spent my weekend refreshing and going in details on LINQ and looking at some new features in VS 2008. Beta 2 is the time (In my opinion) to take a look at a particular technology little more seriously in detail. One thing I did not know (confused with the naming .NET naming convention might be the better term) is that no new features where added to the core .NET assemblies like System.Data, System.WIndows.Forms, System.Web etc. These assemblies are still the old framework 2.0 assemblies. I did find a good diagram which expalins what .NET 3.5 here[^]. Now LINQ is present as a set of extension assemblies. The core is still untouched. Only the compilers are modified to provide LINQ support. So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it. Similarily, enhancements is ASP.NET like new controls have been done in an extension assembly: System.Web.Extensions. It includes ASP.NET AJAX and few new controls. I could not find anything new in WPF (apart from some bug fixes probably as some of the assemblies have changed) but seems like there is a new assmbly for some integration of WCF and Workflow: Workflow services (need to do more research on it). There is this System.AddIn framework to allow for custiom addins in applications Managed AddIn Framework[^] which I am not really crazy about. I ran a quick WindDiff on MFC and ATL sources to see if there is something new. MFC has bunch of new methods a a few new classes to support Vista. VC++ also has some new features to support Vista. ATL Server is gone (and now open source available in codeplex). Also there is this STL CLR which I think is one of the most useless thing. I have not done any VC++ development yet to see if there are any improvements to Intellisense. But tomorrow I will convert port a big VC++ solution to see how it works out. LINQ is probably the defining new feature of VS2008/.NET 3.5. Now how well it will be adopted remains to be seen. Also VS 2008 beta 2 is running under perfect harmony with VS 2005. I have not seem any issue so far. -- modified at
I know very little about LINQ. Before I start learning, can someone explain the following questions to me? What is the advantage of using LINQ? Performance? Easier Coding? If LINQ does not accept parameters, how LINQ protect the application from SQL injection attack? How can we control database security? I often grant only Excute permission to users so that users can only use pre-defined queries. They cannot modify database other than that. Can LINQ support this feature? Does LINQ work with database other than MSSQL?
petersgyoung
-
Absolutly agree. But what can you do. Marketeers - Can't shoot them (unfortunately)
-- Always write code as if the maintenance programmer were an axe murderer who knows where you live. Upcoming FREE developer events: * Glasgow: Agile in the Enterprise Vs. ISVs, Mock Objects, SQL Server CLR Integration, Reporting Services, db4o ... * Reading: SQL Bits My website
-
I know next to nothing about .NET 3.x, but LINQ looks like a bunch of SQL commands in C# code, going to the extent of using keywords for the queries --> if this is wrong, sorry. Read no further and correct me :) I was brought up in the "Avoid inline SQL queries" school and taught to use stored procs instead. Have we come full circle? Are queries in code the "in thing" again? :confused:
Cheers, Vıkram.
Be yourself, no matter what they say. - Sting, Englishman in New York.
I'm also sharing the same confusion with you. But Linq is said to be a feature through which we can do any type of querying whether it is in memory,xml or even C# objects. But whats the problem in accessing C# objects using C# code and xml using DOM and using procs for DB. I don't know. But let us wait and see how its evolve and how many will actually use it. Sometimes I may need some options for performing join operations in data tables.::rose:
-
I spent my weekend refreshing and going in details on LINQ and looking at some new features in VS 2008. Beta 2 is the time (In my opinion) to take a look at a particular technology little more seriously in detail. One thing I did not know (confused with the naming .NET naming convention might be the better term) is that no new features where added to the core .NET assemblies like System.Data, System.WIndows.Forms, System.Web etc. These assemblies are still the old framework 2.0 assemblies. I did find a good diagram which expalins what .NET 3.5 here[^]. Now LINQ is present as a set of extension assemblies. The core is still untouched. Only the compilers are modified to provide LINQ support. So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it. Similarily, enhancements is ASP.NET like new controls have been done in an extension assembly: System.Web.Extensions. It includes ASP.NET AJAX and few new controls. I could not find anything new in WPF (apart from some bug fixes probably as some of the assemblies have changed) but seems like there is a new assmbly for some integration of WCF and Workflow: Workflow services (need to do more research on it). There is this System.AddIn framework to allow for custiom addins in applications Managed AddIn Framework[^] which I am not really crazy about. I ran a quick WindDiff on MFC and ATL sources to see if there is something new. MFC has bunch of new methods a a few new classes to support Vista. VC++ also has some new features to support Vista. ATL Server is gone (and now open source available in codeplex). Also there is this STL CLR which I think is one of the most useless thing. I have not done any VC++ development yet to see if there are any improvements to Intellisense. But tomorrow I will convert port a big VC++ solution to see how it works out. LINQ is probably the defining new feature of VS2008/.NET 3.5. Now how well it will be adopted remains to be seen. Also VS 2008 beta 2 is running under perfect harmony with VS 2005. I have not seem any issue so far. -- modified at
Thanks for sharing what you've found. I'm really interested in this very last sentence
Rama Krishna Vavilala wrote:
tomorrow I will convert port a big VC++ solution to see how it works out.
It would be appreciated if you can tell us about the performance as well. I downloaded VS.Net2005 trial a while back and now it's no longer on my machine because I use MFC and it's too slow to work with. I even disabled intelligence but it was still very slow. It takes days to download something this big for me, and comments like this are really invaluable. Thanks. Got my 5.
// "Life is very short and is very fragile also." Yanni
while (I'm_alive)
{
cout<<"I love programming.";
} -
I know next to nothing about .NET 3.x, but LINQ looks like a bunch of SQL commands in C# code, going to the extent of using keywords for the queries --> if this is wrong, sorry. Read no further and correct me :) I was brought up in the "Avoid inline SQL queries" school and taught to use stored procs instead. Have we come full circle? Are queries in code the "in thing" again? :confused:
Cheers, Vıkram.
Be yourself, no matter what they say. - Sting, Englishman in New York.
Inline text-based queries are bad because they are 'invisible' to the compiler (and so cannot be checked, are difficult to maintain, e.g. if you alter a table structure. With LINQ and other data layers these arguments are void as the data is accessible to the program. There are other arguments for stored procedures but this article[^] might persuade you otherwise. I have to state that I rarely use SP's myself, so have never had to convert. I often feel very happy about this when I see other peoples apps with hundreds of SP's to maintain, with half their business logic is in the database and half in their business logic layer code.
'Howard
-
I know very little about LINQ. Before I start learning, can someone explain the following questions to me? What is the advantage of using LINQ? Performance? Easier Coding? If LINQ does not accept parameters, how LINQ protect the application from SQL injection attack? How can we control database security? I often grant only Excute permission to users so that users can only use pre-defined queries. They cannot modify database other than that. Can LINQ support this feature? Does LINQ work with database other than MSSQL?
petersgyoung
petersgyoung wrote:
Does LINQ work with database other than MSSQL?
Well, I just ask that at REMIX, and the answer was, you have the provider model and so you can do the support for the database you use. It is unclear if Microsoft will ship it initially with providers done for other databases, or will do some in the future.
-
Inline text-based queries are bad because they are 'invisible' to the compiler (and so cannot be checked, are difficult to maintain, e.g. if you alter a table structure. With LINQ and other data layers these arguments are void as the data is accessible to the program. There are other arguments for stored procedures but this article[^] might persuade you otherwise. I have to state that I rarely use SP's myself, so have never had to convert. I often feel very happy about this when I see other peoples apps with hundreds of SP's to maintain, with half their business logic is in the database and half in their business logic layer code.
'Howard
Yup but that's "because" the business logic is in the database layer. Make sure you don't do that and it ceases to be an issue. In very rare circumstances I will code a SP to do more than a simple (or simplish) insert, delete, update or select (like some funky search algorithm for example). As far as I can see, I get all the benefits of SPs this way. Stores execution plans, the ability to map a software object onto a slightly different db structure without upsetting client code etc. However, I will read the article :)
The only thing unpredictable about me is just how predictable I'm going to be.
-
Inline text-based queries are bad because they are 'invisible' to the compiler (and so cannot be checked, are difficult to maintain, e.g. if you alter a table structure. With LINQ and other data layers these arguments are void as the data is accessible to the program. There are other arguments for stored procedures but this article[^] might persuade you otherwise. I have to state that I rarely use SP's myself, so have never had to convert. I often feel very happy about this when I see other peoples apps with hundreds of SP's to maintain, with half their business logic is in the database and half in their business logic layer code.
'Howard
OK, you're right about text based queries being bad. But if I want to add a condition, with LINQ, I have to change the C# code, recompile and redeploy. If it's in the stored proc, I just have to add the condition within the proc, and there's no other hassle. Thanks for the article; I'll read it from home. :)
Cheers, Vıkram.
Be yourself, no matter what they say. - Sting, Englishman in New York.
-
I spent my weekend refreshing and going in details on LINQ and looking at some new features in VS 2008. Beta 2 is the time (In my opinion) to take a look at a particular technology little more seriously in detail. One thing I did not know (confused with the naming .NET naming convention might be the better term) is that no new features where added to the core .NET assemblies like System.Data, System.WIndows.Forms, System.Web etc. These assemblies are still the old framework 2.0 assemblies. I did find a good diagram which expalins what .NET 3.5 here[^]. Now LINQ is present as a set of extension assemblies. The core is still untouched. Only the compilers are modified to provide LINQ support. So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it. Similarily, enhancements is ASP.NET like new controls have been done in an extension assembly: System.Web.Extensions. It includes ASP.NET AJAX and few new controls. I could not find anything new in WPF (apart from some bug fixes probably as some of the assemblies have changed) but seems like there is a new assmbly for some integration of WCF and Workflow: Workflow services (need to do more research on it). There is this System.AddIn framework to allow for custiom addins in applications Managed AddIn Framework[^] which I am not really crazy about. I ran a quick WindDiff on MFC and ATL sources to see if there is something new. MFC has bunch of new methods a a few new classes to support Vista. VC++ also has some new features to support Vista. ATL Server is gone (and now open source available in codeplex). Also there is this STL CLR which I think is one of the most useless thing. I have not done any VC++ development yet to see if there are any improvements to Intellisense. But tomorrow I will convert port a big VC++ solution to see how it works out. LINQ is probably the defining new feature of VS2008/.NET 3.5. Now how well it will be adopted remains to be seen. Also VS 2008 beta 2 is running under perfect harmony with VS 2005. I have not seem any issue so far. -- modified at
Rama Krishna Vavilala wrote:
So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it.
You'd have to track down every LINQ assembly in the GAC and every referenced assembly that doesn't already exist in .NET 2. While it runs on the 2.0 CLR it still requires its own support assemblies to work. It would probably not be a good idea to start distributing a LINQ assembly pack for .NET 2.0 with your LINQ applications.
-Matt Newman
-
OK, you're right about text based queries being bad. But if I want to add a condition, with LINQ, I have to change the C# code, recompile and redeploy. If it's in the stored proc, I just have to add the condition within the proc, and there's no other hassle. Thanks for the article; I'll read it from home. :)
Cheers, Vıkram.
Be yourself, no matter what they say. - Sting, Englishman in New York.
Not quite how I see the difference. Here is what the alternatives look like to me from my perspective: SP: 1. I am working on my application in Visual Studio, when I want to add a new query. 2. I have to load SQL manager, connect to the DB, open stored proc's, create a new SP 3. Write stored procedure. Remember you have no intellisense or redlining of invalid syntax, etc. 4. Go to my datalayer generator: refresh datamodel from DEV db 5. Go back to VS, rebuild the datalayer code so new SP is compiled and visible 6. Hope that the SP result set (which is untyped as far as the datalayer is concerned, and could be either a single scalar value or a set of unknown tables) matches what I expected it would be when I try to handle the results. 7. Build the app LINQ/my datalayer approach: --------------------------- 1. Working in Visual Studio, locate the place where I want to write the query 2. Write the query in LINQ or my datalayer 3. Build the app By all means stick to SP's if that's what you find easiest, but the rest of the world is moving on.
'Howard
-
I spent my weekend refreshing and going in details on LINQ and looking at some new features in VS 2008. Beta 2 is the time (In my opinion) to take a look at a particular technology little more seriously in detail. One thing I did not know (confused with the naming .NET naming convention might be the better term) is that no new features where added to the core .NET assemblies like System.Data, System.WIndows.Forms, System.Web etc. These assemblies are still the old framework 2.0 assemblies. I did find a good diagram which expalins what .NET 3.5 here[^]. Now LINQ is present as a set of extension assemblies. The core is still untouched. Only the compilers are modified to provide LINQ support. So LINQ still runs on the old 2.0 runtime. I wonder whether it is possible to re-distribute LINQ applications without redistributing the entire .NET 3.5. Should be possible but I have not done any research on how to do it. Similarily, enhancements is ASP.NET like new controls have been done in an extension assembly: System.Web.Extensions. It includes ASP.NET AJAX and few new controls. I could not find anything new in WPF (apart from some bug fixes probably as some of the assemblies have changed) but seems like there is a new assmbly for some integration of WCF and Workflow: Workflow services (need to do more research on it). There is this System.AddIn framework to allow for custiom addins in applications Managed AddIn Framework[^] which I am not really crazy about. I ran a quick WindDiff on MFC and ATL sources to see if there is something new. MFC has bunch of new methods a a few new classes to support Vista. VC++ also has some new features to support Vista. ATL Server is gone (and now open source available in codeplex). Also there is this STL CLR which I think is one of the most useless thing. I have not done any VC++ development yet to see if there are any improvements to Intellisense. But tomorrow I will convert port a big VC++ solution to see how it works out. LINQ is probably the defining new feature of VS2008/.NET 3.5. Now how well it will be adopted remains to be seen. Also VS 2008 beta 2 is running under perfect harmony with VS 2005. I have not seem any issue so far. -- modified at
Rama Krishna Vavilala wrote:
LINQ is probably the defining new feature of VS2008/.NET 3.5. Now how well it will be adopted remains to be seen.
Well, it depends on what you are writing. If you do web work the enhancements to the IDE for web work is drastic. Then there is the limited built in editor for WPF. Also VS2008 will be able to target different versions of .NET making it a replacement for prior versions instead of having to have multiple versions of VS installed. The LINQ thingy is pretty cool. It has a dark side you have to be aware of and it does kill performance a tad, but it is pretty flexible and offers another level of abstraction for your database. Of course, about the same LINQ syntax works with XML, Object, Entities, etc, so once learned, LINQ sets a new common form of accessing data regardless of the type. For quickie database apps, the new LINQDataSouce allows the results of queries to be hooked up to controls such as grids and lists in flash along with being able to page/edit/update that data without extra code. The simple entities that are build with LINQ2SQL, works great in a data layer within small apps. Even if you wish to use your own objects and database access, LINQ can still come into play access the data within your objects. The current Beta 2 still has a number of quirks and flat out bugs, but I think VS 2008 and .NET 3.5 will be really popular with developers that are not anti-Microsoft and not VC6 was best version crowd.
Rocky <>< Latest Code Blog Post: Windows Live Authentication - Easy Stuff! Latest Tech Blog Post: Vista ReadyBoost!