10 reasons why the build works locally
Fails on the build server This is a braindump: 1. Developer did not check all the files in, or
Developer doesn' t have the latest files (sometimes TFs hiccups getting latest
DLLs files ). 2. Different modes (release vs. Debug). Either # If
Debug, or project is unmarked in Configuration Manager. 3. Different bin structure-each project gets its own
(Default for Visual Studio), vs. Single shared bin for all (default for TFs ).
This is especially common when different versions of the same assembly is
Referenced in multiple projects in the same solution. 4. Different
Platform/Configuration 5. The build is running other steps (perhaps
Packaging or command-line unit tests) 6. Different bitness, say developer workstation is
64-bit, but build server is 32-bit, and some extra step breaks because
This. 7. Rebuild-vs-build. developer not running a rebuild.
Hence there's an error in creating a DLL, but it already exists on dev Machine
Due to some other process, but build server fails. 8. Workspace mapping is incorrect-TFs not getting
All the files it needs 9. Unit test code coverage-Visual Studio (at least
2008) can be very britle running command line unit tests and code
Coverage. 10. treat warnings as compile errors-depending on
your process, the build server may fail on these, but Visual Studio may only
flag you with a warning (which Dev ignores)
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
