It would appear that LINQ to SQL is running on a dead end track.

At PDC the announcement was made that no more investments in LINQ to SQL are made and the Entity Framework will absorb any features that LINQ to SQL has and that are worth preserving.

The following message from Tim Mallalieu says it all:

Is LINQ to SQL Dead?

We will continue make some investments in LINQ to SQL based on customer feedback. This post was about making our intentions for future innovation clear and to call out the fact that as of .NET 4.0, LINQ to Entities will be the recommended data access solution for LINQ to relational scenarios. As mentioned, we have been working on this decision for the last few months. When we made the decision, we felt that it was important to immediately to let the community know. We knew that being open about this would result in a lot of feedback from the community, but it was important to be transparent about what we are doing as early as possible.  We want to get this information out to developers so that you know where we’re headed and can factor that in when you’re deciding how to build future applications on .NET.  We also want to get your feedback on the key experiences in LINQ to SQL that we need to add in to LINQ to Entities in order to enable the same simple scenarios that brought you to use LINQ to SQL in the first place.

Live Mesh has gone from Tech Preview to official beta status. This also means it has gone world wide!

"Worldwide availability. We’ve removed the limits on what countries are able to sign up to use Live Mesh. We previously had limitations in place so that we could complete our testing with various language and locale settings, and now that work is indeed complete (with the caveat of course that for now the mobile client, as mentioned above, is not actually available worldwide)."

Yesterday I watched Don Gillet's PDC session on building a Mesh Application. It looks very easy.

My main concern with all this data in the cloud is securing my data. I'm thinking I may need to implement some sort of EncryptedDataEntry class which derives from DataEntry. I'll think about it some more...

In the past I looked at the OpenID standard in relation to Cardspace and AOL. Now Microsoft has committed to making Windows Live ID (previously known as Microsoft Passport) support the OpenID initiative.

"Beginning today, Windows Live ID is publicly committing to support the OpenID digital identity framework with the announcement of the public availability of a Community Technology Preview (CTP) of the Windows Live ID OpenID Provider."

The Live Services page does not mention Cardspace in relation to OpenID, but it stands to reason that as an OpenID provider Microsoft will somehow offer Cardspace support as well, just like www.myopenid.com.

Windows Azure is the name Microsoft has given to the cloud based platform. If you're not at PDC (like me) then go here for more information: http://www.microsoft.com/azure/services.mspx.

"The Azure™ Services Platform (Azure) is an internet-scale cloud services platform hosted in Microsoft data centers, which provides an operating system and a set of developer services that can be used individually or together. Azure’s flexible and interoperable platform can be used to build new applications to run from the cloud or enhance existing applications with cloud-based capabilities. Its open architecture gives developers the choice to build web applications, applications running on connected devices, PCs, servers, or hybrid solutions offering the best of online and on-premises."

Looks like my personal point of interest, Live Mesh, is part of this platform:

"Live Services includes Mesh technologies for synchronizing user’s data and extending web applications across multiple devices."

After discovering that the LINQ to SQL Designer will only support tables from a single data source I set out to manually implement a cross database query using two data contexts.

The result is the following query which joins orders in the OrderDB to products in the VideoGameStoreDB.

LINQ to SQL is unable to resolve this query, even though both databases sit on the same server. The compiler will however not warn you not to do this, instead a runtime exception with message 'The query contains references to items defined on a different data context.' occurs.

In a scenario like this the only solution appears to be to write a stored procedure which can perform the cross database query and use that stored procedure from a data context.

The LINQ to SQL Designer supports just one connection, which makes sense since a LINQ DataContext is scoped to one connection. The designer does offer to change the connection string for you, but I guess making cross database queries is not possible using the designer.

The following message is what you get when dragging a table from a second data source onto the design surface.

I just discovered that the LINQ to SQL Designer does not support User Defined Types.

The following message appears when I try and add a table from my database to my design surface. The Customer table in question has a UDT named 'Point' to specify the GPS location of the business.

Daylight savings for Europe started today. The United States does not switch to daylight savings until the first Sunday in November (this year: Nov. 2nd 2008). Between now and then the time difference between the States and Europe is one hour less.

At PDC this week Microsoft is announcing a new logo for .NET.

Looks very refreshing!

With LINQ to SQL you can choose to use an external mapping file, allowing you to map SQL statements to CLR objects (also referred to as POCO, Plain Old CLR Objects). Doing so means you do not need to adorn your classes with attributes.
Here's a little sample of how to do this.

public class Supplier

{

    public int ID { get; set; }

    public string Name { get; set; }

}

public List<Supplier> GetSupplier( string name )

{

    SqlConnection conn = new SqlConnection( cConnectionString );

    XmlMappingSource xms = XmlMappingSource.FromUrl( @"mapping.xml" );

    var db = new DataContext( conn, xms );

    Table<Supplier> Suppliers = db.GetTable<Supplier>();

    var query = from s in Suppliers

                where s.Name == name

                select s;

    return query.ToList();

}

The XML can be as simple as:

<?xml version="1.0" encoding="utf-8"?>

<Database Name="VideoGameStoreDB"

          xmlns="http://schemas.microsoft.com/linqtosql/mapping/2007">

  <Table Name="dbo.Supplier" Member="Supplier">

    <Type Name="Supplier">

      <Column Name="SupplierID" Member="ID" />

      <Column Name="SupplierName" Member="Name"  />

    </Type>

  </Table>

</Database>

You can use SQLMetal (a command line tool included with Visual Studio) to generate a mapping file.

The SDN Conference 2008 was a great success, thanks to all the speakers and attendees for making it so!

Beth Massi has a great write up on the day after the conference, the traditional Holland Tour: http://blogs.msdn.com/bethmassi/archive/2008/10/14/holland-tour.aspx.

Time to start working on SDN Conference 2009

Microsoft has put up a page to inform us about the next version of Visual Studio,  it is called Visual Studio Team System 2010.

Part of the new deal is a change in licensing, the fun part is: the licensing change takes effect on October 1st 2008!!!

Those of you who subscribe to MSDN and will now have access to both the Developer and DBPro edition of VSTS:

Better Together – Visual Studio Team System Development Edition and Database Edition
In recognition of the increased need to integrate more of the lifecycle members together, we will provide a unified Development and Database product in Visual Studio Team System 2010. Beginning October 1, 2008 Development Edition and Database Edition MSDN subscribers will have access to both products.

I just answered an email asking for a referral to a good hosting place, thought I'd blog about my experience with my hosting provider.

I've been running my blog and website with DiscountASP.NET for the last 3 years and never had an incident. They offer ASP.NET 3.5 hosting and usually offer options to test beta versions of ASP.NET or SQL Server as well, which is something I like. They're not the cheapest, but in my opinion, worth the money.

Click the banner to go to their site.

In the spirit of transparency: The link contains a referral code which will generate a kickback for me

The Maine Developer Network is helping out the MSDN Roadshow. Thanks to Shawn we're able to have the MSDN Roadshow come as far north as Augusta, ME. On October 3rd the Developer Evangelists for the New England region: Chris, Bob and Jim will be up (or down) in Augusta to present the latest and greatest .NET technologies. A full day of FREE training, open to everyone!

Sign up here: http://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032387795&culture=en-US

Topics are:

• Understanding the ADO.NET Entity Framework
• Discovering Dynamic Data
• Exploring Internet Explorer 8
• RoboLunch
• UI, UX, U Confused?
• A RESTed Development
• Befriending Unit Testing

Location:

Riverview Psychiatric Center
250 Arsenal Drive
Sebago Room Augusta Maine 04332-0011
United States

There will be give aways and ofcourse plenty of fun people to meet!

Here is a good reason to always keep improving:

Registration for the SDN Conference 2008 is open. Visit: www.sdc.nl. 

According to Matt Winkle some performance enhancements have been made to the Workflow designer in Visual Studio 2008 SP1. Strangely enough no mention of these improvements is made in the release notes. I wonder if they made it in.

Matt Winkle: "In .NET 3.5 SP1, there are no features introduced, but there have been a number of internal improvements made, including some substantial perf gains in the WF designer (for certain scenarios)."

Windows Workflow scheduling services manage how workflow instances are scheduled by the workflow runtime engine. Whether they are handled in an asynchronous manner through the DefaultWorkflowSchedulerService, or in a manual, synchronous manner through the ManualWorkflowSchedulerService, these services are an important part of your workflow solution.

The application I'm working on right now uses ManualWorkflowScheduler, so I needed to figure out the exact differences between the two scheduler, luckily MSDN actually offers pretty clear documentation:

Default Workflow Scheduler Service

DefaultWorkflowSchedulerService is used by the workflow runtime engine by default. It creates and manages the threads that run workflow instances in an asynchronous manner on the workflow runtime engine. Workflows that are waiting to run are stored in the internal queue of the DefaultWorkflowSchedulerService . When the DefaultWorkflowSchedulerService wants to start a workflow, a thread is acquired from the .NET Framework thread pool and used to run the workflow. The MaxSimultaneousWorkflows property determines how many simultaneous threads the scheduler service will allow at one time. If the limit is four, for example, the DefaultWorkflowSchedulerService will acquire up to four threads from the .NET Framework thread pool to execute the workflows. If four workflows are already running, additional work items (workflows) are placed in the queue and eventually executed as threads become available. The following figure shows how the DefaultWorkflowSchedulerService executes workflows in an asynchronous manner.

You can set the maximum number of workflow instances that can be active at any one time by passing a parameter to the DefaultWorkflowSchedulerService constructor or by using an application configuration file. Task 1: Configure Runtime Services Using Code shows how to configure the DefaultWorkflowSchedulerService class by using the constructor. Task 2: Configure Runtime Services using App.Config shows the same configuration of the DefaultWorkflowSchedulerService but uses an application configuration file.

Manual Workflow Scheduler Service

The ManualWorkflowSchedulerService provides a threading service that enables the host application that creates a workflow instance to donate the Thread on which the workflow instance is run. Using this threading service, host applications can run a workflow instance on a single Thread (that is, in synchronous mode). This mode blocks the execution of the host application until the workflow instance becomes idle. Subsequently, the workflow instance can only be executed by using the RunWorkflow method of this service.

Alternatively, the workflow can be run on a thread created by a .NET timer by setting the useActiveTimers constructor parameter to true. When this timer expires, the workflow is executed on the timer's thread, rather than the host application's thread. This timer is implemented as a DelayActivity activity.

ManualWorkflowSchedulerService controls the number of threads spawned in an ASP.NET process by reusing the thread that made the ASP.NET Web request to run the workflow instance. This ensures that at any time, the number of active threads in the workflow runtime equals the number of active Web requests in the ASP.NET process.

ManualWorkflowSchedulerService does not automatically run a workflow instance that is in the queue. The host must call RunWorkflow to run a specified workflow.

The workflow designer in VS2008 can sometimes be a little sluggish. I ran across a post on the forum which offers the following advice:

Commonly reported issues

1. Time taken to open a workflow document is long.

2. Opening Activity bind dialog is slow.

Reasons for slow down

The Workflow designer relies on parsing the source code in the current project to provide updated design information in workflow design surface, rules dialog intellisense etc. This is mainly to enable scenarios where picking up changes from the source even before the project has been rebuilt.

Tips to make designer perform better

1. Move all types used in workflows to a different project than where the workflows live.

Move interfaces, event types, custom activities, helper classes to a different project than in which the workflow resides. E.g. in the solution from a customer, there were about 10 project, with 10 workflows each and 10 associated event types. These types are all reparsed to update to build the design time type information every time the user changes workflows in the project. Moving these to a different assembly e.g  just one project with all the types needed for the 10 workflow projects will help improve performance.

2. Reduce the number of workflows in a project.

Each workflow is a type ( directly in c#/vb, and indirectly in xoml case) that needs a design time type to be built by parsing, so if there are 10 workfows in a project, opening any workflow in the project for the first time means parsing all the other workflows as well. Classifying these workflows based on their function and grouping them in 2-3 workflows per project improved performance drastically.

3. Re-Factor large state machine workflows into smaller workflows

One example we found from a customer had 780 states and 1000 activity binds in the same workflow, leading to a InitializeComponent() of about 16000 lines. Factoring this state machine into smaller reusable workflows will making designer performance much better, and reduce a lot of redundant states.

4. Don’t do long running work in activity constructors

Activity constructors are called during design time also, so doing things like connecting to a database etc should never be done in constructors, this can make the designer take too long to open workflow documents using these activities.

Visual Studio 2008 SP1 and .NET 3.5 SP1 offer an extensive list of enhancements, but also of bug fixes, here are the links in case (like me) your looking for a specific fix:

http://support.microsoft.com/kb/950263/ - List of changes and fixed issues in Visual Studio 2008 Service Pack 1

http://support.microsoft.com/kb/951845/ - List of changes and fixed issues in Visual Studio 2008 Service Pack 1 for Team Editions 

http://support.microsoft.com/kb/950264/ - List of changes and fixed issues in Visual Studio 2008 Service Pack 1 for Express Editions

http://support.microsoft.com/kb/951847/ - List of changes and fixed issues in Visual Studio 2008 Service Pack 1 for the .NET Framework 3.5