CTP Known Issues

This page lists some important issues that have been discovered in CTP releases of Enterprise Library.

January 2007 CTP

  • You should run build and copy scripts after installing the source code. In addition to the installing the source code and tests, the Source Code Installer installs some scripts that enable you to build the library and copy all of the assemblies into the bin directory. These scripts are under <SrcRoot>\App Blocks\ and are called BuildLibrary.bat and CopyAssemblies.bat. The Visual Studio integrated configuration tool expects the compiled assemblies to be in this directory when using the EntLib3Src configuration set, so you should run these scripts before using the source code. In particular, the Validation Application Block QuickStarts use the EntLib3Src configuration set, so you must run these scripts before opening the QuickStart and attempting to use the configuration tool.
  • Microsoft.Practices.EnterpriseLibrary.Configuration.Design.HostAdapter.dll from source installer is delay signed. The copy of this assembly that is included in the <SrcRoot>\App Blocks\Lib folder is delay signed an will fail strong-naming verification. The correct fully-signed version of this assembly is installed to <InstallRoot>\bin. You should replace the delay-signed assembly with the fully-signed version.
  • Most QuickStarts do not use the EntLib3Src Configuration Set. This CTP introduces a new concept of "configuration sets" which refer to the set of assemblies that should be used for the Visual Studio-integrated configuration tool. It is possible to specify different configuration sets on a solution-by-solution basis. By default, all solutions will use the strong-named assemblies installed with Enterprise Library. However since the QuickStarts reference the non-strong-named source projects, these solutions should use the EntLib3Src configuration set. All of the QuickStarts, other than the Validation Application Block QuickStarts, use the default configuration set. While the VS configuration editor will still work, any changes you make to the QuickStart configuration files will include the Public Key Token of the strong-named assemblies. To get around this, you should choose the EntLib3Src configuration set by selecting the root solution node in the Solution Explorer and changing the EnterpriseLibraryConfigurationSet property to EntLib3Src.
  • Cannot Windows Forms designer when the Visual Studio-integrated configuration editor is open. In a Windows Forms project, you may see errors when attempting to open the designer of a Windows Form while the Enterprise Library Configuration Editor is open in Visual Studio. To get around this, you should close the configuration editor and try opening the form again.
  • Visual Basic code generated by the Application Block Software Factory may not compile. In some situations, the Block Factory may generate VB code that uses the Inherits keyword with interfaces, which is invalid. You should change Inherits to Implements to resolve this problem.
  • Guidance Packages do not show up as installable options if prerequsites are not met. In order to install the guidance packages, you need .NET 3.0 and GAX June 2006 CTP installed. If you do not have these installed, you will not see the guidance packages as selectable options in the MSI.
  • Long path names may cause some failures. Files and paths in this CTP are quite long, and if you try installing the source code or creating Application Block Software Factory projects in certain folders, you may break the Windows 255 character path limit. To avoid this problem, you should only use Enterprise Library from short initial paths. We plan to address this problem in the final release by shortening file and path names used by Enterprise Library.

December 2006 CTP

  • Guidance Packages do not show up as installable options if prerequsites are not met. In order to install the guidance packages, you need .NET 3.0 and GAX June 2006 CTP installed. If you do not have these installed, you will not see the guidance packages as selectable options in the MSI.
  • It is recommended that you install the CTP to the default file location. Using a non-default location may result in problems if you add or remove features at a later time.
  • Long path names may cause some failures. Files and paths in this CTP are quite long, and if you try installing the source code or creating Application Block Software Factory projects in certain folders, you may break the Windows 255 character path limit. To avoid this problem, you should only use Enterprise Library from short initial paths. We plan to address this problem in the final release by shortening file and path names used by Enterprise Library.

Last edited Jan 22, 2007 at 9:14 PM by tomhollander, version 7

Comments

asayonak Mar 30, 2007 at 1:25 PM 
it is not clear, are these open issues still "open" for February Beta release?

lsdeans Mar 12, 2007 at 10:27 PM 
johnman - we are able to run ent lib 3 on .NET 2.0 with no problems

johnman Dec 23, 2006 at 11:28 AM 
Will we be able to run ent lib 3 on .net 2 (since .net 3 is basically .net 2 with winfx extensions) since many companies are just now moving to .net 2 (let alone .net 3)?