With 1.7 million freelancers, we'll match you with the perfect talent.
The client has made the following changes to the job.
Client prefers freelancers from:
You are still able to submit a proposal for this job.
The client prefers freelancers from
a different location.
We have Visual Studio 2010 setup and deployment project that needs improvement. This is for an IE BHO that we developed. The project has a .NET 4.0 dependency and we'd like to change the order in which .NET gets installed. Currently our installer launches setup.exe, which then immediately proceeds with calling the .NET 4.0 installer (located @ DotNetFX40/dotNetFx40_Full_x86_x64.exe inside our installer).
We're wondering if there's any way to make this process more intuitive where our installer shows up first and then kicks of the .NET installation.
So the desired flow is:
User launches installer
User gets a EULA Screen
User selects installation directory
Then .NET 4.0 Installer is Called
.NET 4.0 is installed
Then Our Application is Installed
Note: We bundle the entire .NET 4.0 installer file (50 MB) into our project because the Web client version takes too long to finish -- however, we are open to changing this.
Sign in or Register to see more