You're only licensed to redistribute dotnetfx.exe, there is no MSI. Short story: MSFT wants only one redistributable; to support targets that don't have MSI 3 installed it's not an MSI.
See http://msdn2.microsoft.com/en-us/library/aa480242.aspx for details on redistribution outside of Visual Studio setup project. See http://msdn2.microsoft.com/en-us/library/aa480239.aspx for what appears to be details on getting your Visual Studio setup to deploy dotnetfx.exe. You could add a step to your setup that executes dotnetfx.exe silently and might be able to remove the .NET prerequisites from your setup, if the prerequisites is an issue. On Wed, 2 Apr 2008 08:15:15 -0400, Simon Robinson <[EMAIL PROTECTED]> wrote: >Does anyone know if there's a way to use a Visual Studio setup project to >package the .NET 2.0 framework into an MSI? > >.NET 2.0 comes as a .exe but our network admins are insisting they want it >as a .msi (so that they can use group policy to push it out to all our >servers). > >I've using a VS setup project, with various combinations of explicitly >telling it to add the .NET framework as a prerequisite, even adding a >dummy .NET 2.0 application that we won't ever use, but which forces Visual >Studio to auto-detect that the project requires .NET 2.0. But what I >always find is that either VS puts .NET 2.0 into a separate setup.exe, or >creates the msi that just tells the user to manually go install the .NET >Framework! We could really do with an msi that automatically installs >the .NET framework if required. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
