Windows 8.1 Upgrade Clearing .NET Component Registration
|Date:||13 January 2014|
|Product/Release:||Visual LANSA V13 SP1|
|Abstract:||Windows 8.1 Upgrade clears .NET Component Registration from the Windows registry|
|Submitted By:||LANSA Technical Support|
The ability to enrol .NET components was introduced
in Visual LANSA V13. See
Recently it was discovered that upgrading from Windows 8 to 8.1 has presented a possible issue when accessing 3rd party .NET components in Visual LANSA.
The exact cause to this issue is not known, but it does occur after upgrading from Windows 8 to 8.1. The DLL's for the .NET components still exist in their appropriate location but all registrations of these components have been cleared from their standard registry location, HKLM\Software\Wow6432Node\Microsoft\.NETFramework\AssemblyFolders.
Currently the only known solution is to re-register all the .NET components manually through RegEdit.
Any components that have been cleared will display an error message refering to the component missing.
See below for examples of the errors you may encounter:
- The following image is an example of how the enrolled .NET
component will appear in the Visual LANSA Source editor when the
registration is cleared by the Windows 8 upgrade to 8.1.
- The follwing image is an Example of how the source
code of a form or Reusuable Part, where a .NET component was defined,
would appear when the registration is cleared.
- This following is an example of the fatal error that will occur
if you try and run an application with an unregistered .NET component.