No, I said that CNX2 edits to a nef file would be represented when *viewing* the file in VNX2. I ssid nothing about those edits being honored when re-editing the file in VNX2. I don't use VNX2 as an editor. I don't even consider it an editor. I consider it a viewer and browser, and thats how I use it. I realize that VNX2 does have some limited abilty to make edits to a nef file, and will easily convert a nef file to other formats. But since I'm more than comfortable using CNX2 as my editor, I see no reason to muck up the works by trying to go back and forth between CNX2 and VNX2 with edits to a file, trying to force compatibility that clearly isn't there. I can't speak to the strategy of the development team regarding their intent as it relates to the inter-operability of VNX2 and CNX2, but I would imagine that the editing provisions of VNX2 were meant to serve those who did not want to make the investment in time, effort and capital to use CNX2 as their editor. Which I think is sound policy. Not everyone will want to take photo editing to the degree that some of us do. I can see where VNX2 would serve the needs of many nef shooters, and I think it's great that Nikon provides such a nice program to its customers at no cost.
As to the technical reasons why the two programs could or couldn't be more compatible with respect to honoring each others edits, you're asking the wrong guy. It's a good day for me if I can just get the program to do what I want it to do, without understanding how the moving parts work. There are others here who can speak to that much better than I. But I do know it's a complicated history with different development teams and corporate entitites involved over the years in the development of these two programs. I'm just happy that they work together as well as they do.