Microsoft Project files have different formats depending on versions. Some of
different versionsnumber others of different information and again formats.

A list of Microsoft Project formats must be created. And then discuss pro and
cons of the different formats.

I for my part would not integrate import/export to foreign file formats from the
ground up.

Rationale here is that

1) a new PM tool has to be evaluated first by the potential user base and as
such, they will decide whether it will fit their personal likings and requirements
2) if a user decides that he would rather do his job using OOPM than the other
tool, there is still the transition time between the old tool and the new tool
until that the new tool has proven itself worthy and stable enough for continued
work with that new tool
3) in case that the new tool, in that case OOPM is stable and fulfils the needs
of the user base, they have only a few projects left that they still can manage
using the old solution, in a way, the old solution can slowly die out and there
is definitely no need to import old projects into the new solution any more

and most important

4) as soon as Microsoft sees that there is a tool capable of replacing their own
tool, they will change the file format so that the new tool must once more go
and reverse engineer the new file format, regardless of whether they have a
"standardised" xml based solution at hand

5) writing parsers for the xml based solution presented by Microsoft is way
beyond our man power

 

Reset assignee on issues not touched by assignee in more than 1000 days.

obsolete