The source code is split between two different solutions:
AdapdevFramework (the Adapdev.NET project)
Zanebug
Adapdev.NET
This solution contains the underlying test engine logic. Any non-GUI changes will most likely occur here. The Adapdev.UnitTest project contains the "client-side" test code, i.e. the various attributes that can be used for testing. Adapdev.UnitTest.Core contains the actual test engine.
Zanebug
This solution contains all of the front-end logic, to include the GUI, Console and VS.NET Add-in. Any front-end logic will need to be changed here.
Building
In order to use the source code, it's important to note that the following assemblies must be installed into the GAC:
Adapdev.dll
Adapdev.UnitTest.dll
Adapdev.UnitTest.Core.dll
log4net.dll
nunit.framework.dll (v2.2.0.0)
If you simply try to debug within VS.NET, you'll run into issues. If the dlls aren't in the GAC, you won't be able to run any tests. If they are in the GAC, they'll be referencing cached versions of the dlls located in the Zanebug install directory.
We recommend the following steps when any changes are made:
Build the full Adapdev.NET solution
Copy Adapdev.dll, Adapdev.UnitTest.dll, Adapdev.UnitTest.Core.dll from the FullBuild\bin\Debug directory into the Zanebug\lib directory
Build the Zanebug solution
If you've modified the VS.NET Add-in, make sure to build the ZanebugAddinSetup project
Run Zanebug\prepsetup.bat - this copies all of the build output into the setup folder
Open the buildsetup.iss (requires Inno Setup - see the readme.txt for the software info)
Compile the setup
Run the setup (make sure you've uninstalled any previous versions)
Another option is each time you make a change, open C:\Windows\assembly (the GAC) and delete the Adapdev references. Then build your solution and copy the new Adapdev dlls into the GAC. You'll need to do this each time.