Let’s take a look at how to develop the WeChat public platform through Bee.WeiXin. Regarding the general introduction of WeChat public platform, I will not go into details here. Just look for it in the garden. This article mainly introduces Bee.WeXin, and the code has been published to beeweixin.codeplex.com/.

BeeWeiXin is a development framework developed for Tencent’s WeChat public platform. This project is developed based on Bee OPOA Platform.

Contains the following functions:

1. WeChat reply model based on call tree. The call tree supports multi-level (with context) responses, and can respond in three ways: text, graphics, and custom. Among them, you can customize the three methods (text, graphics, music) provided by the WeChat public platform API.

2. Provides the function of synchronizing the WeChat following user list.

3. Provides menu management function.

4. Provides image and text management functions.

5. Natively integrate all functions on Bee OPOA Platform, mainly Permission management.

About Debugging, it is recommended to use the tools provided by garden friends WeChat public account to develop and release debugging tools

Preview

Configuration item description

Configuration items are all configured in [appSettings] in web.config.

[WeiXinToken] is the public platform API token;

[Debug] is Indicates whether it is currently in debugging mode. The difference between debugging mode and non-debugging mode is whether the initiated call is verified.

[WeiXinUserName] and [WeiXinPassword] are required for [Resynchronize All Users] in the menu [WeChat Follow Users]. Log in the simulated web page to the WeChat public platform, and then obtain the user list information. If it is not needed, you can ignore it or hide this menu.

[WeiXinAppId] and [WeiXinAppSec] are required in the menu [WeChat Menu Management], which can manage the menu of WeChat public accounts. Of course, this tool [WeChat Public Account Development and Debugging Tool Release] also has this function, which is more convenient. If it is not needed, you can ignore it or hide this menu.

[WeiXinController] is the default system response Controller. Please refer to the code for specific logic.

Response in call chain mode

The call chain is based on context. There is an option in the configuration item [Whether to enter the call chain]. If so, this response will be added to the call chain. to form context. For example, [Menu 1] needs to enter the call chain, otherwise the sub-items under this item will not respond.

First look at the following pictures:

From the preview picture, you can intuitively understand that the call chain can provide three types of responses: text, graphics, and customization.

Text is a general text response. For example, [Menu 1] has been configured in the Bee.WeiXinDemo project to respond with text, and the node value is V1001_M1_1.

回復(fù)1，test1
回復(fù)2，test2
回復(fù)3，test3

The reply is as follows:

#The image and text are the image and text information provided in the WeChat public platform API, configured in the call chain Just enter the specified article numbers in order [this number is the ID in WeChat article management] (separated by commas).

For example, test2 under [Menu 1] is in graphic and text format. To enter test2, you need to trigger menu 1 first, and then trigger test2. As shown below:

Customization is integrated into the Bee OPOA Platform frameworkMVC . Therefore, the configuration is also implemented through Controller, Action.

For example, test3 under [Menu 1] is a custom method. To enter test3, you need to trigger menu 1 first, and then trigger test3. As shown below:

I don’t know if you understand it? It is recommended that you download the source code and debug it to deepen your understanding. It is best to take a look at the code when you have time to help improve the project, haha.

[Menu 1] only has key values ??[1], [2], and [3]. How should the user respond if he inputs something else? At this time, you only need to configure the key value [*] as a response to other configuration items.

理解調(diào)用鏈上下文

在這種基于調(diào)用鏈的應(yīng)答中， 上下文是必要的。 怎么理解呢？舉例說明吧：我要查詢某個產(chǎn)品的某個國家的最近3個月的銷售情況。 由于微信平臺的特性， 我們不可能像其他應(yīng)用給用戶以直觀的查詢。

我們只有采用引導(dǎo)式的方式去引導(dǎo)用戶得到她想要的結(jié)果。 設(shè)計的菜單如預(yù)覽圖中【多級菜單】項所示。具體的配置項如下圖：

當(dāng)用戶點擊菜單按鈕觸發(fā)了【V1001_M1_2】的事件， 系統(tǒng)響應(yīng)提示文本【上圖的1】； 用戶根據(jù)提示， 選擇產(chǎn)品， 輸入1， 系統(tǒng)提示輸入國家【上圖的2】。 由于國家太多， 不太可能配置所有國家的選項， 所有采用了一個通配符的方案【上圖的3】， 并采用自定義的方式應(yīng)答。? 代碼如下：

public WeiXinTextResult CheckCountry()
        {            string content = ViewData.TryGetValue<string>("content", string.Empty);            // 驗證輸入的國家是否合法
            bool validFlag = content.IndexOf("CN") >= 0;            if (validFlag)
            {                return WeiXinText("1 最近3個月銷售統(tǒng)計\r\n2 最近6個月銷售統(tǒng)計");
            }            else
            {                // 由于調(diào)用鏈有上下文， 用戶輸入錯誤， 需要將當(dāng)前應(yīng)答取消。Current.MessageStack.Pop();                Current.MessageStack.Pop();                return WeiXinText("國家不合法，請重新輸入國家。");
            }
        }

由以上代碼可以知道上下文可以通過Current.MessageStack獲取。

用戶輸入正確的國家代碼, 則引導(dǎo)用戶做下一個選擇.

自定義MVC響應(yīng)

這個基本上跟Bee OPOA Platform的方式一模一樣。 如【菜單1】下的【Other】項的響應(yīng)就是采用該方式的。代碼如下：

public ActionResult Other()
        {            return View();
        }

View代碼如下：

<%@ Page Language="C#" AutoEventWireup="false" Inherits="Bee.Web.BeePageView" %>

<%@ Import Namespace="Bee.Web" %>
<%@ Import Namespace="Bee" %>
<%@ Import Namespace="System.Collections.Generic" %>
<xml>
 <ToUserName><![CDATA[<%=ViewData["FromUserName"] %>]]></ToUserName>
 <FromUserName><![CDATA[<%=ViewData["ToUserName"] %>]]></FromUserName>
 <CreateTime><%=Bee.WeiXin.DateTimeUtil.GetWeixinDateTime(DateTime.Now) %></CreateTime>
 <MsgType><![CDATA[text]]></MsgType>
 <Content>回復(fù)1 聯(lián)系方式 
 回復(fù)2 在線咨詢</Content>
</xml>

框架基類 Bee.WeiXin.Controller.WeiXinControllerBase提供了微信公眾平臺API所對應(yīng)的三種響應(yīng)的ActionResult, 具體請查看源碼.

【相關(guān)推薦】

1. 微信公眾號平臺源碼下載

2.?微智創(chuàng)T+微信機器人源碼

The above is the detailed content of Tutorial on the use of Bee.WeiXin WeChat framework. For more information, please follow other related articles on the PHP Chinese website!