Force use of original .Net 4.0 when .Net 4.5 is installed
Oskar Berggren <[email protected]> Sat, 27 Oct 2012 19:57:05 +0200
| Newsgroups | gmane.comp.windows.dotnet.nant.devel |
|---|---|
| Message-ID | <CAHOuc7NZcdn6hwAbUG7o7-v3uBzKwKDCAEHMa2jcWeW0ak6j7g@mail.gmail.com> |
--===============0903125874242864826== Content-Type: multipart/alternative; boundary=e89a8f6471d142f97004cd0e2bba --e89a8f6471d142f97004cd0e2bba Content-Type: text/plain; charset=ISO-8859-1 Hi, .Net 4.5 is an inplace upgrade for .Net 4.0. If you want to ensure that your software runs on a machine with only the original .Net 4.0 installed, you need to take care when building, so that you don't cause dependencies on .Net 4.5 versions of the assemblies. This thread discuss the issue and there is a proposed solution that involves editing nant.exe.config to avoid referencing updated assemblies found under C:\Windows\...: http://stackoverflow.com/questions/11991383/nant-build-using-net-4-5-beta-assembly-references-despite-specifying-net-4-0 What are the nant developers' take on this? Is the solution on stack overflow the way to go? If so, should this be regarded as a bug in nant? It doesn't seem "proper" to edit nant.exe.config in a runtime installation. /Oskar --e89a8f6471d142f97004cd0e2bba Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,<br><br>.Net 4.5 is an inplace upgrade for .Net 4.0. If you want to ensu= re that your software runs on a machine with only the original .Net 4.0 ins= talled, you need to take care when building, so that you don't cause de= pendencies on .Net 4.5 versions of the assemblies.<br> <br>This thread discuss the issue and there is a proposed solution that inv= olves editing nant.exe.config to avoid referencing updated assemblies found= under C:\Windows\...:<br><a href=3D"http://stackoverflow.com/questions/119= 91383/nant-build-using-net-4-5-beta-assembly-references-despite-specifying-= net-4-0">http://stackoverflow.com/questions/11991383/nant-build-using-net-4= -5-beta-assembly-references-despite-specifying-net-4-0</a><br> <br>What are the nant developers' take on this? Is the solution on stac= k overflow the way to go? If so, should this be regarded as a bug in nant? = It doesn't seem "proper" to edit nant.exe.config in a runtime= installation.<br> <br><br>/Oskar<br><br> --e89a8f6471d142f97004cd0e2bba-- --===============0903125874242864826== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ WINDOWS 8 is here. Millions of people. Your app in 30 days. Visit The Windows 8 Center at Sourceforge for all your go to resources. http://windows8center.sourceforge.net/ join-generation-app-and-make-money-coding-fast/ --===============0903125874242864826== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ nant-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nant-developers --===============0903125874242864826==--