10 Comments

• Just wanted to pop in and thank you for my two favorite presentations of the event.  "Building N-Tier with LINQ"(even though I have decided to not use LINQ for my applications for now) and "Leverage Silverlight 2 Animation Features".  You're a great speaker and I really took a lot away from the courses, thanks.
  

• Thanks Jarrette! I appreciate it and am glad you got something out of the sessions. :-)
  

• Definitely the best session I attended at DevConnections. With all the new technology Microsoft is releasing we were feeling a little overwhelmed to what direction we wanted to focus on. Your session on Building N-Tier with LINQ really brought everything together. It was one of those Ah-ha moments for me!
  
  P.S.
  Any chance you have a VB.NET version of your architecture?
  

• Thanks Eric. I really appreciate you taking the time to comment on the session and I'm glad to hear you found it useful. I don't currently have a VB.NET version unfortunately. One of these days I need to convert it.
  

• Hi Dan, The NTier Apps with LINQ session was awesome. You are a great speaker. Thanks for making the code to use with all the different data layers with LINQ, Sprocs and everything. That makes is really useful to compare and contrast.
  Thanks !
  

• Thanks Pallavi...I appreciate it. Glad you were able to attend. That's a fun talk to give since there are so many options people can choose from.
  

• Building N-Tier ASP.NET Applications with LINQ Code was one of the best session I took. I create all my applications in layers also. I notice you recommend to name the namespaces for Context and Entity. I understand Model is used for the Entity Namespace but what if you want to separate the Model layer in another project. Can that get confusing ?
  

• Hector,
  
  Thanks for attending the session. I'm glad you found it useful. As far as the separation you mention, I generally prefer to have my model classes in a separate project. But, from a productivity point of view changing the entity and data namespaces in the designer and having both data and model classes in the same project certainly works. It's something you'll have to think through to see if it works well for your situation though. It's possible to map to other classes as well that are external: http://weblogs.asp.net/dwahlin/archive/2008/08/18/using-linq-to-sql-xml-mapping-files-step-by-step.aspx
  

• Hey Dan,
  
  I'm finally getting around to downloading all the code samples from dev connections. I really enjoyed your session, thanks!
  
  -Gio
  

• Hi Gio,
  
  Thanks for coming to the session. Glad you enjoyed it. :-)