Code/CFLite/CFNetwork: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 15: | Line 15: | ||
##in the "Configuration:" menu, pick "All Configurations" | ##in the "Configuration:" menu, pick "All Configurations" | ||
##go to "configuration properties->debugging" | ##go to "configuration properties->debugging" | ||
##set "Command" to "$(SolutionDir)build\CFTest Debug.app\Contents\Windows\ | ##set "Command" to "$(SolutionDir)build\CFTest Debug.app\Contents\Windows\CFTest Debug.exe". | ||
#Now build and run. | #Now build and run. | ||
#your output should match the file "correct.txt" (except the bonjour services you have on your network may vary) | #your output should match the file "correct.txt" (except the bonjour services you have on your network may vary) | ||
#for cleaner output during testing, you can temporarily set 'kExtraLogging' to 0 (that way you just get pass / fail rather than full logging) | #for cleaner output during testing, you can temporarily set 'kExtraLogging' to 0 (that way you just get pass / fail rather than full logging) | ||
Revision as of 20:12, 1 August 2014
This page will document the results of the CFNetwork project on Freelancer.
To see work already completed, see the old page
CFTest Project
The latest CFNetwork test framework.
Update: Since the above was released, a bug has been fixed in CFBonjour. Please get this delta update.
How to get started
- Install Bonjour Print Services for Windows.
- download the CFTest project and put it in your development tree
- download the above delta updater, and merge it with the CFTest project
- in VS2008, Open the file "CFNetwork/CFTest/win_vs/CFTest.sln".
- In the "Solution Explorer"
- select "CFTest", right click it and pick "Properties"
- in the "Configuration:" menu, pick "All Configurations"
- go to "configuration properties->debugging"
- set "Command" to "$(SolutionDir)build\CFTest Debug.app\Contents\Windows\CFTest Debug.exe".
- Now build and run.
- your output should match the file "correct.txt" (except the bonjour services you have on your network may vary)
- for cleaner output during testing, you can temporarily set 'kExtraLogging' to 0 (that way you just get pass / fail rather than full logging)