Code/CFLite/CFNetwork: Difference between revisions

From kJams Wiki
Jump to navigation Jump to search
No edit summary
Line 10: Line 10:
## go to "configuration properties->debugging"
## go to "configuration properties->debugging"
## set "Command" to "$(SolutionDir)build\$(TargetName).app\Contents\Windows\$(TargetFileName)".
## set "Command" to "$(SolutionDir)build\$(TargetName).app\Contents\Windows\$(TargetFileName)".
## in VS2010 and later, actually you may need to just specify the full (in step 4 above), as "$(TargetName)" does not seem to expand correctly for debug vs. release
## in VS2010 and later, actually you may need to just specify the full path (in step 4 above), as "$(TargetName)" does not seem to expand correctly for debug vs. release
#Now build and run.
#Now build and run.
#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 16:36, 20 September 2014

This code available on this page is the results of the CFNetwork project on eLance. I hereby release it under the terms of the "New BSD License".

How to get started

  1. Install Bonjour Print Services for Windows. (you do not need to run the printer wizard nor set up a printer, this is just a service that CFTest makes use of)
  2. download CFNetwork and put it in your development tree
  3. in Visual Studio, Open the file "CFNetwork/CFTest/win_vs/CFTest.sln".
  4. In the "Solution Explorer"
    1. select "CFTest", right click it and pick "Properties"
    2. in the "Configuration:" menu, pick "All Configurations"
    3. go to "configuration properties->debugging"
    4. set "Command" to "$(SolutionDir)build\$(TargetName).app\Contents\Windows\$(TargetFileName)".
    5. in VS2010 and later, actually you may need to just specify the full path (in step 4 above), as "$(TargetName)" does not seem to expand correctly for debug vs. release
  5. Now build and run.
  6. for cleaner output during testing, you can temporarily set 'kExtraLogging' to 0 (that way you just get pass / fail rather than full logging)