mgr.DefaultManager.SaveChangesAsync(ObCol, AddressOf UserSaved, Nothing)

What I discovered is that wherever there are two signatures that are the same AFTER REMOVING OPTIONAL PARAMETERS, the VB compiler disallows BOTH.

Deborah Kurata filled me in on the background

This is from the C# spec:

"If two candidates are judged to be equally good, preference goes to a candidate that does not have optional parameters for which arguments were omitted in the call. This is a consequence of a general preference in overload resolution for candidates that have fewer parameters."

http://msdn.microsoft.com/en-us/library/dd264739%28VS.100%29.aspx - http://msdn.microsoft.com/en-us/library/dd264739(VS.100).aspx

This is from the VB documentation:

"A procedure with an http://msdn.microsoft.com/en-us/library/09yx51zh.aspx -
http://msdn.microsoft.com/en-us/library/e18yd02w.aspx - http://msdn.microsoft.com/en-us/library/e18yd02w.aspx

So C# resolves it and VB won't.
 

Thanks, Deborah!

Deborah Kurata

http://www.insteptech.com/ - Instep Technologies, Inc

Blog: http://msmvps.com/blogs/DeborahK - http://msmvps.com/blogs/DeborahK

Co-Chair: East Bay.NET user group

Microsoft MVP

I have a workaround for VB developers. You must create a C# class library project (if you don’t have one already) and add the following class to it:

using System;

using System.Collections;

namespace IdeaBlade.EntityModel {

  public static class EntityManagerExtensions {

    public static EntitySaveOperation SaveChangedItemsAsync(

      this EntityManager manager,

      IEnumerable entities,

      SaveOptions saveOptions = null,

      Action<EntitySaveOperation> userCallback = null,

      object userState = null) {

        return manager.SaveChangesAsync(entities, saveOptions, userCallback, userState);

    }

  }

}

You may then write:

mgr.SaveChangedItemsAsync(changeList)