none
mscorlib.fakes.dll override each other for multiple unit test projects

    Question

  • Hi,

       We have multiple unit test projects using VS 2012 Fakes. Each project generates its own mscorlib.fakes.dll for different classes/namespaces (as Fakes does not generate shims and stubs for all classes by default).

        This works fine if we run unit tests in VS 2012. However, our build controller output all assemblies to a single directory for the unit test solution. This will cause mscorlib.fakes.dll from different projects override each other. Note that all these unit test projects uses same version of mscorlib.

         We wanted to create a central place for mscorlib.fakes.dll or generate different name for each project, but no luck. Any idea for this?

    Thanks.

      

    Wednesday, October 30, 2013 3:45 AM

Answers

  • Thanks for your reply.

    What we end up to resolve this issue is to create a consolidated mscorlib.fakes and system.fakes for all projects. Then each project referenced these two shared files as links.

    With this, we make sure every project will get same mscorlib.fakes.dll and system.fakes.dll.

    Thursday, October 31, 2013 6:19 PM

All replies

  • Hi,

    I have moved this thread to Team Foundation Server - Build and release management forum for better response.

    Thanks,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Thursday, October 31, 2013 7:23 AM
  • Hi rogersong,

    Thanks for your post.

    According to your description, you may want to have a different output structure from the default.

    Please go through this blog below:

    http://lajak.wordpress.com/2011/05/07/customize-binaries-folder-in-tfs-team-build/.

    As described in that blog, you can customize your build process template by adding CreateDirectory activity behind the Run MSBuild for Project activity, then set the Directory property.

    Hope it can help.

    Best regards,

    Cece 


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Thursday, October 31, 2013 11:16 AM
    Moderator
  • Thanks for your reply.

    What we end up to resolve this issue is to create a consolidated mscorlib.fakes and system.fakes for all projects. Then each project referenced these two shared files as links.

    With this, we make sure every project will get same mscorlib.fakes.dll and system.fakes.dll.

    Thursday, October 31, 2013 6:19 PM