using weirdness

   Hi

I'm helping a team of newbie devs evaluate DevForce and have run into some very weird stuff!

The main problem I have is that the using statements in the ViewModel class need to be exactly right.

I have the following code:

using System.Collections.ObjectModel;
using IdeaBlade.EntityModel;

namespace XXX.DevForce.SL
{
    public class MainPageViewModel
    {
        private ObservableCollection<Customer> Customers { get; set; }
        private void Loaded()
        {
            Customers = new ObservableCollection<Customer>();
            var mgr = new DevForceDbEntities();
            var query = mgr.Customers;
            query.ExecuteAsync(op => op.Results.ForEach(Customers.Add));
        }
    }
}

Now the above doesn't compile - I get an ambiguous reference on op.Results.

The above code was typed without the using statements, then (using ReSharper) the using statements were inserted. (That is, I inserted the using statements that ReSharper suggested. This normally works fine.)

But something is wrong - I have to manually correct the using statements to read as follows:

using System.Collections.ObjectModel;
using IdeaBlade.Core;
using IdeaBlade.EntityModel;

Given that we're ReSharper fans, this is of concern to us.

So, what is causing this? I really don't understand - but it's a big problem for us. It's taken me quite some time chasing down this problem to identify the exact cause.

On another matter (and I don't know whether it's related to DevForce or not) I have tried to implement an IValueConverter class in my Silverlight project. However, when I refrence it in the XAML (in the UserControl.Resources) I get errors in the Cider designer:

Error 1 The type 'SL:BoolToVisibilityConverter' was not found. Verify that you are not missing an assembly reference and that all referenced assemblies have been built. C:\Projects\Visual Studio Projects\XXXDevForce1\XXX.DevForce.SL\MainPage.xaml 6 10 XXX.DevForce.SL

I have tried the exact same code in another non-DevForce Silverlight 4 project and the IValueConverter class works fine. 

I have found that if I put the IValueConverter into a separate Silverlight class library and reference it from the main Silverlight project I can get around the error.

Anyway, any help with these issues would be much appreciated.

Best regards,

Craig

(Auckland, New Zealand)