%3CLINGO-SUB%20id%3D%22lingo-sub-974353%22%20slang%3D%22en-US%22%3ERules%20Extensions%20-%20Build%20and%20Compile%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-974353%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Feb%2012%2C%202016%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3EOnce%20you%20have%20the%20code%20typed%20up%20and%20your%20ready%20to%20test%20it%20the%20first%20thing%20you%20need%20to%20do%20is%20Build%20the%20Solution.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EAt%20the%20top%20of%20your%20Visual%20Studios%20Application%20you%20should%20have%20a%20section%20Labeled%20BUILD%3C%2FP%3E%3CBR%20%2F%3E%3CP%20style%3D%22padding-left%3A%2030px%22%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EClick%20on%20BUILD%3C%2FP%3E%3CBR%20%2F%3E%3CP%20style%3D%22padding-left%3A%2030px%22%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EClick%20on%20Build%20Solution%3C%2FP%3E%3CBR%20%2F%3E%3CP%3ELook%20for%20the%20Output%20window%20usually%20at%20the%20bottom%3C%2FP%3E%3CBR%20%2F%3E%3CP%20style%3D%22padding-left%3A%2030px%22%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%20%20%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EVerify%20no%20errors%3C%2FP%3E%3CBR%20%2F%3E%3CP%3ENavigate%20to%20the%20location%20the%20.dll%20was%20saved%2C%20if%20you%20dont%20know%20the%20it%20should%20be%20listed%20in%20the%20output%20window.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EIn%20my%20example%20this%20is%20set%20up%20in%20my%20lab%20and%20i%20have%20Visual%20Studios%20installed%20on%20the%20same%20server%20as%20my%20Synchronization%20Service.%20If%20the%20file%20was%20not%20saved%20to%20the%20extensions%20folder%20of%20the%20Synchronization%20Service%20you%20would%20want%20to%20move%20the%20file%20to%20that%20destination.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EOnce%20the%20file%20has%20been%20moved%20to%20that%20directory%20open%20the%20synchronization%20service.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-974353%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Feb%2012%2C%202016%20Once%20you%20have%20the%20code%20typed%20up%20and%20your%20ready%20to%20test%20it%20the%20first%20thing%20you%20need%20to%20do%20is%20Build%20the%20Solution.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-974353%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ebuild%20and%20compile%20code%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Erules%20extension%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft
First published on MSDN on Feb 12, 2016

Once you have the code typed up and your ready to test it the first thing you need to do is Build the Solution.


At the top of your Visual Studios Application you should have a section Labeled BUILD





Click on BUILD




Click on Build Solution


Look for the Output window usually at the bottom




Verify no errors


Navigate to the location the .dll was saved, if you dont know the it should be listed in the output window.


In my example this is set up in my lab and i have Visual Studios installed on the same server as my Synchronization Service. If the file was not saved to the extensions folder of the Synchronization Service you would want to move the file to that destination.


Once the file has been moved to that directory open the synchronization service.