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: Thanks for your assistance in the matter :) I have decided to avoid the obout_ComboBox control entirely - by writing my own multi-select combobox (which I believe will have a much smaller html footprint anyway). This means I can target my build entirely to asp.net 4.5.2, which I feel should fix the issue :) It's strange (and somewhat worrying) that visual studio allows you to build a website/application that "mixes different versions of asp.net" (even if they are in referenced dlls).
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: Thanks for your assistance in the matter :) I have decided to avoid the obout_ComboBox control entirely - by writing my own multi-select combobox (which I believe will have a much smaller html footprint anyway). This means I can target my build entirely to asp.net 4.5.2, which I feel should fix the issue :) It's strange (and somewhat worrying) that visual studio allows you to build a website/application that "mixes different versions of asp.net" (even if they are in referenced dlls).