This is a bit of a blast from the past type of post, but I would write about this anyway.
In 4.6.11 you may observe the following error logged on K2 service startup:
“Error”,”System”,”2010″,”TypeLoadError”,”SourceCode.Hosting.Server.Runtime.HostTypeLoader.LoadHostableTypes”,”2010 Type Load Error, Method ‘get_DisplayName’ in type ‘SourceCode.Hosting.Runtime.Group’ from assembly ‘SourceCode.Hosting.Runtime.IdentityService, Version=220.127.116.11, Culture=neutral, PublicKeyToken=16a2c5aaaa1b130d’ does not have an implementation.”
This error gets logged on K2 service startup and only in case you have certain rollups/coldfixes in place – it does not appear if you use 4.6.11 RTM.
This error can be caused by by the presence of SourceCode.Hosting.Runtime.IdentityService.dll in “C:\Program Files (x86)\K2 blackpearl\Host Server\Bin\HostedServers” – whereas this file is only supposed to be located in “C:\Program Files (x86)\K2 blackpearl\Host Server\Bin\HostedServices”. It’s a very good example of pitfalls related with use legacy K2 patching model involving manual files replacement – error prone and slow process. Luckily starting from 4.7 there are CU and FP with which installers almost fully addressed such type of problems.
So K2 released version 4.6.11 today and you may find all six components of the platform available in respective downloads section of portal.k2.com. Mysterious component number six is K2 Language Pack 4.6.11 (Preview) 🙂
So for all keen on trying latest and greatest time has come. And since recently you have an option to take Update Manager route which is available for you if you run 4.6.9 or later version of K2. There are certain caveats for use Update Manager, especially in how you need to do modify operations for updated environments (see “K2 blackpearl 4.6.11 Installation and Configuration – Update Manager PDF” for details).
Another interesting thing is that even if you are using combined installer or separate installers (meaning those which can be used to perform clean install) to update existing environment the same Update Manager type of install is being run (though on per component basis) and what is also new here is that once you done updating one of the components Update Manager reminds you about availability of update for another related component:
This possibly doesn’t look as a big thing for you, but as I normally see quite a few of support cases down to the simple fact that people start their upgrade but not upgraded all of the components in their environment I really appreciate this. People can plainly forget update some component and discover this only after a while when strange errors crop up and after placing support ticket and doing a bit of investigation work. So these reminders really going to save some time for all.
This release adds some new wizards to create dynamic item references and loop through them using the “For Each” wizard. There is also new License Report for managing K2 environment user licenses. This release fully supports Visual Studio 2015 and Windows 10 support (caveat: no Edge browser support, but this is normal – just try to remember situation with x64 IE support at the time when IE9 was released). Enhancements have been made to the K2 Designer and to the file and image attachment controls.
K2 4.6.11 Windows 10 Support
List of fixes and new features in each component can be found in the Release Notes:K2 4.6.11 Release Notes (KB001735)And the same for K2 connect can be found in separate release notes document:K2 Connect 4.6.11 Release Notes (KB000860)
Once you done with installing 4.6.11 RTM your list of K2 installed components going to look something like this:
And below is a new K2 Designer start page, which has clean and neat look, isn’t it? At least I like it better than what we had before.
Looking forward to see early adopters leveraging new features and how real adoption of this release will play out (given the nature of my work I can expect to see some first hand accounts 🙂 ).
So with new wave of releases from Microsoft we now have Visual Studio 2015 and Windows 10 amongst other things, and depending on what you do you may be more excited about one or another of these two. But what is common between VS 2015 and Windows 10 they all come with .NET 4.6. There is much more in these new versions, but for example for Windows 10 two salient features you will notice are built in .NET 4.6 and Edge browser.
Now to K2. Upcoming 4.6.11 release promises us full support of Windows 10 (excluding Edge browser), but there is an interesting thing with old versions of K2 and .NET 4.6. In case you are doing development for older versions of K2 platform you may want to use Windows 10 and/or Visual Studio 2015 on your development workstation and this may pose a small issue.
Here is screenshot from clean Windows 8.1 Enterprise machine on which Visual Studio 2015 installed. This is what we have in terms of .NET on this machine:
As you can see we have .NET 4.5 as well as .NET 4.6 installed. But here is what K2 Setup Manager 4.6.8 thinks about this:
So you don’t have .NET Framework 4.5 🙂 Some other applications may have issues with detecting your .NET version with advent of 4.6, but as Microsoft says in such cases “if app was written accordingly to our recommendations you won’t have any issues.” You may read up a bit about this in the related blog post at Aaron Stebner’s WebLog.
No worries – you will see this only with 4.6.8 and earlier versions, starting from 4.6.9 and onwards .NET detection works OK whether you have .NET 4.6 or not. You may also contact K2 support to obtain a coldfix for K2 setup manager 4.6.8 which will will solve this issue.