search

MoreOnCode / MonoGameBookExamples

One framework for creating powerful cross-platform games.
http://www.monogame.net
Other
0 stars 0 forks source link

Devise scheme to share one MG with all samples #1

Open groundh0g opened 10 years ago

groundh0g commented 10 years ago

I'm not crazy about putting all samples in one solution, but that looks like the route MG is taking with theirs.

MG-Samples reference the MG source project via ../../../path notation, though, assuming that MG has been pulled to a specific (relative / parallel) path. I'm leaning more towards pulling a snapshot of MG into the samples folder. But I'm not really sold on that idea either.

Alternatives?

  1. NuGet, of which I'm completely oblivious? Not supported on all platforms, so have to link to source or DLLs for some projects anyway.
  2. Build MG DLLs and put in shared folder? Lots of work, updates are tedious. Not as flexible as project reference to MG source project(s). Could possibly automate, but I would still be the bottleneck for updates and patches.
  3. Some brilliant scheme that I (and none of my GitHub peers) have yet considered? Eureka! That's it!
  4. Pro's of pulling and storing a copy of the MG sources:
    • It makes debugging braindead easy.
    • Updates are easy. (I'm still the bottleneck, though.)
    • Easier to explain process to readers.
    • "It just works" for readers who skip the explanation.
groundh0g commented 10 years ago

Mentioned on MonoGame community site.

http://community.monogame.net/t/structuring-example-projects-for-a-book/1430?u=groundh0g

Moving ahead as planned. Will change course if I get some compelling feedback.