.Net Framework 4.0 Dependency about chocolateygui HOT 16 CLOSED

The installer is supposed to check if it is there. but a dependency would be nice.

from chocolateygui.

Okay, I will take a look at the package that Matt created for 4.5, and see what I can do.

from chocolateygui.

I don't believe a .Net 4.0 chocolatey package will get you very far because NuGet requires .Net 4 anyways. Or perhaps I'm misunderstanding your meaning.

from chocolateygui.

Ah, that is a very good point! I think you could be right.

from chocolateygui.

Take a look at http://boxstarter.codeplex.com/SourceControl/changeset/view/e467cbf71a5a#Bootstrapper/Check-Chocolatey.ps1 for an example of getting .net4.0 via webpi. On a .net 2 machine, you can install chocolatey but you cant successfully use it to install any nuget based packages. However, you can use its webpi provider to instal .net4.0 which never passes through nuget.exe and thus does not require .net4.0. Once webpi completes the install, then you can install any of the packages.

from chocolateygui.

Noice, thank you, this is just what we need!

from chocolateygui.

Just as an update on this...

As requested by Rob, I created a .Net Framework 4.0 choco package, which I believe he is going to be including (somehow) within the initial install of Chocolatey, which means that we shouldn't need to do anything for ChocolateyGUI, as it will already "always" be installed.

from chocolateygui.

I was gonna get to that last weekend but I'm thick into a major revamp of boxstarter that I really want to finish up. So sometime in the next couple weeks unless anyone beats me too it.

from chocolateygui.

Not a problem at all Matt. Do you know when the next version of Chocolatey is set to be released, and also which (if any) pull requests are going to be included? :-)

from chocolateygui.

Is this still relevant and open?

from chocolateygui.

Yes, this is still an issue. Now that there is a .Net 4.0 package, we could simply take a dependency on that, in the same way that others do. The only slight issue is that if you are not using Boxstarter (which handles the reboots), taking this package as a dependency can cause it's own issues.

from chocolateygui.

How so?

from chocolateygui.

When .Net 4.0 installs, it "sometimes" leave itself in a state where there is a pending reboot. Boxstarter catches this and does the reboot, and then carry on with the remainder of the installation. However, if you just try to install ChocolateyGUI directly after the .Net 4.0 package, things don't always go well, and you get a garbled error message. It doesn't happen all the time, but something we will need to watch out for.

from chocolateygui.

Eeek :<. Maybe add a helper check for pending reboots in the Choco installer that asks them to restart? Shrug

from chocolateygui.

Hmm, maybe, but I think that would be going against the grain of what Chocolatey is for. Chocolatey is the Package Manager, really specialising in installing/updating applications. The dependencies is a "nice to have", in my opinion. I would rather put together all the packages explicitly in a Boxstarter package, as shown here:

https://github.com/gep13/ChocolateyPackages/blob/master/gep13.BoxstarterDev/tools/ChocolateyInstall.ps1

And let Boxstarter do what it is good at. This is obviously a little harder to explain to people, but definitely pays for itself in the long run.

The above link is a Boxstarter Script for creating a Boxstarter Development Machine :-)

Gary

from chocolateygui.

Okay, looking again at the WiX package for ChocolateyGUI, it does the work of checking to make sure that the .Net Framework 4.0 is installed (that is even pointed out in the comments at the start of this thread). Since that is the case, and the .net 4.0 chocolatey package is not really meant to be used as a dependency, I think it is best to leave this as is.

from chocolateygui.