If case you did not know, Telerik released LINQ to M a few weeks ago, enabling you to use a LINQ style interface with M values of data. Mehfuz and I have written blog posts where you can see how to use the basics. 

There have been tremendous amounts of downloads and we have gotten tons of feedback. (Thanks, keep it coming!) One thing that stood out is that when you are building M values a lot of time you will have a named instance of your M code like this:

 1: //People is the named
"M" instance
 2: People{
 3:  {Id=1,Name="Stephen
Forte",Age=37},
 4:  {Id=2,Name="Mehfuz Hossain",Age=29},
 5:  {Id=3,Name="Vassil
Terziev",Age=31},
 6:  {Id=4,Name="Nadia Terziev",Age=27},
 7:  {Id=5,Name="Chris
Sells",Age=37},
 8:  {Id=6,Name="Todd Anglin",Age=27},
 9:  {Id=7,Name="Joel
Semeniuk",Age=37},
 10:  {Id=8,Name="Richard Campbell",Age=42},
 11:  {Id=9,Name="Kathleen
Gurbisz",Age=31}
 12:  }"; 

 

In the first version of LINQ to M, you get a runtime error saying that LINQ to M cannot parse “People”. The most current refresh of LINQ to M fixes this problem and you can run your LINQ queries against M values that have a named instance. You can get the refresh here. Enjoy!


About the Author

Steve Forte

 sits on the board of several start-ups including Triton Works. Stephen is also the Microsoft Regional Director for the NY Metro region and speaks regularly at industry conferences around the world. He has written several books on application and database development including Programming SQL Server 2008 (MS Press).

Comments

Comments are disabled in preview mode.