Hi

Althougth I post this question last year in private thread, I had to post it again and asked for much help. I felt so headache on upgrading the our 100+ solutions from V2.6 to V3.1.

I read much materials about upgrading llblgnepro. All of them need much manually work. I need a tool to do upgrade all 100+ solutions at one time. It **automatically **modify all SD.dlls from V2.6 into V3.1 and also modify the setting information of web.config or app.config.

In primary, Otis suggested that: ---------------Suggestion-------------------------------------------------------------------------------------- You can use any tool which can search/replace the dlls in a text file on disk. VS.NET can do find/replace in csproj files and your app's .config file.

replace: SD.LLBLGen.Pro.LinqSupportClasses.NET35, Version=2.6.0.0 with SD.LLBLGen.Pro.LinqSupportClasses.NET35, Version=3.1.0.0

replace: SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=2.6.0.0 with: SD.LLBLGen.Pro.ORMSupportClasses.NET20, Version=3.1.0.0

replace: SD.LLBLGen.Pro.DQE.SqlServer.NET20, Version=2.6.0.0 with: SD.LLBLGen.Pro.DQE.SqlServer.NET20, Version=3.1.0.0

See for list of tools: http://www.thefreecountry.com/programming/searchandreplace.shtml

There are many more of these tools, I haven't checked the windows resource kit and I'm sure powershell can help too.

be sure to work with a copy of your own source / projects so you can revert back to the v2.6 ones.

We don't use an update tool because it's really just find/replace in the csproj files and the config file, we don't need to update license strings in licenses.licx, like devexpress does.

We actually don't use that tool anymore from then as well, as it ruins subversion's copies in .svn folders. Be aware of that to not include those into your search/replace. If you do, you'll get checksum errors when commiting the changes back into subversion. the devexpress conversion tool doesn't prevent for this as well.

Hope this helps.

I think this suggestion is very good but it still refer to much manully work. I trust llblgenpro team can develop a upgrade tool as "ProjectConverter". Please see : http://community.devexpress.com/blogs/aspnet/archive/2007/09/10/how-to-easily-convert-your-project-to-a-new-devexpress-release.aspx.

We use the devexpress from V9.3.2 to V10.2.6 in two years. We upgrade it in every 3 or 4 months. The devexpress "ProjectConverter" help us too much. We didn't need to do upgrade every solution and can upgrade all solutions on SVN server side at one time.

Please understand that I look like to be a stick like a limpet, I am indeed very headache on upgrading problem.

Best regards Ricky

I'll have to say it again I'm afraid The only things that have to upgraded are the references to runtime libs. That's it. We don't use licenses.licx, so these files don't need change, something devexpress requires. That's why they offer an upgrade tool.

Walaa wrote:

I'll have to say it again I'm afraid The only things that have to upgraded are the references to runtime libs. That's it. We don't use licenses.licx, so these files don't need change, something devexpress requires. That's why they offer an upgrade tool.

I have 100+ solutions. As you mentioned, I need to open every solution. Then I manullay modify the references into the runtime libs , and modify the setting information web.config too. That is terrible thing for me.

I just use the projectConvert.exe to import the **only one entrance folder **of 100+ solutions in svn server, then simply click upgrade button. It automatically modify all devexpress references into new versions and setting inofrmation web.config. That is enough for us.

I just only hope you can provide a simple tool as projecConvert.exe.

Best regards Ricky

The upgrade tool of devexpress always ruins our applications, as it modifies .svn folders as well (it simply does a global file search/replace) -> changes in both versions -> svn problems. (so we do that by hand. It also ruins the licenses.licx file every time)

Anyway, you also have to re-generate all code to v3 if you upgrade to v3, and we changed the file format so you've to upgrade the .lgp to .llblgenproj.

I'm not sure what your 100+ projects are, but if they're referencing your generated code, then as I said before, a global search/replace with a tool which does that is the easiest. In another thread I gave you a link to a series of tools (but there are others) which do search/replace on disk in files.

Anyway, IMHO you can't update all your projects automatically: you have to make sure they work with the new version. Perhaps your 100+ applications are really 1 application which is modified for 100+ customers, not sure, but upgrading to a different version requires simple file changes in the csproj files, but that's not all, you have to make sure your application works with the new version as well, e.g. perhaps we changed something and you have to deal with the breaking changes.