End, indicating a new start

The last check-in of the previous two days, after updating dnn c # To 5.6.2, the task of this version also completed his mission, the next DNN release will be based on C.

Review

After more than a year of maintenance, I am very tired and happy to learn and communicate with you. I tried to translate DNN into C # several years ago, but I finally gave up because I didn't have a good solution and a solution to maintenance and upgrade, it may take several months to convert to a version. However, after a few months, the official DNN version may have been updated several times, then, isn't my work finished before the beginning, and I cannot maintain consistency between the two versions. After receiving more solutions, I have been thinking about a problem,What is upgrade?Since the software upgrade is continuous, the Upgrade Code is certainly traceable, and the idea is gradually forming a solution for maintaining version upgrade. Of course, the first step is to perform a complete conversion. To tell the truth, this task tests people's willpower. There are too many files and too many code, in addition, vb.net has a "powerful" compiler, which leads to a variety of vb.net code writing methods. It is too worried when trying to solve one strange error after another. After a long time, I saw "build Successful" for the first time. The excitement is beyond words, and of course the resulting pain is even more complicated. After the compilation is successful, I can't wait to open the browser and prepare to appreciate my "masterpiece". It's so perfect. The overwhelming exception makes me unable to survive. After debugging and analysis again and again, an exception occurs until the installation interface appears, until the "installation completed" is displayed, until the homepage is opened for a long time, until you can log on and edit it, until "almost" is available. Successful! It is no less than the feeling of holding hands with your girlfriend for the first time. The following tasks are relatively easy to test, modify, and submit.

Now it's time to start upgrading. After I complete the entire conversion process, DNN has upgraded two versions as I expected, here, we need to publish the inventory weapons maintained in this article, a comparison tool. WinMerge is in the open-source camp, and BeyondCompare is in commercial software. By comparing the DNN official version files one by one, you can see which files have been modified in this upgrade, after you modify the code, copy the changed code to the corresponding location of the C # version and change it to the C # version. In this way, you can track and maintain the code, basically, each DNN upgrade takes 1-2 days to complete tracking to the C # version.

The following things are simple, and we can continue. During this period, he communicated with Shaun Walker and Scott Willhite and officially submitted the version to the Official Directory. Of course, I did not expect that DNN decided to start 6.0 development by C, I am very grateful to the DNN team for making such a wonderful decision. Although there may be nothing for everyone, it is of great significance to me!

Tips

How to convert? Here we mainly use SharpDevelop's conversion tool and the very easy-to-use Fuse fusion tool. After this article, I attached a relatively simple VS plug-in (For details, refer to the article) to facilitate code snippet conversion.

How to upgrade? Always use BeyondCompare for comparison and upgrade.

Step 1: Comparison;

Step 2: copy the code to the C # version;

Step 3: Convert the code to C # code.

 

Note

Although the dnn c # project may no longer be updated, I will continue to study DNN, research. net, research technology, either not, or do better.

Attachment

Converting.zip (based on converged fusion Service)

1. decompress the file to My Documents \ Visual Studio 2010 \ Addins; (if it is VS2008, put it in the VS2008 directory)

2. Open VS and select the code to be converted;

3. select option-Converting to convert vb.net code to c #.