Problems Occurred When Asp.net used the DevExpress control to publish it to the server

When developing Asp.net, it is inevitable that third-party controls will be used. On the Development machine, we install related packages and run normally. After the release, major and minor problems will occur. In fact, these problems are easy to solve, to ensure the security and high performance of servers, we should not turn servers into a development platform.

Devexpress, a third-party component, is no exception. We only need to add reference to the corresponding control class library, and ensure that the bin directory must be included in the release at the time of release, copy the file in the following directory:

D: \ Program Files \ devexpress 2009.2 \ Components \ sources \ devexpress. dll (under the installation directory)

Here, aspxgridview is used as an example to briefly introduce:

Devexpress. Data. v9.2.dll

Devexpress. utils. v9.2.dll

Devexpress. Web. v9.2.dll

Note: All the above three class library web application projects will be added to the public

Devexpress. Web. aspxeditors. v9.2.dll

Note: standard controls (such as buttons, labels, etc ......)

Devexpress. Web. aspxgridview. v9.2.dll

Note: aspxgridview

Devexpress. Web. aspxgridview. v9.2.export. dll

Note: An export control (Word, Excel) used with aspxgridvew)

Devexpress. Web. aspxthemes. v9.2.dll

Note: After the aspxgridview style is released, it is found that all the styles are missing, that is, this reference is missing.

 

In this way, you only need to add the necessary content, but the server load is not limited, the website load will also be optimized to ensure performance