.net – DocumentFormat.OpenXml 2.5 in .NET 3.5.1 gives warnings

netopenxmlopenxml-sdk

I have decided to use .NET 3.5.1 but when I add the DocumentFormat.OpenXml 2.5 throught the NuGet Package Console with Install-Package DocumentFormat.OpenXml I get a lot of warnings :

1>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5):
warning MSB3258: The primary reference "DocumentFormat.OpenXml,
Version=2.5.5631.0, Culture=neutral, PublicKeyToken=123,
processorArchitecture=MSIL" could not be resolved because it has an
indirect dependency on the .NET Framework assembly
"System.Data.SqlXml, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=123" which has a higher version "4.0.0.0" than the
version "2.0.0.0" in the current target framework.

1>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5):
warning MSB3258: The primary reference "DocumentFormat.OpenXml,
Version=2.5.5631.0, Culture=neutral, PublicKeyToken=123,
processorArchitecture=MSIL" could not be resolved because it has an
indirect dependency on the .NET Framework assembly "System.Security,
Version=4.0.0.0, Culture=neutral, PublicKeyToken=123" which has a
higher version "4.0.0.0" than the version "2.0.0.0" in the current
target framework.

1>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5):
warning MSB3268: The primary reference "DocumentFormat.OpenXml,
Version=2.5.5631.0, Culture=neutral, PublicKeyToken=123,
processorArchitecture=MSIL" could not be resolved because it has an
indirect dependency on the framework assembly "System.Xaml,
Version=4.0.0.0, Culture=neutral, PublicKeyToken=123" which could not
be resolved in the currently targeted framework.
".NETFramework,Version=v3.5". To resolve this problem, either remove
the reference "DocumentFormat.OpenXml, Version=2.5.5631.0,
Culture=neutral, PublicKeyToken=123, processorArchitecture=MSIL" or
retarget your application to a framework version which contains
"System.Xaml, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089".

1>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5):
warning MSB3258: The primary reference "DocumentFormat.OpenXml,
Version=2.5.5631.0, Culture=neutral, PublicKeyToken=123,
processorArchitecture=MSIL" could not be resolved because it has an
indirect dependency on the .NET Framework assembly "Accessibility,
Version=4.0.0.0, Culture=neutral, PublicKeyToken=123" which has a
higher version "4.0.0.0" than the version "2.0.0.0" in the current
target framework.

1>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1605,5):
warning MSB3268: The primary reference "DocumentFormat.OpenXml,
Version=2.5.5631.0, Culture=neutral, PublicKeyToken=123,
processorArchitecture=MSIL" could not be resolved because it has an
indirect dependency on the framework assembly "System.Numerics,
Version=4.0.0.0, Culture=neutral, PublicKeyToken=123" which could not
be resolved in the currently targeted framework.
".NETFramework,Version=v3.5". To resolve this problem, either remove
the reference "DocumentFormat.OpenXml, Version=2.5.5631.0,
Culture=neutral, PublicKeyToken=123, processorArchitecture=MSIL" or
retarget your application to a framework version which contains
"System.Numerics, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=123".

It seems like DocumentFormat.OpenXml 2.5 needs or is using .Net 4.

Should I worry about these warnings [and stick to .net 4.5 where I don't get these warnings]?

I want to avoid .net 4.5 since they need admin rights to be installed.

Best Answer

From the Open XML SDK 2.5 for Microsoft Office download page, the SDK requires the Microsoft .NET Framework version 4.0.

If you want to use the Microsoft .NET Framework version 3.5 SP1, you can use the Open XML SDK 2.0 only.

Related Solutions

.net – Difference between decimal, float and double in .NET

float and double are floating binary point types. In other words, they represent a number like this:

10001.10010110011

The binary number and the location of the binary point are both encoded within the value.

decimal is a floating decimal point type. In other words, they represent a number like this:

12345.65789

Again, the number and the location of the decimal point are both encoded within the value – that's what makes decimal still a floating point type instead of a fixed point type.

The important thing to note is that humans are used to representing non-integers in a decimal form, and expect exact results in decimal representations; not all decimal numbers are exactly representable in binary floating point – 0.1, for example – so if you use a binary floating point value you'll actually get an approximation to 0.1. You'll still get approximations when using a floating decimal point as well – the result of dividing 1 by 3 can't be exactly represented, for example.

As for what to use when:

For values which are "naturally exact decimals" it's good to use decimal. This is usually suitable for any concepts invented by humans: financial values are the most obvious example, but there are others too. Consider the score given to divers or ice skaters, for example.
For values which are more artefacts of nature which can't really be measured exactly anyway, float/double are more appropriate. For example, scientific data would usually be represented in this form. Here, the original values won't be "decimally accurate" to start with, so it's not important for the expected results to maintain the "decimal accuracy". Floating binary point types are much faster to work with than decimals.

C# – Could not load file or assembly or one of its dependencies

Check if you are referencing an assembly which in turn referencing an old version of unity. For example let's say you have an assembly called ServiceLocator.dll which needs an old version of Unity assembly, now when you reference the ServiceLocator you should provide it with the old version of Unity, and that makes the problem.
May be the output folder where all projects build their assemblies, has an old version of unity.

You can use FusLogVw to find out who is loading the old assemblies, just define a path for the log, and run your solution, then check (in FusLogvw) the first line where the Unity assembly is loaded, double click it and see the calling assembly, and here you go.

Best Answer

Related Solutions

.net – Difference between decimal, float and double in .NET

C# – Could not load file or assembly or one of its dependencies

Related Topic