Home/ Questions/Q 244385
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T21:00:01+00:00

I am using a SharedAssemblyInfo file which seems to be a ‘standard’ technique: http://blogs.msdn.com/jjameson/archive/2009/04/03/shared-assembly-info-in-visual-studio-projects.aspx

  • 0

I am using a SharedAssemblyInfo file which seems to be a ‘standard’ technique:
http://blogs.msdn.com/jjameson/archive/2009/04/03/shared-assembly-info-in-visual-studio-projects.aspx

I put the SharedAssemblyInfo.cs file into my web application because with web site projects I cannnot ‘add files as a link’.

But now I need to add a second web project to the solution and obviously the SharedAssemblyInfo file cannot be within both projects.

How do I get round this problem without having duplicate SharedAssemblyInfo files?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    One way to solve this problem from within a web site as opposed to a web project is via your source control provider.

    If you are using Visual Source Safe you can “share” the file to both projects (folders) and not branch. If you are using subversion 1.6 you can use a single file “externals” property. See this page for info.

    In the case of Team Foundation Server, you can look at this codeplex article. I don’t have any experience with TFS, but I think in the case of a SharedAssembly.cs the branch and merge solution would work fine.

    This means you will have to check the file in in one location and check it out in the other location for the change to take effect. However, have the AssemblyInfo out of sync during the development process probably won’t break anything.

    • 0