Fixing the disappearing collection problem
Sometimes, when creating custom control classes that contain collections, the contents of those collections that are defined at design-time refuse to serialize from one instance of the project solution to the next. This is a known problem with the Windows Forms design-time and has to do with the way that resources are read back from the resource file when a project is reloaded. The resource is stored with the version number of the control that produced it and so, while you're testing your custom control and rebuilding it from time to time, the version number is automatically updated by default. This means that the next time you run the code, the resources you defined are no-longer recognized by the current version of the code. To overcome this problem, remove the automatic version generation code by editing the AssemblyInfo file manually and removing the asterisks from the version number. The following listing shows a modified AssemblyInfo file. using System.Reflection; using System.Runtime.CompilerServices;
// // General Information about an assembly is controlled through the following // set of attributes. Change these attribute values to modify the information // associated with an assembly. // [assembly: AssemblyTitle("")] [assembly: AssemblyDescription("")] [assembly: AssemblyConfiguration("")] [assembly: AssemblyCompany("")] [assembly: AssemblyProduct("")] [assembly: AssemblyCopyright("")] [assembly: AssemblyTrademark("")] [assembly: AssemblyCulture("")]
// // Version information for an assembly consists of the following four values: // // Major Version // Minor Version // Build Number // Revision // // You can specify all the values or you can default the Revision and Build Numbers // by using the '*' as shown below:
//[assembly: AssemblyVersion("1.0.*")] [assembly: AssemblyVersion("1.0.0")]
// // In order to sign your assembly you must specify a key to use. Refer to the // Microsoft .NET Framework documentation for more information on assembly signing. // // Use the attributes below to control which key is used for signing. // // Notes: // (*) If no key is specified, the assembly is not signed. // (*) KeyName refers to a key that has been installed in the Crypto Service // Provider (CSP) on your machine. KeyFile refers to a file which contains // a key. // (*) If the KeyFile and the KeyName values are both specified, the // following processing occurs: // (1) If the KeyName can be found in the CSP, that key is used. // (2) If the KeyName does not exist and the KeyFile does exist, the key // in the KeyFile is installed into the CSP and used. // (*) In order to create a KeyFile, you can use the sn.exe (Strong Name) utility. // When specifying the KeyFile, the location of the KeyFile should be // relative to the project output directory which is // %Project Directory%\obj\<configuration>. For example, if your KeyFile is // located in the project directory, you would specify the AssemblyKeyFile // attribute as [assembly: AssemblyKeyFile("..\\..\\mykey.snk")] // (*) Delay Signing is an advanced option - see the Microsoft .NET Framework // documentation for more information on this. // [assembly: AssemblyDelaySign(false)] [assembly: AssemblyKeyFile("")] [assembly: AssemblyKeyName("")]
Imports System Imports System.Reflection Imports System.Runtime.InteropServices
' General Information about an assembly is controlled through the following ' set of attributes. Change these attribute values to modify the information ' associated with an assembly.
' Review the values of the assembly attributes
<Assembly: AssemblyTitle("")> <Assembly: AssemblyDescription("")> <Assembly: AssemblyCompany("")> <Assembly: AssemblyProduct("")> <Assembly: AssemblyCopyright("")> <Assembly: AssemblyTrademark("")> <Assembly: CLSCompliant(True)>
'The following GUID is for the ID of the typelib if this project is exposed to COM <Assembly: Guid("C3A5B8EE-72DE-43E8-8FD2-246A9C12C9EF")>
' Version information for an assembly consists of the following four values: ' ' Major Version ' Minor Version ' Build Number ' Revision ' ' You can specify all the values or you can default the Build and Revision Numbers ' by using the '*' as shown below:
'<Assembly: AssemblyVersion("1.0.*")> <Assembly: AssemblyVersion("1.0.0")>
Note in both cases how the AssemblyVersion has been modified. The original AssemblyVersion line is commented out above. Return to Bob Powell's Windows Forms Tips and Tricks.
|
