An encapsulated asp.net verification code class

The first reflection is whether these properties of the verification code can be set (that is, whether they are encapsulated into a class and then used by exposing public properties and methods, or whether the verification is implemented directly in the general handler) Code generation to output), the result is unfortunately the latter... The algorithm inside feels pretty good, at least for someone like me who barely understands algorithms, so I thought of encapsulating it. She then shamelessly incorporated it into her own class library ^^

First analyze the shortcomings in this code (what she thinks):
1. For procedural programming, if you want to modify the verification code Properties, such as modifying font size, background color and other details, you need to find the relevant code in the general processing program and modify it. However, this code is better. It separates the verification code string generation and image generation in different methods, making it easy to find the places to be modified.
2. If I want to apply this function to other places, such as a winform program, then this code cannot be reused in the form of a component (a dll), but can be copied, pasted and modified...
3. I didn’t find that the verification code was saved after it was generated (- -!)

Of course, the so-called shortcomings are relative, that is, if you have time to think about it and then slowly design a verification code class, you will definitely It can make a relatively good class, but if you are working on a project and the project is urgent, such code is actually more powerful. The so-called object-oriented design pattern code decoupling is just a cloud~~~

The next step is my modification of this code. First, determine what effect I want, that is, how I want to use it after encapsulating it. First of all, I hope that when using it, I only need to create a new verification code instance (if necessary, I can set various attributes of the verification code arbitrarily), and then I can call certain methods of this instance to use strings, streams, bitmap objects, and byte respectively. Obtain this verification code in the form of an array (note that this verification code class does not include the function of saving the verification code into the context. Personally, I feel that generating the verification code and saving the verification code into the context are two different functions. There is no need to add this function. Do it in the verification code class). In this case, the code becomes extremely simple in the general processing program. First, just create a verification code with new, then call the method to obtain the verification code in the form of a string, and then save it in the morning and afternoon. As for whether it exists in the Session or Cookie It comes as needed, and the verification code class does not care about these; then it calls another method to obtain the verification code in the form of a byte array, so that the image can be output through the context.Response.BinaryWrite() method, that is to say There are only three lines of code in the general processing program. The calling code is roughly as follows:

/// <summary> 
/// 获取验证码（一般处理程序入口函数） 
/// </summary> 
/// <param name="context">当前上下文</param> 
public void ProcessRequest(HttpContext context) 
{ 
// 创建验证码 
ValidateCode validateCode = new ValidateCode(); 
// 获取验证码（字符串），写入Session 
context.Session["SomeValidateCode"] = validateCode.GetString(); 
// 输出验证码（图片） 
context.Response.BinaryWrite(validateCode.GetByteArray()); 
}

PS: I remember that when I first started working, the code was poorly written (worse than now). I usually used it directly when I got a copy of the code. I never thought about whether to use it. The code should be modified or encapsulated. I was taught by my master at that time and I was very impressed. Personally, I feel that there is nothing wrong with using other people's code. First of all, others have used it to at least prove the usability of the code. In addition, my IQ is limited. Some things you want to break your own are not as good as others, but you must not blindly use other people's code. Just use it. It is best to make necessary modifications or encapsulation according to your actual situation, even if it is just a simple layer. Of course, again, if the project is urgent, it is obviously a waste of time. In short, don’t think about it, use it as soon as you get it, at least make sure the key code or the overall structure of the code is clear.

For more encapsulated asp.net verification code related articles, please pay attention to the PHP Chinese website!