Guidance on programmatic up-to-date check
See original GitHub issueVisual Studio Version: 16.3.9
I’m building an MSBuild tools NuGet package (or whatever they’re actually called) which takes artefacts produced from an SSDT project (.sqlproj) and uses them in a F# project (.fsproj). I’ve got it working with MSBuild command line but was running into issues with getting Visual Studio to run the build on changes. @davidwengier helpfully pointed me at up-to-date checks.
Because I’m finding the artefacts programmatically (in my package’s targets) I understand I need to override one of the CollectUpToDateCheck*DesignTime
targets. (At least I think I do, based on the documentation and this comment.)
However I’m not quite sure which one to override. The one I would expect to override based on the docs would be CollectUpToDateCheckBuiltDesignTime
, but that’s already doing some things which I wouldn’t want to copy and paste into my package in case it changes in the project system.
(I am new to MSBuild and all that, so I could be majorly missing something here!)
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (7 by maintainers)
I opened https://github.com/dotnet/project-system-tools/pull/211 to fix the problem with the first build so keep an eye out for a new release of Project System Tools in the not too distant future.
Thanks for the guidance on the up-to-date check, @drewnoakes. Super helpful! I very much appreciate it. I’ll continue on the MSBuild side of things now!