Same assemblyInfo.vb across multiple projects

[Brian Henry]

is there any way to make an assembly file accessable across multiple
projects (we have over 20 that need the info all to be the same at build
version, title, desc, copyright,etc) i saw MS did this with the quick starts
with what looks like to be a short cut to a file in each project... is there
any way to have the assembly as the actuall file in one project and all the
others reference it? this is also a source controled solution too by the
way... all the projects are located in the same solution also...

thanks

[Peter Huang]

RE: Same assemblyInfo.vb across multiple projects

Hi Brian,

I think to achieve this we need to involve the vss, here is a link you may
take a look.

Team Development with Visual Studio .NET and Visual SourceSafe
<http://msdn.microsoft.com/library/de...-us/dnbda/html
/tdlg_rm.asp>

Specifically, Chapter 5: ¡°The Build Process: Consider Centralizing
Assembly Version
Numbers¡±:

Consider Centralizing Assembly Version Numbers
To update the assembly version information for multiple assemblies, the
build
script or build coordinator must check out and update multiple AssemblyInfo
files.
To centralize the version information and enable a single file checkout and
update,
consider the following approach:
1. Place the AssemblyVersion attribute in a single source file, for example
AssemblyVersion Info.cs or AssemblyVersion Info.vb.
2. Share the file across any projects that need to share the same version
number within VSS.

This approach assumes that you want the same assembly version assigned to
all assemblies generated by a particular system build.


Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

[Brian Henry]

Re: Same assemblyInfo.vb across multiple projects

thanks!

""Peter Huang"" <v-phuang@online.m icrosoft.com> wrote in message
news:AGAkxHreEH A.1256@cpmsftng xa06.phx.gbl...[color=blue]
> Hi Brian,
>
> I think to achieve this we need to involve the vss, here is a link you may
> take a look.
>
> Team Development with Visual Studio .NET and Visual SourceSafe
> <http://msdn.microsoft.com/library/de...-us/dnbda/html
> /tdlg_rm.asp>
>
> Specifically, Chapter 5: ¡°The Build Process: Consider Centralizing
> Assembly Version
> Numbers¡±:
>
> Consider Centralizing Assembly Version Numbers
> To update the assembly version information for multiple assemblies, the
> build
> script or build coordinator must check out and update multiple
> AssemblyInfo
> files.
> To centralize the version information and enable a single file checkout
> and
> update,
> consider the following approach:
> 1. Place the AssemblyVersion attribute in a single source file, for
> example
> AssemblyVersion Info.cs or AssemblyVersion Info.vb.
> 2. Share the file across any projects that need to share the same version
> number within VSS.
>
> This approach assumes that you want the same assembly version assigned to
> all assemblies generated by a particular system build.
>
>
> Best regards,
>
> Peter Huang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>[/color]