solution doesn't build

[Kevin Greiner]

I forked the repo a few minutes ago, opened master branch and used Visual Studio 2013 to build. Here are the errors I received:

Error 9 The command "xcopy "C:\Users\kgreiner\Documents\sql-hunting-dog-fix-typos\HuntingDog2012\bin\Debug\HuntingDog.dll" "C:\Program Files (x86)\Hunting Dog\SSMS2012" /Y /R" exited with code 4. HuntingDog2012 Error 19 The command "xcopy "C:\Users\kgreiner\Documents\sql-hunting-dog-fix-typos\HuntingDog2014\bin\Debug\HuntingDog.dll" "C:\Program Files (x86)\Hunting Dog\SSMS2014" /Y /R" exited with code 4. HuntingDog2014 Error 42 An error occurred while validating. HRESULT = '80004005' C:\Users\kgreiner\Documents\sql-hunting-dog-fix-typos\HuntingDogInstall\HuntingDogInstall.vdproj HuntingDogInstall Error 51 The command "xcopy "C:\Users\kgreiner\Documents\sql-hunting-dog-fix-typos\HuntingDog\bin\Debug\HuntingDog.dll" "C:\Program Files (x86)\Hunting Dog\" /Y /R" exited with code 4. HuntingDog

When I attempt to run these commands from a command prompt, the error is "Access denied."

[Kevin Greiner]

Only administrator processes have the necessary permissions to write to the Program Files folders.

To resolve this, open Visual Studio 2013 as administrator and build.

I suggest the README section "How do I get set up?" be updated to reflect this.

[Kevin Greiner]

An alternative resolution is to modify the post-build steps to output the resulting binary to %APPDATA%\Microsoft\MSEnvShared\Addins which does not require administrative privileges for writing.

I have a number of improvements to the build documentation, if you're interested.

[alex empty]

Kevin, I am actually thinking abut removing this XCOPY command completely. it is more useful only once you installed product - then you build and quickly update DLLs in the destination folder. ..

what do you think?

[Kevin Greiner]

The use you describe is perfectly valid. If you want to remove the xcopy post-build, perhaps document how to accomplish this in the README.