Code Authoring Process
1, Dalwebservice folder, processing data acquisition interface
--The database access code is mainly under the Mrtmclass project, the mine introduction and the license Information WebService interface is the existing
Here to understand the relevant business field information can be.
2, the Mrs Folder, processing the Web backend data interface
--Add code sequentially in the model, IBLL, DAL, BLL four sections, model and IBLL in the contract suffix project
Here according to the front-end display needs, the field to be used to build model, and then make a query of the BLL interface and implementation.
Mine introduction and license information as long as the interface can be queried, do not have to make changes to submit.
3, GMS. Web.admin\areas\minemanage folder, processing data application and display
--Complete the action associated with the controller
--Complete the code for the view
Here's a look at some of the ways the backend provides data through action to the front end, under the MVC framework,
As well as the front end of the js,html and other effects.
Note:
--refer to the completed Mine Manager minemanageinfo module to encode.
--page Effect reference: http://221.235.182.4:8006/account: admin Password: wxgtj2015
After entering, select two-dimensional supervision, and then select the Yadong mine on the map, click to view mine information has page effect.
---IDE is VS2013---
1. Database
221.235.182.4:8082
User name: SA
Password: sykj3180759
2. Test the publishing server
Remote Desktop: 60.172.210.120:23389
User name: Administrator
Password: [email protected]
Release Port: 23396
3. The code is based on the third-party framework GMs
Description Address: http://www.cnblogs.com/guozili/p/3496265.html
4. Initial User name password
Land Bureau Account SGTJ
Password 111111
Mining Enterprise Account ksqy
Password 111111
-----------the procedure for adding a new project to the Mrs Feature module----------------------
1. Under the Gms.mrs folder under the Source code folder, add the Sub-module folder
2, in the Solution Explorer, to add the location of the module, right-click the new project, make the code directory just the directory, named according to the rules
3. Setting related references
--BLL References:
Gms. Core.cache
Gms. Framework.contract
Gms. Framework.dal
Gms. Framework.utility
Gms. Mrs.xx.Contract
Gms. Mrs.xx.DAL
--contract References:
EntityFramework
Gms. Framework.contract
Gms. Framework.utility
--dal References:
Databaselib
Gms. Core.config
Gms. Core.Log
Gms. Framework.contract
Gms. Framework.dal
Gms. Mrs.xx.Contract
Mrtmwebservice Service Reference, named Mrtmservice
4. Set the project's build path to: ". \.. \.. \.. \bin\ "
5. Add code files within each project and copy them from other modules to modify them.
6. Modify the Gms.web reference and code settings for the module.
--Quote contract,.
Adding related content in--controllerbase.cs and Servicecontext.cs
7. Modify the GMS.Web.Admin reference to the new module. The BLL, contract, Dal all have to be quoted
8,mrtmwebservice.asmx.cs inside Add code
9. Finally, add the Service Reference update service references. Mrtmwebservice Service Reference, named Mrtmservice
Note 1, reference inside no update on their own manually added
2, about the following question
The endpoint configuration portion of the contract "SERVICEREFERENCE1.XXXXXX" could not be loaded because multiple endpoint configurations for the contract were found. Please indicate the preferred endpoint configuration section by name
The reason is that "add external reference" is referenced more than once in the Web. config file
<system.serviceModel>
<bindings>
<basicHttpBinding>
<binding name= "Webservicesoap"/>
<binding name= "WebServiceSoap1"/>
</basicHttpBinding>
</bindings>
<client>
<endpoint address= "Http://10.29.68.32/WebService.asmx" binding= "BasicHttpBinding"
bindingconfiguration= "Webservicesoap" contract= "Servicereference.webservicesoap"
Name= "Webservicesoap"/>
<endpoint address= "Http://10.29.68.32/WebService.asmx" binding= "BasicHttpBinding"
bindingconfiguration= "WebServiceSoap1" contract= "Servicereference.webservicesoap"
Name= "WebServiceSoap1"/>
</client>
</system.serviceModel>
So delete a node can be (if the reference is WEBSERVICESOAP, delete the relevant node WebServiceSoap1, and Vice-)
You can also specify the bindingconfiguration name when the page is referenced:
such as: servicereference.webservicesoap web = new Webservicesoapclient ("Webservicesoap");
Transferred from: http://www.cnblogs.com/for917157ever/p/3195725.html
ASP. Add code inside the code flow (BLL contract DAL)