SURVEY:SUMMARY:BUILD_DIFFICULTY[not_applicable, reasonable_effort, code_problematic or string] reasonable_effort
SURVEY:SUMMARY:CLASSIFICATION[practical,theoretical,hardware] practical
SURVEY:SUMMARY:CORRECT_CODE_LOCATION[string] 
SURVEY:SUMMARY:PUBLISHED_CODE[not_applicable, yes, no] yes
SURVEY:SUMMARY:SAME_VERSION[not_applicable, yes, no_but_available, no_and_not_available] no_but_available
SURVEY:SUMMARY:STUDY_FOUND_CORRECT_CODE[not_applicable, yes, no] yes
SURVEY:AUTHOR1:BUILD_COMMENT[string] 1. Your student did not escape backlashes ('\')  while feeding path strings to the python calls. For example, the build log has this<br/>- <br/>>>> synthesize_dll("C:\Users\student6\Documents\GitHub\\repro\ccs12\WartellMHL12\src\Obfuscation\\results")<br/><br/>This call will work if the path is amended to,<br/><br/>>>> synthesize_dll("C:\\Users\student6\\Documents\\GitHub\\repro\ccs12\WartellMHL12\src\Obfuscation\\results")<br/><br/>2. The last sentence states the student was unable to proceed because the script was looking for version 11 while the version of Visual Studio he was using was upgraded to 12.<br/>  However the first command in the build log creates a new project by setting the vsvars path to within version 11 of Visual Studio (which is why it is looking specifically for version 11).<br/>  I've copied the line I'm referencing below<br/>- <br/>>>> create_project(".\\results", "C:\Users\student6\Downloads\Notepad++Portable\Notepad++Portable.exe", "C:\Program Files (<br/>x86)\Microsoft Visual Studio 11.0\Common7\Tools\vavars32.bat")<br/><br/>If that path is instead pointed to the location of vsvars for the currently used version of Visual Studio (not vavars, that seems to be a typo by the student), and if the path is correctly escaped as explained in (1), the build should  work just fine.
SURVEY:AUTHOR1:BUILD_DIFFICULTY[not_applicable, reasonable_effort, code_problematic or string] reasonable_effort
SURVEY:AUTHOR1:BUILD_DIFFICULTY_COMMENT[string] 
SURVEY:AUTHOR1:CLASSIFICATION[practical,theoretical,hardware] practical
SURVEY:AUTHOR1:CLASSIFICATION_COMMENT[string] 
SURVEY:AUTHOR1:CORRECT_CODE_LOCATION[string] 
SURVEY:AUTHOR1:PUBLIC_COMMENT[string] 1. Your student did not escape backlashes ('\')  while feeding path strings to the python calls. For example, the build log has this<br/>- <br/>>>> synthesize_dll( "C:\Users\student6\Documents\GitHub\\repro\ ccs12\WartellMHL12\src\Obfuscation\\results") <br/><br/>This call will work if the path is amended to, <br/><br/>>>> synthesize_dll( "C:\\Users\student6\\Documents\\GitHub\\repro \ccs12\WartellMHL12\src\Obfuscation\\results") <br/><br/>2. The last sentence states the student was unable to proceed because the script was looking for version 11 while the version of Visual Studio he was using was upgraded to 12.<br/>  However the first command in the build log creates a new project by setting the vsvars path to within version 11 of Visual Studio (which is why it is looking specifically for version 11).<br/>  I've copied the line I'm referencing below<br/>- <br/>>>> create_project(".\\results", "C:\Users\student6\Downloads\ Notepad++Portable\Notepad++Portable.exe", "C:\Program Files (<br/>x86)\Microsoft Visual Studio 11.0\ Common7\Tools\vavars32.bat") <br/><br/>If that path is instead pointed to the location of vsvars for the currently used version of Visual Studio (not vavars, that seems to be a typo by the student), and if the path is correctly escaped as explained in (1), the build should  work just fine.
SURVEY:AUTHOR1:PUBLISHED_CODE[not_applicable, yes, no] yes
SURVEY:AUTHOR1:SAME_VERSION[not_applicable, yes, no_but_available, no_and_not_available] no_but_available
SURVEY:AUTHOR1:SAME_VERSION_COMMENT[string] 
SURVEY:AUTHOR1:STUDY_FOUND_CORRECT_CODE[not_applicable, yes, no] yes