[Serialization] C # communication (Serial Port and network) Framework Design and Implementation-0. Preface,

[Serialization] C # communication (Serial Port and network) Framework Design and Implementation-0. Preface,

Contents

 

Preface

I have just joined the work and used VB and VC to develop software. With the rise of C #, I heard that C ++ is used. The company decided to use C # for software development in the future #, he started his career by buying C # programming introductory books for five yuan in the book market. Developing C/S and B/S structures is essential, and involves the Remoting, WebService, thread, asynchronous, and other cloud-based technologies. So far, I have not dared to say that I am proficient, but I am also skilled. I have studied the source code of the Framework, and I dare not say that I understand it all, but it is of great help to improve the technology.

In the traditional industry, I really feel the importance of introducing Internet thinking methods, and realize value-added services based on traditional industry products and user groups. Independently designs and develops remote E-service systems, clients, servers, Web management systems, and mobile APP (Android) programs. The prototype of the entire system is basically complete, and the leadership is also bright. It is a good thing to admire. As an ideal and purposeful programmer, we can only promote the company's development and achieve personal development. At that time, there was no concept of "Internet +". There was a difference in understanding between functional departments, and the project was slow and in a half-dead state. It is also reasonable to be slow to respond to new things in the style of doing things that does not show rabbits.

Think about the work you have made over the years. It is worth thinking about for those who think that developing software is an art. For a long time, only the communication (Serial Port and network) platform (SuperIO) can share with you, forming a product for you to perform secondary development.

In that year, I went to the interview with a framework interface and a brief introduction. After I was hired, when talking about salary, the department leaders said the "software" was very simple. It is understandable to reduce the salary. However, as a group of engineers, developers, designers, architects, and other people, I am most disgusted to hear someone say: this is very simple; this is easy to implement; this can be done in a short time ...... And so on. As a lightweight communication framework, SuperIO can improve reuse and reduce workload, which is valuable.

Speaking of frameworks, there are many frameworks on the Internet for our use. The communication framework, Message Queue framework, distributed task framework, and Web development framework are free of charge. Therefore, we should thank the Internet for its more diverse, open, and efficient technology.

For Engineers, I admire and envy those who make wheels. However, most people are using the wheel to stand on the shoulders of giants and pay more attention to the implemented business. I am not a developer, And I just formed a general software framework based on the company's business.

What is a good framework? You have no idea. From the developer's point of view, after N years, there will be motivation for modification and room for expansion. From the perspective of secondary developers (applications, it indeed improves development efficiency and reduces costs. From the perspective of user applications, the operation is indeed stable. Different subjects have different concerns.

After years of improvement and iteration, SuperIO indeed supported many devices and protocols of the company, and played an important role in data collection and interaction of integrated projects. It improves reuse and development efficiency, and reduces time and labor costs. There are also many users who are using it for free. Some people have reported that SuperIO is a bit like configuration software. To be honest, it is far worse than the configuration software, but the core communication is similar.

The core idea of SuperIO is to make the unchanged part stable, and make the changed part (display, data processing and storage, service, etc.) flexible. Similarly, the same framework can be completed in other languages such as Java, Python, and QT, more reflected in the ideological aspect.

I plan to write a serialized article to introduce the design and implementation of SuperIO, and point out where improvements are needed. It is hoped that communication can be improved together.

 

 

The Directory of the serialization article plan is as follows: chapter 1 communication framework introducing essential application scenarios of communication solving practical problems framework introduction framework application characteristics Framework Design Features plug-in application framework development environment third-party components summary chapter 2 Overall framework design Host Program Design communication Mechanism Design hierarchical model object summary chapter 1 Device Driver Design (Interface) device interface design Virtual Device Interface Design Protocol Driver Design command cache design data persistence design data interaction design communication status design timing task design operation Priority design authorization design Event Response design context menu design IO channel monitoring design Device Manager summary chapter 1 serial port and network I/O design unified IO Interface I/O manager serial port I/O manager network I/O manager summary chapter 2 Communication Controller Design controller serial port controller network controller summary chapter 2 Overall Controller design assembly parts interface function Event Response Data Transfer summary chapter 1 design of external interfaces plug-in interface graphical display interface data export interface service component interface summary chapter 2 plug-in engine design framework contract-interface implementation interface plug-in prototype-abstract class reflection mechanism dynamic loading plug-in summary chapter 9th Host Program detailed design configuration file design Loading Device Driver loading interface view loading data export loading service component DockPanel application detection operation authorization design in Chinese and English global exception monitoring overview chapter 1 debugger design debugging interface debugging command line debugging summary chapter 2 reasons for switching between Chinese and English versions without built-in resource files custom configuration file language Management Summary chapter 2 License design concept code implementation summary chapter 2 secondary development and application construction main program device-driven development graphical display development data export development service component development summary chapter 2 Configuration Tool application parameter configuration design driver mounting design summary chapter 1 OPC server and client development and design OPC server design OPC client design summary

 

 

Author: Wei Xiaozhi

QQ: 504547114

. NET Development Technology Alliance: 54256083

Document Download: http://pan.baidu.com/s/1pJ7lZWf