This project is read-only.

Upgrade Process - 4 to 5

Jun 11, 2013 at 4:12 PM
Edited Jun 17, 2013 at 4:42 PM
Hey Chris,

I finally have time and the necessity to upgrade an existing project to version 5+. I have a fresh installation of Visual Studio (2012) and nhydrate

My project has an older module wrapped around nhdal and one wrapped around efdal. I know that the bulk of my work will be converting the nhdal code to efdal.

However, the real question begins how do I upgrade my wsgen file to the new file format. I cannot seem to find the process in any discussions/release notes or the user guide. Obviously, visual studio will not open the wsgen file in anything but XML and if I rename the file to *.nhydrate opening it corrupts the file.

Any guidance you might be able to provide will be most appreciated.




After some digging I found if I create an empty model and right click in the field I can click utilities and import legacy.

I now get the following message:

"An error occurred while importing the legacy modelRoot"

Any suggestions?


Jun 27, 2013 at 5:06 PM
Codetools must be on vacation, he deserves it! Anyone else have any thoughts about how to get this darn model upgraded?

Jul 3, 2013 at 1:03 AM
Please send your model to this is odd. I need to look at it.
Jul 12, 2013 at 11:43 PM
I appreciate you taking a look at the model Chris thank you.

I have more questions I am currently seeking answers to, and will post here and update as I come across answers. If you have any input into any of them feel free :)
  1. Maintaining the version history, after getting the upgraded model back from you the version it wants to install is the current version of my database is version Should I just increase the model version to, and because this is the case it has obviously lost the changes since the last install, what will it try to install in the database and is there anyway to maintain the version history maintained in the older system table?
  2. Still on the database installer, I keep the db installer in source control and I notice the newly generated one has a substantially different folder structure. Should I just do a complete branch of my source control when I ramp the model version to I would obviously prefer to maintain the same trunk, but am concerned only because most of the old files (including the generated update scripts - will appear to foundation server as deleted.
Thanks in advance,

Jul 30, 2013 at 11:35 PM
Looking at the daunting task ahead of me to move to the 5.X modeler, I will have to wait until I get the older project transitioned from NHDAL to EFDAL. I fear that maintaining the models separately will be horrifying.

Can I install the old 4 line in Visual Studio 2012? How much of a chore would it be to make these compatible?

Here is the process for the eventual transition (when I get the older project moved to EFDAL).
  1. Upgrade the model to the new modeler.
  2. If there are verification errors fix these and generate/publish using the old 4.X generator and retry (1).
  3. When there are no verification errors on the upgraded model increase the model version number and generate.
  4. Verify the non-generated code files in the EFDAL have had their code retained, should be right?
  5. Fix any resulting errors in the calling code(s), there shouldn't be any right?
  6. Publish application with new modeler generated EFDAL.
  7. Proceed happily to continue producing new modules under the new modeler enjoying the model management features tooo.
Please provide thoughts and input if you have any.

Hopefully, I get the NHDAL dependant module updated this year.