Problem with AsyncParallelTask and navigation properties

In the process of upgrading to DF2010 6.0.3.1:
I'm having an issue with AsynchParallelTask which is performing a few queries to preload a bunch of tables which are used for navigation properties.  For some reason one of the navigation properties remains "detached" even though the data is there.

In this instance:
      var queryCity = Manager.Cities
                                    .Include(City.PathFor(c => c.County.State.Country));
      var queryLanguage = Manager.Languages.Where(l => l.Enabled);

      int i = 0;
      var task = AsyncParallelTask.Create()
        .AddAsyncQuery(++i, n => queryCity, r => { })
        .AddAsyncQuery(++i, n => queryLanguage, r => { });
      task.Execute(...);

Stepping into the "..." section of code in the Execute(), and inspecting "Manager.States.First()", I see "{Language: 0} - Detached" for the Language navigation property.
If I inspect "Manager.Languages.First()", I see "{Language: 1} - Unchanged", so I know the data is there since the first states should really be linked to Language 1.

If I change the first query to:
      var queryCity = Manager.Cities
                                    .Include(City.PathFor(c => c.County.State.Country))
                                    .Include(City.PathFor(c => c.County.State.Language));
and rerun it.
This time, when I inspect "Manager.States.First()", I see "{Language: 1} - Unchanged" for the navigation property.

I'm going to leave the query in the second case for now, but I'm worried that some other navigation properties may not be linking up correctly during a complex asynch parallel query.

Thanks!


Edited by mikewishart - 30-Jun-2010 at 6:24pm

Hi Ting,

No luck.

      var queryCity = Manager.Cities
                                    .Include(City.PathFor(c => c.County.State.Country))
                                    .Include(City.PathFor(c => c.County.State));
      var queryLanguage = Manager.Languages.Where(l => l.Enabled);

States still do not get linked up to the languages.

The original symptom that caused me to go look for this: When the application starts up it looks at the local configuration, determines what state the user lives in and determines the initial default language.  The language was being set to an empty string.  Looking at this the State and Language were disconnected even though both records were in the entity graph.


Edited by mikewishart - 02-Jul-2010 at 10:09am

Apparently this was caused by some sort of corruption in the edmx file when converting from VS2009 to VS2010.

Definitely a few gotchas, I tried to do it by hand originally.
After discovering this problem, I went back and started a new application, created new edmx files for our databases and referenced the old edmx files to try in fill in the gaps. Remembering where all the customizations were done on a large model (for example, a column's concurrency strategy set to something other than "none") is the tough part.  The pluralization isn't quite as nice as it was before either. After that was done, it was just a matter of unloading the model project, copying the edmx files in place and reloading the project and regenerating the devforce code.  I hope we don't have to go through that again anytime soon.