VB Net Hook - Post-build event fails to copy

[ThickChips]

Hi,

Following the guide. The guide is listed in X8, I had to modify the path for 2022. 

In post build events, I set the field to:

copy "$(TargetPath)" "C:\Program Files\Mastercam 2022\Mastercam\chooks\"
copy "$(ProjectDir)\Resources\FunctionTable\$(TargetName).ft" "C:\Program Files\Mastercam 2022\Mastercam\chooks\$(TargetName).ft"

I get error at startup, exited with code 0.

Do spaces need properly escaped in the path name?

 

Thanks

[Mick George]

2 minutes ago, ThickChips said:

Hi,

Following the guide. The guide is listed in X8, I had to modify the path for 2022. 

In post build events, I set the field to:

copy "$(TargetPath)" "C:\Program Files\Mastercam 2022\Mastercam\chooks\"
copy "$(ProjectDir)\Resources\FunctionTable\$(TargetName).ft" "C:\Program Files\Mastercam 2022\Mastercam\chooks\$(TargetName).ft"

I get error at startup, exited with code 0.

Do spaces need properly escaped in the path name?

 

Thanks

With Mastercam 2022 and beyond it is no longer recommended to install to the chooks folder due to elevated permissions requirement.

 

Replace the post build step as follows, assuming these paths match your paths:

IF NOT EXIST "C:\Users\Public\Documents\Shared Mastercam 2022\Add-Ins" MKDIR "C:\Users\Public\Documents\Shared Mastercam 2022\Add-Ins"
copy "$(TargetPath)" "C:\Users\Public\Documents\Shared Mastercam 2022\Add-Ins\$(TargetFileName)"
copy "$(ProjectDir)Resources\FunctionTable\$(TargetName).ft" "C:\Users\Public\Documents\Shared Mastercam 2022\Add-Ins\$(TargetName).ft"

[byte]

15 hours ago, ThickChips said:

Hi,

Following the guide. The guide is listed in X8, I had to modify the path for 2022. 

In post build events, I set the field to:

copy "$(TargetPath)" "C:\Program Files\Mastercam 2022\Mastercam\chooks\"
copy "$(ProjectDir)\Resources\FunctionTable\$(TargetName).ft" "C:\Program Files\Mastercam 2022\Mastercam\chooks\$(TargetName).ft"

I get error at startup, exited with code 0.

Do spaces need properly escaped in the path name?

 

Thanks

Running visual studio in admin mode is typically required to access the program files folder, if you are not an admin, then it isn't possible.