Code/CFLite/CFNetwork: Difference between revisions

From kJams Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 3: Line 3:
To see work already completed, see the [[Code/CFLite/CFNetwork/Old|old page]]
To see work already completed, see the [[Code/CFLite/CFNetwork/Old|old page]]


'''Update''' this project has been completed.  Will be posting all source code soon.
'''Update''' this project has been completed.  <strike>Will be posting all source code soon.</strike>See below for code!
==CFTest Project==
==CFTest Project==
The latest [https://karaoke.kjams.com/cflite/downloads/cfnetwork.zip CFNetwork] test framework.
The latest [../cflite/downloads/cfnetwork.zip CFNetwork] test framework, which includes CFLite!


'''Update:''' Since the above was released, a bug has been fixed in CFBonjour.  Please get this [https://karaoke.kjams.com/cflite/downloads/delta.zip delta update].
==How to get started==
==How to get started==
#Install [http://support.apple.com/kb/DL999 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)
#Install [http://support.apple.com/kb/DL999 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)
#download [https://karaoke.kjams.com/cflite/downloads/cfnetwork.zip the CFTest project] and put it in your development tree
#download [../cflite/downloads/cfnetwork.zip the CFNetwork project] and put it in your development tree
##download the above [https://karaoke.kjams.com/cflite/downloads/delta.zip delta updater], and merge it with the CFTest project
#in Visual Studio, Open the file "CFNetwork/CFTest/win_vs/CFTest.sln".
#in VS2008, Open the file "CFNetwork/CFTest/win_vs/CFTest.sln".
#In the "Solution Explorer"
#In the "Solution Explorer"
## a) select "CFTest", right click it and pick "Properties"
## a) select "CFTest", right click it and pick "Properties"
Line 18: Line 16:
## c) go to "configuration properties->debugging"
## c) go to "configuration properties->debugging"
## d) set "Command" to "$(SolutionDir)build\$(TargetName).app\Contents\Windows\$(TargetFileName)".
## d) set "Command" to "$(SolutionDir)build\$(TargetName).app\Contents\Windows\$(TargetFileName)".
## e) in VS2010 and later, actually you may need to just specify the full path above, as "TargetName" does not expand correctly for debug vs. release
#Now build and run.
#Now build and run.
#your job is to provide any required new code (and of course fix any bugs) to get the output to 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 04:29, 19 September 2014

This page will document the results of the CFNetwork project on eLance.

To see work already completed, see the old page

Update this project has been completed. Will be posting all source code soon.See below for code!

CFTest Project

The latest [../cflite/downloads/cfnetwork.zip CFNetwork] test framework, which includes CFLite!

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 [../cflite/downloads/cfnetwork.zip the CFNetwork project] 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. a) select "CFTest", right click it and pick "Properties"
    2. b) in the "Configuration:" menu, pick "All Configurations"
    3. c) go to "configuration properties->debugging"
    4. d) set "Command" to "$(SolutionDir)build\$(TargetName).app\Contents\Windows\$(TargetFileName)".
    5. e) in VS2010 and later, actually you may need to just specify the full path above, as "TargetName" does not 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)