Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Additional changes needed to .csproj files if using different VeriStand version #19

Open
jtcalvert opened this issue Jan 6, 2025 · 0 comments

Comments

@jtcalvert
Copy link

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:

image

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant