Some winform third-party controls

AboutWinform third-party controls

These daysWinform, for the sake of appearance, for convenience,... I used some third-party controls for all the reasons I needed, and finally made myself tired, but I also learned something, or, more specifically, I would like to say, a lesson, don't hide your private words, just say it right, don't bother you if you don't care, just fart!

1.YourWinformProgramIf you need skin replacement, you should not use a third-party control that is too advanced. For example, if you use dotnetbar and want skin replacement, you will use the irisskin skin replacement control again. This problem arises, it's useless to change the skin of the dotnetbar control. Later I thought it was right. The dotnetbar control itself has a skin replacement function. It doesn't hold your irisskin control, but it's hard to look at it with the replacement of the dotnetbar, just a few dead faces. This is probably a so-called fish and a bear's paw! There is another question. The skin change control is not easy to use. I just want to do it myself. Google and Baidu check it. Mom, what the Chinese do is to use others' skin changes, I did not have a few to study this carefully (at least I checked the result). It would be too heavy to be "tailistic". I really don't know what it would be like if I didn't crack it!

2. for third-party controls, we should not only use well, but also put it in the most suitable place, but also carefully read the development documents of other people, thoroughly understand, then we will "Write down as God ". I used dotnetbar. I thought it was just a control set. After studying it, I knew it was a framework, just like there are devcomponents. dotnetbar. office2007form , This allows us to easily implement a form similar to office07, complacent!

3.For some third-party controls with source code, when time permits and energy permits, we have to open these controls layer by layer. Don't just take them here, we need to turn others into our own, so that we can grow slowly, or we will always be a software migrant worker! Like this one I usedRibbon controls, foreigners do a lot of work, but there are still some shortcomings in them. As for where the lack is, you guys are all eye-catching and don't have to go into details!

4.If the project requires time and permits it, you may wish to write custom controls by yourself. If you are not using the custom controls of others, you will have the strongest control over the controls used in the entire project, the controls of others may be very powerful, but the risk comes with them. You can ensure that your controls are100% cracking, and there are no bugs, there is no free lunch in the world, this is old saying, but it is absolutely rational!

Today, I wrote this article, and I wrote it later. Who told me this? Tomorrow, continue.Code, Continue to work hard, continue learning, continue... Continue to the new socialist life, haha!

original address: http://www.cnblogs.com/fangbaiyi/archive/2009/09/08/1562827.html