Builder.com Article #6
Woo hoo. Here is my sixth article on Builder.com. Basically, it's how to idiot-proof your assembly versioning when you target different versions of the Framework.
Ok, they didn't make all the changes I wanted to, but oh well. I'll include the biggest one here. They left out a paragraph and a figure. This paragraph, along with the accompanying code, goes right after Figure B:
On the 24th, my article on code organization comes out. It ties in directly with the techniques in the past two articles. You're in for a real treat. I would like nothing better then for you guys to start using this system. Not for my sake, but for the sake if your customers. It really is the smart way to go.Building off my “single codebase” methodology I introduced in my last article, I’ve included a complete sample AssemblyInfo.vb file, as shown in Figure C. This is the preferred way to organize your code. Make sure to follow the instructions in my last article to ensure that this system is used properly.
<
Assembly: AssemblyDescription("DTS Engine for the .NET Framework. Features 100% ADO.NET Integration and 100% Extensibility.")>
<Assembly: AssemblyCompany("Interscape Technologies, Inc.")>
<Assembly: AssemblyProduct("GenX.NET 3.0")>
<Assembly: AssemblyCopyright("Copyright (C) 2002-2003 Interscape Technologies, Inc. All Rights Reserved.")>
<Assembly: AssemblyTrademark("Simple. Affordable. Solutions.")>
<Assembly: CLSCompliant(True)>
<Assembly: ComVisible(True)>#
If NET11 Then
<Assembly: AssemblyTitle("GenX.NET 3.0 for .NET 1.1")>
<Assembly: AssemblyVersion("3.0.5000.1143")>
<Assembly: AssemblyFileVersion("3.0.1143.0")>
#Else
<Assembly: AssemblyTitle("GenX.NET 3.0 for .NET 1.0")>
<Assembly: AssemblyVersion("3.0.4322.1142")>
<Assembly: AssemblyFileVersion("3.0.1142.0")>
#End IfFigure C: Complete Sample AssemblyInfo.vb File