I fixed in my copy by changing "SharpAssembly " to "MonoDevelop.SharpAssembly.Assembly.SharpAssembly " in the afflicted files. Obviously this shouldn't happen because they're using MonoDevelop.SharpAssembly.Assembly already and referencing the correct assembly dll. But it's a workaround for now.