Upgrading IDE

[SeeCwriter]

I have NNDK version 2.4 RC2, with SNMP. I am eligible to upgrade to the latest release, but the latest
release (2.5) doesn't appear to come with SNMP. How do I upgrade with SNMP?

[rnixon]

Did you enter in all your key codes when you installed 2.5.2?

[SeeCwriter]

I got it. I screwed up.

After transfering my projects to the new version, can I now just delete the old nburn directory structure
to remove the old version? That appears to be the only way to remove old versions. I don't want to
screw up the registry or something.

[rnixon]

I rename my old directories with the version number (like they say in the release notes) and don't delete them. That way I can always go back. It doesn't interfere with the env. vars if you always have the same name for the active directory: c:\nburn. Never copy a project, you must always import through the eclipse import feature (you can do the whole project, or just the source files).

[tod]

Why do you have to copy projects at all because of a new NNDK? I realize you may be using NBEclipse but as long as your project directory isn't inside the nburn directory the projects should be fine.

[Ridgeglider]

A copy of the source-only into a similarly-named project in a new workspace would preserve the release and/or debug images built under a previous release of the tools. Depends what matters to you, how custom (non-system) libs are set up, etc.

[rnixon]

Yes, my point was what Ridgeglider said. By leaving the workspace in the \nburn install I have a 100% saved environment and project. Lets say I have one workspace separate from my tools. I then update the tools, rebuild my project, and something does not work. I would love to be able to go back and rebuild it exactly the same way as before.

Now you could say this should never happen, and if it does, its the tools fault. But that has never been the case for me. I've had two problems come up with my own code in this circumstance:
One was that I changed some code, but got interrupted and forgot to rebuild everything. When I did the import to the new install it did have to rebuild everything, and things didn't work right. I quickly found my error by going back to the old release.
Second, I had my own lib and modified the build config to add it. In the new release I got a bunch of errors. Confirming the earlier release worked quickly helped me figure out what the problem was.

In a perfect world none of this happens, but mine is far from perfect