This is a migrated thread and some comments may be shown as answers.

WPF45 Documents assemblies wrong version number

3 Answers 153 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Heiko
Top achievements
Rank 1
Iron
Veteran
Heiko asked on 22 Nov 2016, 11:20 AM

Directory: UI for WPF R3 2016/Binaries.NoXaml/WPF45.

I noticed that Telerik.Windows.Documents.xxx assemblies e. g.

  • Telerik.Windows.Documents.Core.dll
  • Telerik.Windows.Documents.Spreadsheet.dll
  • Telerik.Windows.Documents.Flow.dll
  • etc.

all have a version number of 2016.3.1021.40 where I had actually expected 2016.3.1021.45. At least in former releases these assemblies ended in .40/.45. Now they have the same version number as the assemblies under /WPF40. This is somewhat confusing and can lead to errors.

Regards
Heiko

3 Answers, 1 is accepted

Sort by
0
Martin Ivanov
Telerik team
answered on 24 Nov 2016, 10:21 AM
Hi Heiko,

We decided that there is no need to provide the document processing assemblies build under both .NET versions - 4.5 and 4.0. This is why since R3 2016 we ship only .NET40 document processing dlls. The .NET40 version is compatible with .NET45 so you can use the dlls in a .NET45 project without problems.

Regards,
Martin
Telerik by Progress
Telerik UI for WPF is ready for Visual Studio 2017 RC! Learn more.
0
Heiko
Top achievements
Rank 1
Iron
Veteran
answered on 28 Nov 2016, 09:50 AM

OK, your decision. I still find that confusing, in my opinion, you should stick to a fixed scheme. This is the second time that Telerik changed the naming scheme for the document processing dlls (first was a build date differing from the other assemblies) which doesn't make it easier for your customers to follow.

Anyway thanks for the reply.

Regards
Heiko

0
Martin Ivanov
Telerik team
answered on 29 Nov 2016, 10:24 AM
Hello Heiko,

Indeed, this is not very convenient, but the impact to the end user is minimized. And the size of the shipped dlls is reduced. However, excuse us for any inconvenience caused.

Regards,
Martin
Telerik by Progress
Telerik UI for WPF is ready for Visual Studio 2017 RC! Learn more.
Tags
General Discussions
Asked by
Heiko
Top achievements
Rank 1
Iron
Veteran
Answers by
Martin Ivanov
Telerik team
Heiko
Top achievements
Rank 1
Iron
Veteran
Share this question
or