Problems encountered during commissioning of C ＃ project

1.  Use EF As data Library connection tool , During debugging, you will encounter such as Model PK Error and other prompt information , This is usually because the database table structure changes but is not updated in the project Model As a result of , This situation is generally Update once model Or delete the table and add it .

But I don't know the reason for the following problem , If you have encountered the same problem or know how to solve it, leave a message to guide you .

2. When the project is released You may encounter that you can't put some dll Load into the release file , perhaps bin Some of the following dll What can't be found , In this case Generally put bin and obj Folder Click not included in the project Pictured .

3. Use EF As a database connection tool , The database connection information is recorded in Model Of App.config in , If you want to use it directly in the project xxEntities.TableNmae Or Linq & Lambda perform SQL when , Need in the project config Configure the same database connection information in the file .

4. The assembly manifest definition found does not match the assembly reference

When a project references a new Nuget Package or upgrade Nuget Package version , After the release, we usually have no problem locally , because Web.config It has been updated with , But because the server is generally Web.config The file will not be overwritten , Pay attention to runtime Reference package version under , Otherwise, it is easy to cause the conflict that the assembly manifest definition does not match the assembly reference

 

 

~~~~~~~ It will be updated continuously in the future