May 31, 2017 at 02:48 #20895whiteGhostParticipant
I’ ve been hunting around for some instruction on how you would like the structure to be incorporated. It almost looks like a separate project in some respects. It also looks like some of the files will overwrite some already existing from the APEX Path and Utility AI downloads. I had made a backup of the original project but decided to stop there and await some direction. Please advise.
CheersMay 31, 2017 at 10:46 #20899RamiKeymaster
Thanks for your post.
Really, there aren’t that many rules in regards to how you structure Apex Path and Apex Utility AI.
It is true that they share some DLLs (e.g. ApexShared), but the two distributions ship with identical shared DLLs, so it doesn’t matter which you choose, or whether you choose to overwrite one with the other. Any DLL that is not shared will not be named the same across the two distributions, so there should be no issue.
Apex Path is distributed with a “Full Source” zip file. This zip includes all the source code as normal C# code files, no DLLs. Thus, the DLL version and the full source version cannot be present in the same project simultanetously, since this results in ‘already exists’ compiler errors. So, you just need to choose whether you want to work with the full source or the DLLs (recommended). If you do choose the full source, then some of the DLLs that ship with Apex Utility AI will not be needed, namely the ones that are shared with Apex Path.
You must be logged in to reply to this topic.