![]() If it doesn’t compile, then what? The shared code is now required to be different in two different projects and you may have no history as to what was changed. If the project compiles but doesn’t work correctly, you may not find out until you’ve given it to your users, with the worst case being unrecoverable data corruption. With careful planning, you’ll probably hit #1 75% of the time, but the other two are wrought with problems. The project compiles and doesn’t work like it did before.The project compiles and everything works just like it did before.When you do get around to working on it again, there’s three possibilities: Making one little change to a shared file or method which works fine in the current project could completely break a project that you haven’t worked on in a year. One of the largest issues with this type of system is that everything must be kept in sync all the time. While this technique works with a single developer across two or three projects, it gets more and more complicated as you add more projects and even more-so if you try to add more developers. There can be issues with this technique, especially when using shared services like DropBox.īecause of the latency involved, external items shared in a shared folder on a server or a file sharing service are never truly in-sync with one another. ![]() Quite often what users try to do is to export classes and modules to a shared folder and have everyone include those in their projects. A topic that comes up every once in a while on the forums is how to share code among several projects with more than one developer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |