I gave a question about upgrading csla from 4.5.10 to 4.5.20...
The main question is why each time it becomes harder and harder of upgrading project to use newer version of csla.
My project is running under csla 4.5.10 and .net framework 4 CP.
Right now I'm trying to upgrade it to use csla 4.5.20 because, I suppose the problem with asyncrhonious running of BeginFetch is resolved.
I have about 11 projects in solution the references Csla, and that's not enough to add only Csla library to the each project. I also need at least add: System.Runtime and System.Threading.Tasks that coming with Microsoft.Bd.Async package.
My question is how can I do it faster without wasting a lot of time trying to unserstand what I need to add to References to be able to lunch the application epsecially if I'm using installation package and I don't want to spend time to investigate source code of Csla?
And why each new version of Csla becomes more harder for upgrading...
Here is the error what I'm receiving:
1>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): warning MSB3268: The primary reference "Csla.Xaml, Version=4.5.20.0, Culture=neutral, PublicKeyToken=93be5fdc093e4c30, processorArchitecture=MSIL" could not be resolved because it has an indirect dependency on the framework assembly "System.Threading.Tasks, Version=2.5.16.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v4.0,Profile=Client". To resolve this problem, either remove the reference "Csla.Xaml, Version=4.5.20.0, Culture=neutral, PublicKeyToken=93be5fdc093e4c30, processorArchitecture=MSIL" or retarget your application to a framework version which contains "System.Threading.Tasks, Version=2.5.16.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
1>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): warning MSB3268: The primary reference "Csla, Version=4.5.20.0, Culture=neutral, PublicKeyToken=93be5fdc093e4c30, processorArchitecture=MSIL" could not be resolved because it has an indirect dependency on the framework assembly "System.Threading.Tasks, Version=2.5.16.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v4.0,Profile=Client". To resolve this problem, either remove the reference "Csla, Version=4.5.20.0, Culture=neutral, PublicKeyToken=93be5fdc093e4c30, processorArchitecture=MSIL" or retarget your application to a framework version which contains "System.Threading.Tasks, Version=2.5.16.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
When I'm adding System.Runtime and System.Threading.Tasks to all my projects, in the Main Project I begin to receive error:
15>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,7): warning MSB3268: The primary reference "Csla" could not be resolved because it has an indirect dependency on the framework assembly "System.Runtime, Version=1.5.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v4.0,Profile=Client". To resolve this problem, either remove the reference "Csla" or retarget your application to a framework version which contains "System.Runtime, Version=1.5.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
15>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,7): warning MSB3268: The primary reference "Csla.Xaml" could not be resolved because it has an indirect dependency on the framework assembly "System.Runtime, Version=1.5.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v4.0,Profile=Client". To resolve this problem, either remove the reference "Csla.Xaml" or retarget your application to a framework version which contains "System.Runtime, Version=1.5.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
Not only for Csla. but for all my project that are referenced by Main Project.
Thanks in advance.
I ran into the same thing. I discovered that NuGet was creating an app.config in each project that "redirects" the version number for those two dlls.. But that app.config was not added to the project. Once I manually added that new app.config to the project I was able to get it to build.
Copyright (c) Marimer LLC