Skip to main content


 

Symptoms

 


When performing installation of K2 4.6.8 or earlier on a machine which has Visual Studio 2015 installed K2 Setup Manager unable to proceed flagging that Microsoft .NET Framework 4.5 prerequisite is not installed. Both .NET Framework 4.5 and 4.6 (which goes along with Visual Studio 2015) are installed on the machine.
 

 

Diagnoses

 


This is known issue with K2 Setup Manager 4.6.8 and earlier versions - they unable to detect .NET Framework version correctly when .NET 4.6 is installed. Some additional details on .NET 4.6 can be found below.

The .NET Framework 4.6 is an in-place upgrade for all of the following versions of the .NET Framework:
.NET Framework 4
.NET Framework 4.5
.NET Framework 4.5.1
.NET Framework 4.5.2

An in-place upgrade means that if you install the .NET Framework 4.6 when any of the above versions of versions of the .NET Framework are installed on your PC, .NET Framework 4.6 setup will upgrade them and you will be left with only the .NET Framework 4.6 installed afterwards. In addition, any attempts to install older versions of the .NET Framework 4 family when the .NET Framework 4.6 is already present will result in .NET Framework setup blocking you from installing because it detects that a newer version is already installed.
.NET Framework 4.6 included with Visual Studio 2015 and it is also included with Windows 10.
 

 

Resolution

Upgrade to K2 4.6.9 or newer version. In cases where it is not possible please contact K2 support to request a coldfix for K2 Setup Manager 4.6.8

 

 

 

NOTE: All versions of K2 older than 4.6.11 do not support .NET 4.6. This is indicated in K2 blackpearl Compatibility Matrix. The coldfix mentioned above can only be useful to allow you to install K2 for Visual Studio 4.6.8 components on Windows 10 developer's machine where there is no option of removing .NET 4.6. In all of the other scenarious using .NET 4.6 on K2 server of any version older than 4.6.11 puts you into unsupported state. To get full support for .NET 4.6 you havre to upgrade to K2 4.6.11 or newer version of K2. Please refer to .NET section of K2 blackpearl Compatibility Matrix for details.

 

 



 
Be the first to reply!

Reply