0

There are some modules in one workspace such as login module, user register module. It belongs its own project. Other modules call them. But what is the advantage and disadvantage in multiple project in one workspace

rmaddy
  • 314,917
  • 42
  • 532
  • 579
Dean Lee
  • 781
  • 2
  • 7
  • 13
  • 2
    Compare https://stackoverflow.com/questions/21631313/xcode-project-vs-xcode-workspace-differences. – Martin R Aug 14 '18 at 07:19
  • @Martin R thanks. But I think the answer you provided means what project and workspace are. I still don't know why use this. Just for code re-use? – Dean Lee Aug 14 '18 at 07:56
  • Possible duplicate of [Xcode Project vs. Xcode Workspace - Differences](https://stackoverflow.com/questions/21631313/xcode-project-vs-xcode-workspace-differences) – il3v Aug 14 '18 at 09:16
  • The answer also covers what you're asking. They say that projects are sufficient in most cases and workspaces should be used only if really necessary, with the exception of CocoaPods, that *requires* you to use workspaces (in fact, it does that for you at the moment you initialize it). "Really necessary", at least in my experience, means "only if you are working on a complex environment covering multiple apps sharing some non-trivial functionalities". Other than that, a single project should be good for you – il3v Aug 14 '18 at 09:19
  • @il3v thanks. I should look into it carefully – Dean Lee Aug 14 '18 at 10:52

0 Answers0