Installer leaves root owned files

[Charles]

The installer requires sudo on UnixLike system and one side effect of this is the remainder of files that cannot be manipulated when not root:

Source/Cobra.MSBuild/TestProjects/ExampleSolution/HelloWorld/bin/Debug/HelloWorld.exe: Operation not permitted
Source/Cobra.MSBuild/TestProjects/ExampleSolution/HelloWorld/bin/Debug/HelloWorld.exe.mdb: Operation not permitted
Source/Cobra.MSBuild/TestProjects/ExampleSolution/HelloWorld/bin/Debug: Operation not permitted
Source/Cobra.MSBuild/TestProjects/ExampleSolution/HelloWorld/bin: Operation not permitted
Source/Cobra.MSBuild/TestProjects/ExampleSolution/HelloWorld/obj/x86/Debug/HelloWorld.cobraproj.FilesWrittenAbsolute.txt: Operation not permitted
Source/Cobra.MSBuild/TestProjects/ExampleSolution/HelloWorld/obj/x86/Debug/HelloWorld.exe: Operation not permitted
Source/Cobra.MSBuild/TestProjects/ExampleSolution/HelloWorld/obj/x86/Debug/HelloWorld.exe.mdb: Operation not permitted
Source/Cobra.MSBuild/TestProjects/ExampleSolution/HelloWorld/obj/x86/Debug: Operation not permitted
Source/Cobra.MSBuild/TestProjects/ExampleSolution/HelloWorld/obj/x86: Operation not permitted
Source/Cobra.MSBuild/TestProjects/ExampleSolution/HelloWorld/obj: Operation not permitted
Source/hello.cobra: Operation not permitted
Source/InstallFromWorkspace.exe.mdb: Operation not permitted
Source/Misc/hello.exe.mdb: Operation not permitted

To fix this, possibilities include:

• Modify the owner or perms afterwards
• Run the commands that create these files in such a way that this doesn't happen in the first place

Btw, the current workaround is to issue this command from within the workspace

sudo chown -R MYUSERNAME .