Including dotnetfx.exe in deployment project
-
Upon first pass it appears as thought the dotnet framework is no longer embedded and automatically deployed with VS.NET microsoft installer deployment projects as it was in Release Candidate 1. I was hoping not to have the user have to run the dotnetfx.exe redistributable separately before they could install the .NET application I have written. When I compile a deployment project I get the warning: "This setup does not contain the .NET Framework which must be installed on the target machine by running dotnetfx.exe before this setup will install. You can find dotnetfx.exe on the Visual Studio .NET 'Windows Components Update' media. Dotnetfx can be redistributed with your setup." Does any know a way to have the dotnetfx.exe automatically run when a new .NET application is being installed? Any ideas on other options? Kyle
-
Upon first pass it appears as thought the dotnet framework is no longer embedded and automatically deployed with VS.NET microsoft installer deployment projects as it was in Release Candidate 1. I was hoping not to have the user have to run the dotnetfx.exe redistributable separately before they could install the .NET application I have written. When I compile a deployment project I get the warning: "This setup does not contain the .NET Framework which must be installed on the target machine by running dotnetfx.exe before this setup will install. You can find dotnetfx.exe on the Visual Studio .NET 'Windows Components Update' media. Dotnetfx can be redistributed with your setup." Does any know a way to have the dotnetfx.exe automatically run when a new .NET application is being installed? Any ideas on other options? Kyle
Thomas Scheidegger had this to say about it on the DOTNET mailing list.
MS did a last-minute change in deployment strategy! .NET Framework Deployment Guide: [http://msdn.microsoft.com/library/en-us/dnnetdep/html/dotnetframedepguid.asp](http://msdn.microsoft.com/library/en-us/dnnetdep/html/dotnetframedepguid.asp) and in special for VS.NET and .msm: [http://msdn.microsoft.com/library/en-us/dnnetdep/html/vsredistdeploy.asp](http://msdn.microsoft.com/library/en-us/dnnetdep/html/vsredistdeploy.asp) the solution seems to be a 'Bootstrapper' hack..... ThomasJames Sonork ID: 100.11138 - Hasaki "Not be to confused with 'The VD Project'. Which would be a very bad pr0n flick. :-D" - Michael P Butler Jan. 18, 2002 -
Thomas Scheidegger had this to say about it on the DOTNET mailing list.
MS did a last-minute change in deployment strategy! .NET Framework Deployment Guide: [http://msdn.microsoft.com/library/en-us/dnnetdep/html/dotnetframedepguid.asp](http://msdn.microsoft.com/library/en-us/dnnetdep/html/dotnetframedepguid.asp) and in special for VS.NET and .msm: [http://msdn.microsoft.com/library/en-us/dnnetdep/html/vsredistdeploy.asp](http://msdn.microsoft.com/library/en-us/dnnetdep/html/vsredistdeploy.asp) the solution seems to be a 'Bootstrapper' hack..... ThomasJames Sonork ID: 100.11138 - Hasaki "Not be to confused with 'The VD Project'. Which would be a very bad pr0n flick. :-D" - Michael P Butler Jan. 18, 2002