This way you'll need to run the project converter quite rarely when the assembly name changes through major version changes to eg. If you want to make things even easier at new devexpress updates and do not want to run each time project converter to update the version number in the references exclude from you references ', Version=10.2.6.0, Culture=neutral, PublicKeyToken=b88d1754d700e49a' so instead of: This solution works perfect with Hudson build integration server and svn. This when a new version of devexpress is out you need just to update those DLLs instead of installing every time a new devexpress version and this way you can also revert to a previous version in case of a blocker bug or even run different devexpress ver on the same machine. In addition to the devexpress dlls add also App_Licenses.dll to that folder and reference it in all projects that use devexpress assemblies. NET products, describes the details of the installation process, and provides. If you have questions, feel free to call us at +1 (818) 844-3383 between 7:30AM and 4:30PM PST or email us at. If you're starting a new project, give DevExpress a try - download our free 30-day trial version. Best solution and hassle free with build servers is to have a shared folder in the source control where you keep the devexpress assemblies or different folders if you use different devexpress versions in different projects and reference those assemblies in the projects. This section provides information on the requirements for installing DevExpress. To see our best work in action, check out the online demos for our ASP.NET, MVC or HTML5 product lines.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |