Resolution process:

1: Because all referenced DLLs are not copied locally, all referenced DLLs have been checked to ensure that they are included in the input directory. The operation fails and the error content is the same
2: if the reason for x86 or x64 editing is not specified, x86 and x64 versions are generated respectively. The operation fails and the error content is the same
3: after installing the devaxpress control on the test computer, it runs normally.

Solution:

The reason is that the DLL is not copied completely. Open your VS project. There is a DevExpress Assembly Deployment Tool menu in the “Tools” of the menu bar. With this tool, you can export the DEV-related dlls used in the current project.

There is a special note. If you use the icons in Dev, please put DevExpress.Images.v{version number}.dll in your project.

Similar Posts:

• [How to Solve] SQLite database error: no such column
• How to Solve MSB8020 The build tools for v141 (Platform Toolset = ‘v141‘) cannot be found. To build using the
• Using react native elements in RN project to report an error: unrecognized font family ‘material icons’
• docker: Error response from daemon: Conflict. The container name “/xx” is already in use
• Microsoft report viewer 2012 cannot load related DLL
• Vs generation fails without error [How to Solve]
• Error:Configuration with name ‘default’ not found.
• The following table: unable to import javax. Servlet. HttpServletRequest
• [Solved] Error in uploading app icon when IOS app is released (image can’t contain alpha channels or transparencies)
• Anaconda “unable to locate program input point OpenSSL_ sk_ new_ Reserve is used in dynamic link library anaconda3 / library / bin / libssl-1_ On 1-x64.dll & qu