Not sure whether this is an issue or not, but sometimes I get this warning from my build:
The following assembly has dependencies on a version of the .NET Framework that is higher than the target and might not load correctly during runtime causing a failure: AjaxControlToolkit, Version=15.1.4.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e. The dependencies are: System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a. You should either ensure that the dependent assembly is correct for the target framework, or ensure that the target framework you are addressing is that of the dependent assembly.
What makes this odd is that:
1) I don't encounter it all the time. e.g. if I "clean" my build, then do a "rebuild all" I don't normally see it (but sometimes I do).
2) my applications web.config has these lines in it:
<compilation targetFramework="4.5.2">
<httpRuntime targetFramework="4.5.2"/>
Both of which (in my opinion) meet the requirement that "the dependent assembly is correct for the target framework" (i.e. because 4.5.2 is higher than the System.Design Version=4.0.0.0 that it is complaining about).
Anyway's, just wondering if anybody else has encountered this (as I don't really want my release build fooming on my live server).
Thanks
Chris
Comments: It will take me a while to provide you with a sample project (even if I wanted to) - as this is for my website http://www.victorianhawk.com/ (which has a large code base). I can say the following however: 1) It has taken me a week or so to upgrade my code base from asp.net 3.5 to asp.net 4.5.2 (visual studio 2015). As part of this, visual studio added this line to my web.config: <pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID"> Now, I took controlRenderingCompatibilityVersion out this morning, to see if it made any difference - but to no evail! Whilst the warning message initially disappeared - I have seen it at least once this afternoon (i.e. the "random behaviour" compile warning). Do you think controlRenderingCompatibilityVersion could be causing "linking" to incorrect versions of asp.net libraries? NOTE: I can't easily remove it at present, because I'm using the compiled css control adapters (asp.net 2.0 updated to asp.net 4.5.2). NOTE: whilst I did strip out the css control adapters earlier today, I still saw the "AjaxControlToolkit warning" at least once. Can you recommend any asp.net dll "walkers" that will show me the dependencies (e.g. if it's picking up an incorrect one from somewhere)?
The following assembly has dependencies on a version of the .NET Framework that is higher than the target and might not load correctly during runtime causing a failure: AjaxControlToolkit, Version=15.1.4.0, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e. The dependencies are: System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a. You should either ensure that the dependent assembly is correct for the target framework, or ensure that the target framework you are addressing is that of the dependent assembly.
What makes this odd is that:
1) I don't encounter it all the time. e.g. if I "clean" my build, then do a "rebuild all" I don't normally see it (but sometimes I do).
2) my applications web.config has these lines in it:
<compilation targetFramework="4.5.2">
<httpRuntime targetFramework="4.5.2"/>
Both of which (in my opinion) meet the requirement that "the dependent assembly is correct for the target framework" (i.e. because 4.5.2 is higher than the System.Design Version=4.0.0.0 that it is complaining about).
Anyway's, just wondering if anybody else has encountered this (as I don't really want my release build fooming on my live server).
Thanks
Chris
Comments: It will take me a while to provide you with a sample project (even if I wanted to) - as this is for my website http://www.victorianhawk.com/ (which has a large code base). I can say the following however: 1) It has taken me a week or so to upgrade my code base from asp.net 3.5 to asp.net 4.5.2 (visual studio 2015). As part of this, visual studio added this line to my web.config: <pages controlRenderingCompatibilityVersion="3.5" clientIDMode="AutoID"> Now, I took controlRenderingCompatibilityVersion out this morning, to see if it made any difference - but to no evail! Whilst the warning message initially disappeared - I have seen it at least once this afternoon (i.e. the "random behaviour" compile warning). Do you think controlRenderingCompatibilityVersion could be causing "linking" to incorrect versions of asp.net libraries? NOTE: I can't easily remove it at present, because I'm using the compiled css control adapters (asp.net 2.0 updated to asp.net 4.5.2). NOTE: whilst I did strip out the css control adapters earlier today, I still saw the "AjaxControlToolkit warning" at least once. Can you recommend any asp.net dll "walkers" that will show me the dependencies (e.g. if it's picking up an incorrect one from somewhere)?