VSTO Excel自动化德语环境报错：XlDirection命名空间歧义（BC30560）

Hey there, I’ve run into exactly this frustrating issue when working with VSTO Excel automation across different Office locales—let’s break down what’s happening and how to fix it.

What’s Causing the Problem? #

The BC30560: 'XlDirection' is ambiguous error (paired with the System.Reflection.TargetInvocationException) happens because:

• In non-English Office environments like German, your VSTO project might be referencing two separate namespaces that both define the XlDirection enum: Microsoft.Office.Interop.Excel (the core interop assembly) and Microsoft.Office.Tools.Excel (the VSTO-specific tools assembly).
• In English locales, the compiler might prioritize one namespace by default, but German Office installations can shift this priority or introduce duplicate references that trigger the ambiguity.
• The TargetInvocationException is just a wrapper—this is thrown because the underlying code can’t resolve the enum ambiguity during runtime reflection calls.

Step-by-Step Fixes #

1. Explicitly Qualify the Enum with Its Full Namespace

The quickest fix is to stop relying on implicit namespace imports and tell the compiler exactly which XlDirection you want to use. Instead of writing:

Range.End(XlDirection.xlDown)

Write:

Range.End(Microsoft.Office.Interop.Excel.XlDirection.xlDown)

This eliminates any ambiguity immediately.

2. Use a Namespace Alias (Cleaner for VB.NET)

If you don’t want to type the full namespace every time, set up an alias in your VB.NET project:

• Go to your project references, find Microsoft.Office.Interop.Excel, right-click > Properties.
• Set the Alias field to something like XLInterop.
• At the top of your code file, add:

  Imports XL = Microsoft.Office.Interop.Excel
  

• Now you can use the alias to reference the enum clearly:

  Range.End(XL.XlDirection.xlDown)
  

3. Clean Up Duplicate References

• Open your project’s References tab and check for:
  • Multiple versions of Microsoft.Office.Interop.Excel
  • Unnecessary references to Microsoft.Office.Tools.Excel (if you’re not using VSTO-specific controls)
• Remove any redundant references, then clean your project (Build > Clean Solution) and rebuild.

4. Clear Bin/Obj Folders

Sometimes old compiled files from the English locale linger and cause conflicts. Manually delete the bin and obj folders in your project directory, then rebuild from scratch.

Final Note #

Once you resolve the XlDirection ambiguity, the System.Reflection.TargetInvocationException will disappear automatically—it’s just a side effect of the underlying compilation error.

内容的提问来源于stack exchange，提问作者Raghu