A previous development guide http://www.cnblogs.com/RainbowInTheSky/p/5496777.html
Some people often appear in the deployment of DLL compatibility problems (in fact, can see the small butterfly jinghong article, butterfly God has already stepped on the pit http://www.cnblogs.com/xiaodiejinghong/tag/mono/)
Stress testing with Webbench is recommended after site deployment
1.microsoft.web.infrastructure.dll do not upload, mono has been implemented (MS DLL has API dependency problem), mono DLL can be installed after the installation of the directory inside to find, reference:/http Www.cnblogs.com/xiaodiejinghong/archive/2013/05/23/3092181.html
2.system.componentmodel.dataannotations.dll, this DLL is an indicator of the component model, many ORM are useful, it is necessary to add references and upload ( note version )
3.system.drawing.dll, this DLL does not have to upload, but the use of a few points (GDI + believe that when the installation of mono is installed), you can generate a verification code in the use of fonts, But many font Linux systems are not with themselves (they do not have as many resources as Windows),
Results in the invocation of the font did not find the reference error, the solution is also simple, as far as possible to use the Linux font (no alternative), the problem of all programming languages are the same, belonging to the system environment problems.
DLL references to projects are important, and irrelevant DLL recommendations are removed (too many references to useless DLLs, load or initialize will be slow), and the project's functional consistency is maintained. (if there are any DLLs that are problematic, list them in the tired.) )
C # Development Guide for Linux (cont.)