You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"If you are using a different version of VeriStand or a different file path location, update the VeriStandDir constant in the .csproj files."
However, this is not the only change you must make to those files. In addition to updating the VeriStandDir contant to the correct path, you must also update the hardcoded path in the PostBuildEvent tag, which is where the build will place the new controls. For example, if target VeriStand 2023, I would update line 180 in the CustomControlsExamples.csproj file like this:
Alternatively, the CustomControlsExamples.csproj file could be updated to extract the VeriStand version from the VeriStandDir constant and use that to build the path for where the custom controls DLL should be copied.
The text was updated successfully, but these errors were encountered:
In the readme, it has the instruction:
"If you are using a different version of VeriStand or a different file path location, update the VeriStandDir constant in the .csproj files."
However, this is not the only change you must make to those files. In addition to updating the VeriStandDir contant to the correct path, you must also update the hardcoded path in the PostBuildEvent tag, which is where the build will place the new controls. For example, if target VeriStand 2023, I would update line 180 in the CustomControlsExamples.csproj file like this:
Alternatively, the CustomControlsExamples.csproj file could be updated to extract the VeriStand version from the VeriStandDir constant and use that to build the path for where the custom controls DLL should be copied.
The text was updated successfully, but these errors were encountered: