External Tools

This page covers examples of how Click-Coder is setup with other tools.

Professional Programmers typically use Click-Coder along with an IDE such as Visual Studio and extensions including code-completion. Click-Coder is best suited for pure AI coding  (e.g. "Please unify the two functions to format date string. And for the user table I'd like to also show last_login, is_verified and transaction_limit.") Click-Coder can suggest which files are needed to implement the task and then proceed. After approving the code change you typically use your IDE to build and run. Or, if you prefer to stay in Click-Coder for the full workflow cycle you can use Click-Coder to invoke batch files to do the build and run (see Settings | Paths). For example for the build: 

SET MSBUILD="C:\Program Files\...MSBuild.exe"

SET SOLUTION_PATH=C:\...

SET BUILD_PATH="c:\temp\build"

%MSBUILD% %SOLUTION_PATH% /nologo /t:Rebuild /p:Configuration=Debug /p:Platform=x64 /p:TargetFramework=net8.0 /p:OutputPath=%BUILD_PATH% /m /clp:ErrorsOnly > %BUILD_PATH%\build_output.txt 2>&1

exit /b %ERRORLEVEL%

Launch from IDE

If you want to launch Click-Coder directly from your IDE, simply type "clickcoder" in the terminal. This will automatically set the current directory as the selected project folder, streamlining your workflow.