http://www.sqlmag.com/authors/author/author/5081318/rsscomment/5081318en-USFri, 25 May 2012 10:44:23 GMTFri, 25 May 2012 10:44:23 GMThttp://www.sqlmag.com/article/aspnet/aspnet-jquery-templates-141225#commentsAnchorSun, 27 Nov 2011 11:34:54 GMT
None of the "Related Content" links work ?? ]]>LouALOHSun, 27 Nov 2011 11:34:54 GMThttp://www.sqlmag.com/article/aspnet/aspnet-jquery-templates-141225#commentsAnchorhttp://www.sqlmag.com/article/net-framework2/dragged-kicking-and-screaming-to-entity-framework#commentsAnchorMon, 31 Oct 2011 23:47:07 GMT
I feel your pain. I just finished a feasibility study using EF 4.1. I was thinking it would be future proof and more mature by now. I was also hoping that EF 4.1 would allow you to graphically map your preexisting POCO objects to an preexisting schema and you can start writing Linq queries against it. It certainly seems possible from what Microsoft and their advocates say. What I found, however, was a series of frustrations and hair pulling moments that yielded zero productivity. Yes, you can create entities from existing schemas, create new entities and have it generate a schema, but using preexisting POCO objects and mapping that to an arbitrary schema is either not possible, or extremely difficult to do. You essentially have to edit cryptic XML or write incredibly, verbose and equally cryptic mapping code using their fluent API. You'd think this would be a common scenario with all the legacy databases out there, but obviously not a lot of effort was put into it. Entity Framework seems to work well if you're creating a schema from scratch or using a schema that looks like Northwind. If you're using a poorly designed database, or a legacy one, you may be out of luck as I found out. Linq to Sql is a much better product in that it makes no pretenses of doing anything more that being able to perform CRUD operations on your database using Linq. I'll continue to stick with it for now.]]>joebeazelmanMon, 31 Oct 2011 23:47:07 GMThttp://www.sqlmag.com/article/net-framework2/dragged-kicking-and-screaming-to-entity-framework#commentsAnchorhttp://www.sqlmag.com/article/jquery/microsofts-jquery-templates-extension-136424#commentsAnchorFri, 10 Jun 2011 00:25:40 GMT
Are these templates compatible with mustache.js? Is it possible to use them on the server side as well?]]>robertc64Fri, 10 Jun 2011 00:25:40 GMThttp://www.sqlmag.com/article/jquery/microsofts-jquery-templates-extension-136424#commentsAnchorhttp://www.sqlmag.com/article/aspnet2/a-great-asp-net-resource-next-edition#commentsAnchorThu, 11 Nov 2010 07:29:57 GMT
Great review, very detailed.
Thank you Don.

Luigi]]>Luigi ZambettiThu, 11 Nov 2010 07:29:57 GMThttp://www.sqlmag.com/article/aspnet2/a-great-asp-net-resource-next-edition#commentsAnchorhttp://www.sqlmag.com/article/aspnetmvc/using-renderaction-components-in-asp-net-mvc-2-applications#commentsAnchorTue, 02 Nov 2010 05:12:44 GMT
this is a great tutorial! good explained and very clear, also a thumbs up for the code included!

thx
Kennethvr
http://www.spot-it.eu]]>van RumsteTue, 02 Nov 2010 05:12:44 GMThttp://www.sqlmag.com/article/aspnetmvc/using-renderaction-components-in-asp-net-mvc-2-applications#commentsAnchorhttp://www.sqlmag.com/article/open-source-development/reports-of-ironruby-s-death-are-premature#commentsAnchorSat, 18 Sep 2010 08:35:38 GMT
Why would Microsoft ever want to spread themselves thin and continue to develop and maintain these obscure languages ? They’re committed to VB/C#/F# and the dot-net framework. They’ve done a terrific job with Visual Studio 2010. What they need to focus-on is rapid app development and frameworks. If you look at the new Webmatrix product, that’s exactly what they are doing.]]>SimmsSat, 18 Sep 2010 08:35:38 GMThttp://www.sqlmag.com/article/open-source-development/reports-of-ironruby-s-death-are-premature#commentsAnchorhttp://www.sqlmag.com/article/aspnet2/ambiguous-bulletedlists-and-the-ajax-control-toolkit#commentsAnchorFri, 14 May 2010 11:09:01 GMT
Derenthal, thanks for your comment and for reporting the bug with the comments and rating tool. We’ll get it fixed as soon as possible. -Anne Grubb, web editor, DevProConnections]]>Anne GrubbFri, 14 May 2010 11:09:01 GMThttp://www.sqlmag.com/article/aspnet2/ambiguous-bulletedlists-and-the-ajax-control-toolkit#commentsAnchorhttp://www.sqlmag.com/article/aspnet2/ambiguous-bulletedlists-and-the-ajax-control-toolkit#commentsAnchorThu, 13 May 2010 11:20:11 GMT
This is exactly why I ditched the bug-ware that is the AJAX control toolkit long ago. Anyone remember the ’feature’ that throws commas into your tex boxes in a modal dialog control? And it was really great how every new release created new bugs and made old ones worse. Go with Telerik. Maybe someday MS will stop treating this toolkit like a red headed step-child.
And the invisible button for posting comments on this page is, like, super innovative!]]>DerenthalThu, 13 May 2010 11:20:11 GMThttp://www.sqlmag.com/article/aspnet2/ambiguous-bulletedlists-and-the-ajax-control-toolkit#commentsAnchorhttp://www.sqlmag.com/article/project-plan-dbadmin-sql-server-2008-r2-79/sql-server/efficient-data-management-in-sql-server-2008-part-2#commentsAnchorTue, 27 Apr 2010 04:12:33 GMT
Hi,

Great article on the usage of ColumnSets.

I tried the scripts you have provided for using ColumnSet and I think the use of "\" before the columns for getting the SpecialColumn data is not necessary. I have both SQL 2008 and 2008R2, and checked in both and found it returns all 0 when used with "\" e.g.,
SELECT [DogID],\[BirthDate], \[BirthYear], Characteristics
FROM DogCS
the output is with all zeros
DogID BirthDate BirthYear Characteristics
1 0.00 0.00 1997-06-3062Metacam, Phenylpropanolamine, Rehab Forte

For this query
SELECT [DogID],[BirthDate], [BirthYear], Characteristics
FROM DogCS
WHERE DogID = 1

the output is as expected
DogID BirthDate BirthYear Characteristics
1 1997-06-30 NULL 1997-06-3062Metacam, Phenylpropanolamine, Rehab Forte

Regards,
Balaji

]]>MishraTue, 27 Apr 2010 04:12:33 GMThttp://www.sqlmag.com/article/project-plan-dbadmin-sql-server-2008-r2-79/sql-server/efficient-data-management-in-sql-server-2008-part-2#commentsAnchorhttp://www.sqlmag.com/article/net-framework2/dragged-kicking-and-screaming-to-entity-framework#commentsAnchorFri, 12 Mar 2010 03:07:48 GMT
Hi Don. It’s reassuring to know there are others out there who are wary of moving to Microsoft’s latest vogue technology. From my experience there is no substitute for straight ado.net calls to stored procedures - these can be tweaked, bug fixed and optimised without the need to recompile your code.
Regards
Gavin]]>vilhelmsFri, 12 Mar 2010 03:07:48 GMThttp://www.sqlmag.com/article/net-framework2/dragged-kicking-and-screaming-to-entity-framework#commentsAnchorhttp://www.sqlmag.com/article/net-framework2/dragged-kicking-and-screaming-to-entity-framework#commentsAnchorFri, 12 Mar 2010 02:09:15 GMT
Don, Really good article. Will definitely help people wondering whether to take the EF plunge. Regarding the future of LINQ to SQL, it isnt dead. There are a number of enhancements in .NET 4 and i found a post that alludes to its future (http://www.linqdev.com/PublicPortal/publicportal/blog.aspx?EntryID=36) . It is anecdotal of course, in the absence of any formal statement from the product group (and the post from the ado.net team a long time ago raised more controversy than anything else (http://blogs.msdn.com/adonet/archive/2008/10/29/update-on-linq-to-sql-and-linq-to-entities-roadmap.aspx) but I think LINQ to SQL will continue to be the option for folk who dont need database independence or any of the other heavy lifting that EF does.
cheers,
benjy]]>santosh.benjaminFri, 12 Mar 2010 02:09:15 GMThttp://www.sqlmag.com/article/net-framework2/dragged-kicking-and-screaming-to-entity-framework#commentsAnchor