Provides methods that modify how a specified native Microsoft Office Excel object passes locale ID (LCID) information to the Excel object model.
Assembly: Microsoft.Office.Tools.Common.v9.0 (in Microsoft.Office.Tools.Common.v9.0.dll)
'Declaration Public NotInheritable Class ExcelLocale1033Proxy 'Usage You do not need to declare an instance of a static class in order to access its members.
public static class ExcelLocale1033Proxy
In the current release of Visual Studio Tools for Office, the methods in the ExcelLocale1033Proxy class are obsolete.
In earlier releases of Visual Studio Tools for Office, there were some operations where native Excel objects did not work correctly while the ExcelLocale1033Attribute is true. This attribute controls whether the Visual Studio Tools for Office runtime wraps all native Excel objects in proxy objects that always behave as though the end user's locale is English (United States). The methods of the ExcelLocale1033Proxy class were intended to be used to work around these limitations, by getting an Excel object without the proxy, and wrapping the Excel object in its proxy again after the operation in which it was used. In the current release of Visual Studio Tools for Office, native Excel objects work as expected when the ExcelLocale1033Attribute is true, so these methods are now obsolete.
For more information about the affect of locale settings on Excel solutions, see Formatting Data in Excel with Various Regional Settings.
Because the Visual Studio Tools for Office runtime wraps all native Excel objects in a proxy object when the ExcelLocale1033Attribute is true, you might notice a slowdown in certain operations that involve native Excel objects. In these cases, you can improve the performance by using the Unwrap method to get the Excel object without the proxy, and then perform the operation using that object. If you do this, be aware that the object returned by Unwrap uses the locale ID of the current thread, not locale ID 1033.
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.