Use VB to develop green software

In my opinion, the green software is installation-free, short, and lean software. Most of the currently shared software belongs to this type (or move closer to the green software ).

Even the large phoshop software also puts some registration items in a specialized registration file (reg file). to reinstall the operating system, you only need to import the reg file into the registry. In addition, for example, Kingsoft Software can be run without installation.

At present, most of the shared software is made using Delphi. Although its Pascal syntax is awkward, we still insist on using it. The best reason is that it is very convenient to make green software, basically everything is done for an EXE file.

Use VC for shared software. If it is based on API Development (non-MFC), it is always a bit tricky (currently the machine configuration is relatively high, and shared software is generally a small application program, unlike servers, which have high performance requirements, VC development also takes a long time ).

Although the development of MFC is relatively fast, there is also a running library problem. Make it a dynamic link. Users of Windows 9x series cannot use it. compile it into a static link, the Software size is expanded by more than 1 MB. It is better to use less bandwidth when the network bandwidth is not rich.

There are also many introductions in this regard when using VB for green software. However, a slightly complicated program also carries a lot of dowry: VB Runtime Library, OCX control, and so on, if databases (such as ADO and Dao) are used in the software, it is still unknown whether the software can be made of green software.

However, VB is easy to use and software development is faster. If the API technology is well mastered, most software can be well implemented. If VB is used for shared software, development is easy, and additional income can be increased. Why not?

But how can we solve the above problems? Based on my experience and the development of some green software, I would like to talk about my views. If anything is inappropriate, I would like to ask Fang Jia to make an axe.

First, the problem of running database can be solved in this way. At present, most users are on win2000 and XP platforms, while Microsoft has added the Runtime Library to the system directory for us on win2000 and later platforms. (In this regard, Delphi users are very dissatisfied and think this is unfair competition. VB runtime libraries and MFC runtime libraries are all integrated into the system, in this way, Delphi is far behind the software developed by VB and MFC at least in terms of the Software size. Therefore, this part of users do not need to consider the problem of running libraries. for users of 9x series, you can store the VB Runtime library on the Internet. If necessary, you can download the library directly from the Internet. If you don't mind the Software size, you can also release the Runtime Library with your software (directly put the Runtime Library in the same directory of the current software ).

At present, although Microsoft does not support VB, as long as the subsequent versions of Windows still integrate the VB Runtime library, it is still promising to develop shared software with VB (Microsoft has hundreds of megabytes.. NET platform can be integrated. What's more, what about the VB Runtime Library of the zone 1.25m? I am optimistic about this :)

2. If you use VB to develop shared software, we recommend that you only use the basic controls of VB. In addition, do not use database operation controls (or references) such as Dao and ADO. If you operate on data, I recommend that you define your own database format (which can be similar to the database format such as DBASE). This can be done if the data volume is not large (for example, less than 10 thousand records, currently, User Machines are relatively high-end and there is no need to consider too many performance problems. In this case, you only need to run the database to run the vbprogram. In a Win2000 or later system, you can directly run it.

Third, for the sake of appearance, the software interface can be mapped directly using the image control. I have always liked this method. For multi-language version, you can use to read the INI file method, you can also directly read VC compiled pure resource files (can refer to an article I wrote: VB Dynamic Load pure DLL resources (http://blog.csdn.net/yefanqiu/archive/2005/03/16/320640.aspx ).

Fourth, after software development, it is best to compress it with the EXE compression software. There are two advantages: one is that it adds an obstacle to being cracked, and the other is that the software size is greatly reduced, facilitate release.

Fifth, as for encryption, it is a matter of benevolence and wisdom. I don't have to talk about it here.

――――――――――――――――――――――――――――――――

Ye fan Password box. This is the new green software I developed with VB, that is, I can change the language or skin. I think it is no worse than the program developed by VC and Delphi.

: Http://www.sky-walker.com.cn/yefan/yfcodes.rar

If you are interested, you can give more comments. My mailbox: yefanqiu@yahoo.com.cn yefanqiu@sohu.com

――――――――――――――――――――――――――――――――