I use linq to sql for stored procs, which is easy and greatly reliable.
simple queries work good also.
I don't know why so many people on this site complain about it, it's kinda sad really when MS puts out a product well ahead of any other opensource stuff that's out their.
The ad's are kinda funny too, I have been using vista 64 at home and work for almost as long as it's been out, and the only problem I had is when a hard drive failed on me. It's been really reliable, very secure, no issues that I have experience, so I just don't understand the negative ad(s).
I am using WCF in a project as well, and it's also very fast and easy to work with. I have been a.net developer ever since 1.1, and have upgraded all my stuff to 2.0 the day it came out. And we have had really good results using.net with 3rd party tools like Infragistics.
I haven't read the book, but hey, there is so much information about these topics on the msdn pages, who needs a book?
Slashdot Mirror
I use linq to sql for stored procs, which is easy and greatly reliable. simple queries work good also. I don't know why so many people on this site complain about it, it's kinda sad really when MS puts out a product well ahead of any other opensource stuff that's out their. The ad's are kinda funny too, I have been using vista 64 at home and work for almost as long as it's been out, and the only problem I had is when a hard drive failed on me. It's been really reliable, very secure, no issues that I have experience, so I just don't understand the negative ad(s). I am using WCF in a project as well, and it's also very fast and easy to work with. I have been a .net developer ever since 1.1, and have upgraded all my stuff to 2.0 the day it came out. And we have had really good results using .net with 3rd party tools like Infragistics.
I haven't read the book, but hey, there is so much information about these topics on the msdn pages, who needs a book?