Devexpress 10.1.6 source code re-compilation successful (dxperience 10.1.6 re-compilation) with all the resources to be used download address (favorites)

I wanted to write it on my own. I was touched when I saw such details written by this renxiong on the Internet ...., find such a good person, CTRL + V to get it, recent projects have been using the devexpress control, it is necessary to study it in depth :)

First post address: http://www.cnblogs.com/shaoming01/archive/2010/09/09/shaoming01.html

With the strength of the boss, I finally tried to download all the things required for devexpress compilation.

1. dxperience universal-10.1.6 installation package, which is over 190 MB

: Http://downloads.devexpress.com/63be3ab2-a882-4af8-bf95-6ee2ba8af6bb/64.237.51.130/DXperience/2010.1/6/DXperienceUniversal-10.1.6.exe

This is an official link and must be downloaded using thunder,

If it becomes invalid or cannot be connected, you can try to modify the hosts file,

Change downloads.devexpress.com to an IP address.

64.237.51.154, 64.237.51.155, 64.237.51.156, 64.237.51.157, etc. (this method is quite different)

If this is not the case, you can download it elsewhere by file name.

2. Source Code (the most important thing is that I have worked hard to find it .)

Http://rapidshare.com/files/416091676/DX2010.1.6.Sources.rar.html
Unzip the password: allcredits_jfx
Http://rapidshare.com/files/416119124/DXXAF2010.1.6.Sources.rar.html
Unzip the password: allcredits_jfx

I am engaged in winform. I can use it after downloading the first one. I have not used Dev for a long time. I don't know what the second package is.

We recommend that you use a download tool called jdownload, which is faster.

A lot of friends said that the download could not be done, so I had to work hard. It took me half a day to split the source code into several packages and upload them to csdn.

If the above link is hard to download, you can go to the links

Note that it takes some time to upload, so do not blame the downloading point.

3. Compile the script. I have been searching for the script for a long time on the Internet. I guess I can pass level 4 in this bad English. (I have read too many E Documents)

In the end, I used the compiling script of version 10.1.4 to compile the SDK. I guess the compiling package of version 10.1 should be generic. Guess.

: Http://files.cnblogs.com/shaoming01/Devexpress_10.1.4 license

The above are the materials to be prepared. If all the materials are ready, follow the steps below to proceed step by step.

How to Build form source code?

1. Install the trial (download from the official website) Note: Install all parts of the setup, even if you do not need it
2. Now extract the sources (provided by our good friends here, bless them) to{Install Folder}\ Components \ Sources folder
(By sources I mean all the folders starting with devexpress.{Something}
3. Extract the build scripts (all the *. bat, *. CMD and the patchinternalvisibleto stuff) to{Install Folder}\ Components \ Sources folder
4. Now open defines. BAT in some text editor like Notepad
5. Set the version of vs you are using first (in the vsver = vs2008 line)
6. Also, I like to set the configuration variableReleaseInsteadDebug
7. path Editing: the basic idea here is to verify that all paths mentioned in the file are valid for your system. eg. if you have windows 32bit, the programfiles32bit variable shocould point to c: \ Program Files
8. Check all paths and make sure they are valid for your system. I found a few differences on mine:

1. Set Sn = "% programfiles64bit % \ microsoft sdks \ windows \ v6.0a \ bin \ sn.exe"
2. Shocould be
3. Set Sn = "% programfiles64bit % \ microsoft sdks \ windows \ v7.0a \ bin \ sn.exe"

And in vs2010 Section

1. Set gacutil = "% programfiles32bit % \ microsoft sdks \ windows \ v7.0a \ bin \ netfx 4.0 tools \ x64 \ gacutil.exe"
2. Shocould be
3. Set gacutil = "% programfiles32bit % \ microsoft sdks \ windows \ v7.0a \ bin \ netfx 4.0 tools \ gacutil.exe"

9. The bottom of the file is divided into different sections for each version of vs. You only need to check the paths for the version of vs you have
10. If you have trouble finding the correct path for any variable, just search your C: drive for the file the path is referring.
11. Check your changes, save and close the file
12. Now open a command prompt and navigate to{Install Folder}\ Components \ Sources folder
13. Run clear. bat
14. Open the c: \ windows \ Assembly folder
15. If you find any assemblies starting with devexpress, remove them. If you have installed the IDE tools, there will be assemblies like devexpress. dxcore, devexpress. refactor, devexpress. coderush-doNotRemove them. I usually install the IDE tools after finishing with the components to avoid any confusion.
16. Open{Install Folder}\ Components \ sources \ devexpress. dll folder and delete any remaining files from it.
17. Ready to compile! In the Command Prompt window (the one used for running clear. BAT) Run buildall. CMD (and pray)
18. in the output, all yellow MSGs are warnings and can be ignored. the red ones are errors. you might get a few of these (3/4) If you have not installed ASP. net. other than that, there shoshould not be any errors.
If you get a lot of errors, something is probably wrong with the edits you made in the defines. bat. Stop the build, and recheck.
19. After successfully completing the build, run the Toolbox creator from the devexpress group in the Start Menu. Do not run toolboxcreator.exe directly.
20. In{Install Folder}\ Components \ Sources folder there will be a file called publickeytoken.txt, open it in a text editor and copy the key to the clipboard.
21. Run the projectconverter tool from the Start Menu, click the show advanced options check box, past the public key in the Custom Public Key box
22. Point the project folder to you solutions folder and convert all your projects.
23. Good to go!

The E text above is relatively simple. It doesn't mean anything to translate. it's just plain.

Although the steps seem to be many, the operations are relatively simple.

Anyway, I followed this and eventually succeeded. I believe you can do the same.

After the source program is re-compiled, all the demos may not be able to run. You need to generate a new script.

: Http://www.cnblogs.com/shaoming01/archive/2010/09/10/devexpress_ReBuild_ALL_DEMOS.html