Numer ID artykułu: 830698 - Zobacz jakich produktów dotyczą zawarte w tym artykule porady.
This article has been archived. It is offered "as is" and will no longer be updated.
You receive a CustomAttribute attribute as a byte array from an assembly. When you try to emit the CustomAttribute attribute to a new assembly by using the overload AssemblyBuilder.SetCustomAttribute method (ConstructorInfo, Byte), the generated assembly may not contain the emitted attribute.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name -------------------------------------------------------------- 17-Oct-2003 02:59 1.1.4322.959 77,824 Corperfmonext.dll 17-Oct-2003 02:56 1.1.4322.959 311,296 Mscorjit.dll 17-Oct-2003 16:39 1.1.4322.959 2,093,056 Mscorlib.dll 17-Oct-2003 02:57 1.1.4322.959 2,498,560 Mscorsvr.dll 17-Oct-2003 02:58 1.1.4322.959 2,490,368 Mscorwks.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates