in
Forums
Blogs
Files
Devexpress.Com
Client Center
Support Center
DevExpress Channel

Support

Blogging about support in Developer Express.

The Update on "Upgrading Projects"

Now it's time to issue an update on my Upgrading Projects post.

The ProjectConverter tool has been significantly improved since version 6.1. Visually it remains the same (quite an ascetic design, in my opinion), but internally it now has a more sophisticated functionality.

The ProjectConverter modifies the following files of your project/solution:

  • Project files (~.csproj / ~.vbproj) - updates assembly references. Please note that the ProjectConverter currently supports only C# and VB.NET projects.
  • Resource files (~.resx) - updates assembly references in type declarations.
  • License files (~.licx) - clears references to DevExpress.~ assemblies.
  • Web Page files (~.aspx) - updates assembly references in Register tags.
  • web.config - updates assembly references.

These files contain the full version information about an assembly, i.e. they include the assembly minor version number. That is why you should convert your project after installing each minor (maintenance) update. Since DXperience v6.3, the setup suggests that you launch the ProjectConverter after completing the installation. To launch the ProjectConverter manually, please click the link in the Start\All Programs\Developer Express .NET [2005] v6.x\Tools menu.

The ProjectConverter updates only assembly references (user code remains unaltered), hence you can use it both for upgrading and downgrading. For example, if you have a project for DXperience v6.3.2, you can downgrade it, for example, to v6.2.5 by launching the ProjectConverter of the DXperience v6.2.5 installation. That is, the ProjectConverter of your DXperience version is suitable for all projects created with any DXperience suite version. For instance, please use the ProjectConverter to update Knowledge Base articles' sample projects. In this case, you don't really have to worry about which particular version of our controls was used in a given sample; simply process the project's folder with the ProjectConverter that you have installed.

By the way, ProjectConverter.exe accepts some command line parameters. The following switches are currently supported:
/r - recursively process subdirectories.
/s - auto-start the conversion.

Example:
ProjectConverter.exe C:\MyProjectPath /r /s

P.S. Thanks to blogging, I have a good chance to tell you: Merry Christmas! Dear guys and gals who wrote to Support during this year and whom I replied personally! I appreciate your business and your valuable feedback on our products. My warmest wishes for Merry Christmas and a Happy New Year to you and your families.

Published Dec 25 2006, 08:42 PM by Nick (Developer Express)

Comments

 

Miha Markic said:

Merry Christmas to you, too and thanks for all the help.
December 26, 2006 9:43 AM
 

DIMITRIS said:

Hello
Is anyone can help me?
I have the ASPxGrid and Editors ver 6.3.2.0
How i can get the field value ( not the field name) by clicking on the rows.
Bellow is the Row Click event code

Protected Sub ASPxGrid1_RowClick(ByVal source As Object, ByVal e As DevExpress.Web.ASPxGrid.CellClickEventArgs) Handles ASPxGrid1.RowClick


   End Sub

Thanks
December 28, 2006 1:41 PM
 

Nelson said:

Unfortunately it does not do datasources which also contain specific information. ie:

<BindableControlInfo Name="DateEdit" Type="DevExpress.XtraEditors.DateEdit" AssemblyName="DevExpress.XtraEditors3, Version=3.2.5.0, Culture=neutral, PublicKeyToken=79868b8147b5eae4" />

Also it appears to have missed some other things since my project keeps telling me it has references to other 3.2.5 stuff:

Error 6 The type 'DevExpress.XtraEditors.Container.EditorContainer' is defined in an assembly that is not referenced. You must add a reference to assembly 'DevExpress.XtraEditors3, Version=3.2.5.0, Culture=neutral, PublicKeyToken=79868b8147b5eae4'. c:\BFC_DEV\Funder\Funder\Forms\PropertyEdit.Designer.cs

I have 12 such errors that I must now figure out...

Some highlights of what is "mising": IXtraSerializable, INavigatableControl, IToolTipClient, IDataControllerVisualClient, ISupportLookAndFeel, IAppearanceOwner..

..on to check out the newsgroups...
January 12, 2007 2:48 PM
 

Nelson said:

Followup to my previous msg.. It appears that the coverter did not properly convert the reference to the assembly for the VGrid controls. The reference looks like its updated in the references (it says 6.3) but the file path was pointing to the older assembly.
January 12, 2007 4:54 PM
 

Ronald said:

Hello I've got a ASP.NET project made with visual studi 2003.
I have the ASPxGrid and Editor library 2.xx
I would like to convert my project to visual studio 2005 and to convert my controls to 6.3.2.
Can you tell me the better way to do it ?
Do I convert the ASPxGrid before converting the project for vs2005 ?

Thanks
January 24, 2007 3:12 PM
 

SC said:

Hi, I have a C# project built with Visual Studios 2003 and was thinking of upgrading to 2005 (or 2008). My controls were developed with devexpress v.6.1xx. What would be the best way to do this? Upgrade to v6.3xx first and then to v7.xx?

Regards

January 28, 2008 1:09 PM
 

Chamila said:

I tried to upgrade 7.2.2 based web project to 7.3.7. Unfortunately i could not run the project after that. Assembly reference appears to increased to 7.2.2 to 7.3.7, but there must be a problem with public key tokens. Please Advise me to upgrade properly

February 25, 2008 12:15 AM
 

Marsen Karsen said:

Blue Imazing

July 30, 2008 2:25 PM
 

Jason said:

Can you please add this command line information to the documentation?

October 20, 2008 5:24 PM
 

Alan (Developer Express) said:

Jason,

Thank you for your comments. This information will be added soon to the corresponding topic in our documentation: devexpress.com/.../Content.aspx

October 21, 2008 3:54 AM

Leave a Comment

(required)  
(optional)
(required)  
Verification code: Required
   
Add
Copyright © 1998-2008 Developer Express Inc.
ALL RIGHTS RESERVED