View previous topic :: View next topic |
Author |
Message |
eceakturk
Joined: 30 Jan 2017 Posts: 3
|
Posted: Wed Nov 29, 2017 4:54 pm Post subject: Infralution.Localization.Wpf.dll - 4.5 version? |
|
|
We are on the latest version of Globalizer (3.9.7.0, developer edition) - is there a 4.5 version of the Infralution.Localization.Wpf.dll?
The one I have is 2.0 (file version is 3.3.3.0).
If not this is something we need as part of our build process asap. |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Thu Nov 30, 2017 9:04 pm Post subject: |
|
|
The Infralution.Localization.Wpf assembly is targeted at the .NET 3.5 Framework. However it can be used by applications targeting .NET 4 or 4.5 (as it is in the sample WPF project for VS2015). _________________ Infralution Support |
|
Back to top |
|
|
jbaltika
Joined: 01 Dec 2017 Posts: 1
|
Posted: Fri Dec 01, 2017 7:04 pm Post subject: Clarification about .net 4.6.1 |
|
|
Hi guys,
Your current library is build against .net3.5 framework. That means any software which uses your library at runtime needs install .net2/3.5 as part of requirement to run. Its 2017 and Windows 10 doesn't come with .net2/3.5 installed by default or should be. So we need some work arounds.
I just want make sure that i am clear. We don't need modify existing your product, but give as library so we could substitute during MSBuild and our clients would not need install .net2/3.5 on their windows 10 machines ...
http://jimbojet.blob.core.windows.net/img/Infralution.jpg
In simple words these action required:
1. Open Infralution.Localization.Wpf.csproj
2. Change build target to v4.6.1
3. Add reference System.Xaml
4. Make sure that all references points to 4.6.1 version
5. Compile and send that lib to Ece or me |
|
Back to top |
|
|
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Fri Dec 01, 2017 10:14 pm Post subject: |
|
|
If an application compiled against .NET 4.6 uses/references a .NET 3.5 DLL (like Infralution.Localization.Wpf.dll) it does not mean that .NET 3.5 must be installed on the target system. Any given .NET application can only load one version of the .NET Framework assemblies - which is determined by the EXE. Even though Infralution.Localization.Wpf.dll is built against .NET 3.5 it can quite happily be referenced by .NET 4.6 application and run on a clean version of Windows 10 which does not have .NET 2/3 installed on it. For DLLs the Framework version just means that the compiler restricts if from using methods or classes which are not available in the set Framework.
Try this yourself - I've just verified that this is true by running the setting the Sample WPF application framework to .NET 4.6 and then copying just the EXE, satellite resource dlls and Infralution.Localization.Wpf.dll to a clean install of Windows 10 (no .NET 2/3) where it runs without issue.
While you may be using the latest and greatest from Microsoft some of our customers still need to support older operating systems and products and so Globalizer continues to support .NET 2/3. Which means that we need to keep the Infralution.Localization.Wpf compatible with .NET 3.5.
If there is some other reason why you want to change the Framework of the Infralution.Localization.Wpf project then we make the source code freely available via Code Project:
https://www.codeproject.com/Articles/35159/WPF-Localization-Using-RESX-Files
You can download this and follow the simple steps you kindly provided to change the framework. _________________ Infralution Support |
|
Back to top |
|
|
eceakturk
Joined: 30 Jan 2017 Posts: 3
|
Posted: Mon Dec 04, 2017 7:53 pm Post subject: |
|
|
Thanks so much - this is perfect for our needs! |
|
Back to top |
|
|
|