[T3hC13h]

I was messing about with the OS project file structure and it hit me, we already have at LEAST 2 other major project/solution files from VS and #Dev. Why don't we just use one of those as our primary project file and at least support conversion for the other.

This is something we can wait on until the core functionals are up and running but I wanted to bring it up so we don't waste too much time working on a project file we'll just end up scrapping in the name of compatibility.

My thought was to use the #Dev project as our primary project file and offer conversion for VS. Maybe keep the OSP and convert to/from the other two?

Discuss.

[programble]

Maintaining compatibility with other IDEs is a very good idea.

[X@MPP]

T3hC13h, on 25 Dec, 2009 - 04:22 PM, said:

I was messing about with the OS project file structure and it hit me, we already have at LEAST 2 other major project/solution files from VS and #Dev. Why don't we just use one of those as our primary project file and at least support conversion for the other.

This is something we can wait on until the core functionals are up and running but I wanted to bring it up so we don't waste too much time working on a project file we'll just end up scrapping in the name of compatibility.

My thought was to use the #Dev project as our primary project file and offer conversion for VS. Maybe keep the OSP and convert to/from the other two?

Discuss.

#Dev and VS use the sln format dont they?
i was working on project file conversion for VC VC# F# VB etc to <name>osp
but if we are re doing it all oh well

[T3hC13h]

Lol you are correct, VS and #Dev both use the same solution and project file formats....probably should have checked that.

Anyways, what I don't want to happen is for us to put all kinds of work into the OSP format when we would be just as well off using the sln/proj format.

[X@MPP]

well yes i agree lets use the standards