Avoiding TFS build server error "The type or namespace name 'CrystalDecisions' could not be found
Avoiding TFS build server error "The type or namespace name 'CrystalDecisions' could not be found (are you missing a using directive or an assembly reference?)" and solution steps. This solution will be application to adding Enterprise Library assemblies also. This is good approach when you are developing a Integration Application.
How to avoid TFS build server error
Many developers come across this situation; it might help new build developers. This situation comes for many areas I am taking Crystal Reports are the example. Any organization preparing a Build server (TFS) first they will install the necessary DLLs in the server as per the company policy. I am assuming Crystal Reports are not included in company third party standards.
One application requires Crystal Reports so .NET developers developed simple reports and added the project in TFS. In local machine it will build perfectly because .NET IDE will have the necessary dlls. Now deployment turn came and developer created the TFSBuild Project and started Queuing the New Build from Team Explorer?Builds?Project ABC.
Developers found the build with errors saying Missing References. Because all Crystal Reports DLLS's are not available in TFS build server.
Solution: For this kind of situations we need to add the all necessary Dll's in our solution itself.
Step1: Copy your dlls's in root directory (Where your .sln file locates).
Step2: Create a new folder "BuildAssemblies" in our solution
Step3: Add the all dlls in your new folder from the step1
Step4: Check in all the dlls' from "BuildAssemblies"
Step5: Queue new build from Team Explorer?Builds?Project ABC
Attachments
