<?xml version="1.0" encoding="UTF-8"?>
<speaker>
  <biography>Jim Wooley is a frequent speaker, member of the INETA Speaker Bureau, Microsoft MVP, and author of &quot;LINQ in Action&quot;. He is always striving to stay at  the forefront of technology and enjoys the thrill of a new challenge. He has been  active evangelizing LINQ since it's announcement in 2005. In addition, he attempts to pass on the insights he has gained by being active in the community, including organizing the Atlanta Code Camp, leading the Microsoft MS Pros and Atlanta VB Study Group and serving as INETA Membership Manager for the Georgia region. Jim has actively helped to guide Microsoft through Software Design Reviews with product teams and is an active Microsoft Data Programmer Insider and Visual Basic Insider. In addition to speaking at numerous user groups and code camps in 7 states, Jim has presented at product launch events, MSDN conferences, and TechEd.</biography>
  <company></company>
  <company-website>http://www.LinqInAction.net</company-website>
  <id type="integer">2831</id>
  <linkedin-url>http://www.linkedin.com/pub/jim-wooley/1/490/12a</linkedin-url>
  <location>Atlanta, GA</location>
  <name>Jim Wooley</name>
  <personal-website>http://www.ThinqLinq.com</personal-website>
  <title></title>
  <twitter-username nil="true"></twitter-username>
  <average-rating type="decimal">4.73</average-rating>
  <avatar-url>/avatars/2831/thumb/JimHeadShot.jpg</avatar-url>
  <talks type="array">
    <talk>
      <created-at type="datetime">2009-08-28T22:54:12+00:00</created-at>
      <event-id type="integer">171</event-id>
      <id type="integer">1396</id>
      <info>With 3.5 SP1, Microsoft released two competing technologies to provide Object Relationship Mapping strategies over data - LINQ to SQL and the Entity Framework. Microsoft has indicated that, although they will continue to support both technologies, future enhancement efforts will be directed toward the Entity Framework. As a result, people who built applications over LINQ to SQL are faced with the challenge of moving them over to the Entity Framework to take advantage of future enhancements. In this session, we will explore the similarity and differences between the two technologies to help identify times when you should and should not migrate existing code bases. We'll focus on the common pitfalls that developers need to be aware of when moving between the technologies. We'll also look at architectual options you can make to make migration less painful. Additionally, we'll look at some of the functionality scheduled to be included in future versions of the Entity Framework which may influence decisions on making migrations. </info>
      <location nil="true"></location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url>http://www.thinqlinq.com/Downloads/EFMigration.zip</slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url>http://www.jaxcodecamp.com/Agenda.aspx/Sessions</talk-url>
      <title>Migrating from LINQ to SQL to the Entity Framework</title>
      <updated-at type="datetime">2009-08-28T22:54:12+00:00</updated-at>
      <when type="datetime">2009-08-29T15:30:00+00:00</when>
      <average-rating nil="true"></average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-08-14T15:15:58+00:00</created-at>
      <event-id type="integer">87</event-id>
      <id type="integer">1325</id>
      <info>You've seen how to drag tables onto a designer and get an instant data tier. Many applications need to go beyond the basic implementation. In this interactive presentation you'll see some of the more advanced options LINQ to SQL provides to offer mapping alternatives, concurrency, use of stored procedures, inheritance, and stateless context management. In the end, you will leave with more tricks and tips to add to your LINQ toolbox. If you've chosen to use LINQ to SQL as your data access platform, this will be an opportunity to ask your real-life questions.</info>
      <location nil="true"></location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url>http://www.ThinqLinq.com/Files.aspx</slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url>http://www.devlink.net/Sessions/tabid/124/Default.aspx</talk-url>
      <title>LINQ to SQL Tricks and Tips</title>
      <updated-at type="datetime">2009-08-14T15:15:58+00:00</updated-at>
      <when type="datetime">2009-08-15T14:30:00+00:00</when>
      <average-rating nil="true"></average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-08-14T15:13:17+00:00</created-at>
      <event-id type="integer">87</event-id>
      <id type="integer">1324</id>
      <info>A number of technologies have been released in recent years which make building data driven applications easier. Starting with the declarative data models in LINQ and the Entity Framework, we are now able to build more dynamic applications quicker and easier than ever before. Building on top of LINQ, we now have the ability to present data dynamically through services (using ADO.Net Data Services) and web applications (using ASP.Net Dynamic Data). In both of these, we can consume our data models the way we need to rather than by needing constantly modify our external contracts (in terms of Stored Procedures or service contracts). The capabilities we have available to us are not limited to the base scaffolding, but allows for significant customization as necessary for our particular business needs. In addition, we can reuse our underlying models to enforce business requirements while retaining these dynamic capabilities. </info>
      <location nil="true"></location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url>http://www.thinqlinq.com/files.aspx</slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url>http://www.devlink.net/Sessions/InDepthSessions/tabid/200/Default.aspx</talk-url>
      <title>Building dynamic data driven applications</title>
      <updated-at type="datetime">2009-08-14T15:13:17+00:00</updated-at>
      <when type="datetime">2009-08-13T09:00:00+00:00</when>
      <average-rating type="decimal">4.1</average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-08-03T15:38:39+00:00</created-at>
      <event-id type="integer" nil="true"></event-id>
      <id type="integer">1295</id>
      <info>With 3.5 SP1, Microsoft released two competing technologies to provide Object Relationship Mapping strategies over data - LINQ to SQL and the Entity Framework. Microsoft has indicated that, although they will continue to support both technologies, future enhancement efforts will be directed toward the Entity Framework. As a result, people who built applications over LINQ to SQL are faced with the challenge of moving them over to the Entity Framework to take advantage of future enhancements. In this session, we will explore the similarity and differences between the two technologies to help identify times when you should and should not migrate existing code bases. We'll focus on the common pitfalls that developers need to be aware of when moving between the technologies. We'll also look at architectual options you can make to make migration less painful. Additionally, we'll look at some of the functionality scheduled to be included in future versions of the Entity Framework which may influence decisions on making migrations.</info>
      <location>1125 Sanctuary Pkwy, Suite 300, Alpharetta, GA</location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url>http://thinqlinq.com/files.aspx</slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url>http://www.Atlantamspros.com</talk-url>
      <title>Moving from LINQ to SQL to the Enitty Framework</title>
      <updated-at type="datetime">2009-08-03T15:38:39+00:00</updated-at>
      <when type="datetime">2009-08-03T18:30:00+00:00</when>
      <average-rating type="decimal">5.0</average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-06-27T06:30:09+00:00</created-at>
      <event-id type="integer">131</event-id>
      <id type="integer">1219</id>
      <info>LINQ brings us a paradigm shift in working with data from imperitive models to declarative set-based operations. With LINQ we can use the same syntax against many different sources. In this session we will dig under the surface of LINQ to show how the various parts, including Iterators, Duck Typing, IEnumerable, IQueryable, Lambda expressions, expressoin trees, and extension methods work, and how they fit together to allow us to use the same syntax against otherwise dis-similar data sources. By understanding how this works under the covers, you will have a better idea how to use LINQ better.
</info>
      <location></location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url>http://www.thinqlinq.com/Downloads/InsideLinq.zip</slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url></talk-url>
      <title>Inside LINQ</title>
      <updated-at type="datetime">2009-06-27T12:15:42+00:00</updated-at>
      <when type="datetime">2009-06-26T14:20:01+00:00</when>
      <average-rating type="decimal">4.85</average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-06-29T16:49:32+00:00</created-at>
      <event-id type="integer">128</event-id>
      <id type="integer">1234</id>
      <info>When the Entity Framework was released in 2008, Microsoft faced the challenge of two competing technologies (LINQ to SQL and LINQ to Entities) accomplishing essentially the same thing. As a strategic decision, Microsoft decided to direct it's attention moving forward to add enhancements to the Entity Framework. In this session, we will explore the changes needed to move an application from LINQ to SQL over to the Entity Framework. We will also explore some additional capabilities programs can leverage by using the Entity Framework that were not possible with LINQ to SQL.</info>
      <location nil="true"></location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url></slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url>http://vslive.com/2009/lasvegas/linq.aspx</talk-url>
      <title>Moving from LINQ to SQL to the Enitty Framework</title>
      <updated-at type="datetime">2009-06-29T16:49:32+00:00</updated-at>
      <when type="datetime">2009-06-09T22:20:01+00:00</when>
      <average-rating nil="true"></average-rating>
    </talk>
    <talk>
      <created-at type="datetime">2009-06-29T16:51:29+00:00</created-at>
      <event-id type="integer">128</event-id>
      <id type="integer">1235</id>
      <info>With the release of .NET 3.5 and the subsequent SP1, attention has focused upon the legitimacy of Object Relational Mapping systems. Regardless of whether you embrace LINQ to SQL, the Entity Framework, NHibernate, or any of the hundreds of other O/R Mappers, the question remains for the DBA: Is it time to consider alternatives to stored procedures? In this session, we'll introduce LINQ and discuss how programmers and DBA's can work together with these emerging technologies to build robust, performant and dynamic systems.</info>
      <location nil="true"></location>
      <series-id type="integer" nil="true"></series-id>
      <slides-url></slides-url>
      <slideshare-key nil="true"></slideshare-key>
      <talk-url>http://vslive.com/2009/lasvegas/linq.aspx</talk-url>
      <title>LINQ Kinq for the DBA Guy</title>
      <updated-at type="datetime">2009-06-29T16:51:29+00:00</updated-at>
      <when type="datetime">2009-06-09T15:30:01+00:00</when>
      <average-rating nil="true"></average-rating>
    </talk>
  </talks>
</speaker>
