Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Our unit tests expect to find a certain assembly in the GAC. I am wondering what is the best way to put the assembly in the GAC on the build server that is part of TFS2010 automated build?
Is it a good idea to use a post build event with gacutil /i?
Are there better alternatives?
Do your unit tests expect the DLL in the GAC or just available to .NET assembly probing? If it’s actually the latter, why don’t you use [DeploymentItem()] attributes and have the assembly copied to the test folder and then found by .NET via probing? Another option would be to use a HintPath in your test DLL’s config file.