Nope solved the problem. This project is using code assets based on V2 of NuGet api access. I opened the solution in VS 2013 and it loaded just fine(no errors for core/intellisense). Moving forward VS 2015 uses NuGet api v3. The project would need to be migrated to the new API standard in order to support loading these assets in VS 2015 correctly. I have found information on how to do this.
However, It is my personal believe that the people who are much further in their understanding of programming have ether gone private, or moved on. Honestly I can't blame them. Very few people show an interest in helping and simply rant about something breaking with regards to something they have done nothing to help with. Then there is the very likely hood that G(3) lurks these forms to see what is posted publicly.
Honestly i have not been using this tool, not because i don't want to but because i know that in its current state it still detectable. This is based on my understanding of IO interaction and how the AC scans for block range read access request. I am just using it as a platform to learn more about C# and how to use Visual Studio. I thought i would just share these findings in case there was any one else poking around the source files to try and learn something more.
Link to understand more about migration:
https://docs.nuget.org/consume/packa...ackage-restore