Shulou(Shulou.com)06/03 Report--

This article mainly introduces "how C# synchronizes Wechat user grouping information in the management system". In daily operation, it is believed that many people have doubts about how C# synchronizes Wechat user grouping information in the management system. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the question of "how to synchronize Wechat user grouping information in the management system". Next, please follow the editor to study!

1. User grouping and interface design in the management system

In view of the above Wechat grouping operations, we can design a module in Wechat's application management system to manage Wechat grouping data. In this module, you can create groups, modify groups, view groups and other basic operations. You can also synchronize Wechat grouping operations, synchronization operations, mainly adding new grouping information to Wechat. The modified grouping also implements the modification function in Wechat, which is not supported by Wechat at present, so don't worry about it. Finally, we can synchronize the modified data from the Wechat server here. In order to avoid submitting unsuccessful data to us during synchronization, we need to identify the modified record. This is my logical handling of the whole synchronization operation.

In the management system, the list management interface for Wechat grouping is designed as follows.

When creating a grouping, we only need to add a grouping name, and the interface design is simple, but we uniformly design the created ID as-1 as an unsynchronized new identity.

The interface for editing grouping information is shown below. When the grouping is edited and saved, the system will remember the modified grouping.

2. Display the operation code of grouping synchronization

In order to better realize the management of grouping synchronization, I encapsulate the operation code of the grouping in the method of a MVC controller. The page code can be synchronized through the call of Ajax. If the synchronization succeeds or fails, it will prompt the user to let us know the result.

When synchronizing, create a grouping of the newly added local content on the server; modify the name of the modified grouping on the server, and then synchronize the list processing. Before the synchronization operation, the list interface may be as follows: some record ID=-1, and some record the modification flag after modification.

The synchronization button operation of the user grouping is to call a script code, as shown below.

/ / bind the click event of the submit button function BindSyncDataEvent () {$("# btnSyncData") .click (function () {$.messager.submission) ("submit confirmation", "are you sure you want to synchronize the packet information with Wechat server?" , function (action) {if (action) {/ / submit data $("# loading") .show () $.ajax ({url:'/ Group/SyncGroup', type: 'post', dataType:' json' Success: function (data) {if (data.Success) {$("# grid") .datagrid ("reload") $.messager.alert ("prompt", "synchronization succeeded");} else {$.messager.alert ("prompt", "synchronization failed:" + data.ErrorMessage) }, data:''}); $("# loading"). FadeOut (500);})

The red part above is the controller method of MVC called through Jquery. The specific function code is shown below.

/ / synchronization server packet information / public ActionResult SyncGroup () {string accessToken = GetAccessToken (); CommonResult result = BLLFactory.Instance.SyncGroup (accessToken); return ToJsonContent (result);}

From the above, we didn't see much logic, so I encapsulated them further and put it into the business logic layer to deal with it. Let's take a look at its code logic, here in order to make all database operations faster and more complete, using transaction operations, I posted the relevant code to facilitate everyone to understand the logic.

/ / synchronization server packet information / public CommonResult SyncGroup (string accessToken) {CommonResult result = new CommonResult (); try {IUserApi api = new UserApi () Using (DbTransaction trans = baseDal.CreateTransaction ()) {/ / upload the unuploaded record of the local flag groupId =-1 to the server, and then update it locally string condition = string.Format ("GroupID ='- 1'"); List unSubmitList = base.Find (condition) Foreach (GroupInfo info in unSubmitList) {GroupJson groupJson = api.CreateGroup (accessToken, info.Name); if (groupJson! = null) {info.GroupID = groupJson.id BaseDal.Update (info, info.ID, trans);}} / / change condition = string.Format ("GroupID > = 0 and Modified = 1") on the server; List unModifyList = base.Find (condition) Foreach (GroupInfo info in unModifyList) {CommonResult modifyed = api.UpdateGroupName (accessToken, info.GroupID, info.Name); if (modifyed! = null & & modifyed.Success) {info.Modified = 0 / / reset flag baseDal.Update (info, info.ID, trans);}} / delete grouping with delete flag / / condition = string.Format ("GroupID > = 100 and Deleted=1") / / List unDeletedList = base.Find (condition); / / foreach (GroupInfo info in unDeletedList) / / {/ / CommonResult deleted = api.DeleteGroup (accessToken, info.GroupID, info.Name) / / if (deleted! = null & & deleted.Success) / / {/ / baseDal.Delete (info.ID, trans); / /} / /} List list = api.GetGroupList (accessToken) Foreach (GroupJson info in list) {UpdateGroup (info, trans);} try {trans.Commit (); result.Success = true } catch {trans.Rollback (); throw } catch (Exception ex) {result.ErrorMessage = ex.Message;} return result;}

During Jquery synchronization, in order to avoid waiting for too long and unable to judge whether the program is working properly, it is best to add a busy prompt operation, because we use Ajax calls, so we can uniformly set the busy and completion status of Ajax. The specific setting code is as follows.

/ / the settings for unifying the busy display of requests $.ajaxSetup ({beforeSend: function () {$("# loading") .show ();}, complete: function () {$("# loading") .hide ();}}) At this point, the study on "how C# synchronizes Wechat user grouping information in the management system" is over. I hope I can solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.