There are a few things we need to do to make it easier to manage and develop the code:
- The bugsproxy project is in Bugzilla folder. By convension, folder name should match project name.
- By convention, project name should be PascalCase, i.e.
Bugzproxy and not bugzproxy.
- We have a bunch of example console applications, which are not in the solution, which makes it difficult to access and edit them. we need to:
- Add a project to the solution in the samples folder (to be renamed to Samples). The projct should be some kind of content projct, because each file is compiled to a separate assembly, which is something VS doesn't know how to do.
- Rename samples.csproj to something else, which won't conflict
- Add all sample files to new projct.
- The new project will also have a build.bat file, which will build all files with msbuild and the current samples.csproj.
- Add a unit test project, and add unit tests to all supported API. This will allow running an API call for testing in a click of a button, including easy debugging.
- Where did the Properties folder go from the bugzproxy project, along with the AssemblyInfo.cs file? we need to restore it.
- the projct depends on the XMLRPC.NET library. since the project was created (and in fact, since the last commit), NuGet was created, and the library was uploaded to there. So we should add a dependency on the nuget package, instead of placing the DLL in the project folder.
well, I expected this to be markdown-aware.
bold
italics