Force use of original .Net 4.0 when .Net 4.5 is installed about nant HOT 2 OPEN

From my point of view we should check if we can use this new reference assemblies folder in nant.exe.config. I expect that this would ease the configuration a little. And since we require a proper SDK installed on the machine I think we can expect that these folders are present.

from nant.

I have followed the advice on the SO topic I linked to, and it appears to do what I want. However, vbc needs to be handled differently:

For the Visual Basic compiler, the noconfig/nostdlib flags behave differently, and notably they will not prevent linking with some standard libraries. Luckily MS realized this problem and added the /sdkpath argument that should be used instead. With nant, I solved it by adding this inside the vbc task:

<arg line="/sdkpath:&quot;${environment::get-folder-path('ProgramFiles')}\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0&quot;"/>

I hope this can be resolved in a way so (at most) only changes to the project specific build file is necessary to enable this behavior. I.e. so that a nant user need not edit nant.exe.config. Perhaps using the reference assemblies should be the default for nant, which I think can be accomplished if the csc task would always apply the noconfig/nostdlib arguments, coupled with nant automatically adding references to mscorlib and some others (unless the build script itself has given the nostdlib argument to the csc task). Conversely, for vbc, nant should always apply the /sdkpath argument, unless the build script itself has given the sdkpath argument explicitly.

from nant.