Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Can't resume failed install of dotnet45 #500
I think that having something both depending on and conflicting with the same thing is a strange idea, and I've not seen it in other package managers. The current way it's done means that the installation of all dependencies must be completed successfully first try in one sitting. You cannot stop and pick up where you left off.
The reason I asked originally was because dotnet30 usually fails to install for me.
Here are the hurdles I've encountered trying to install dotnet45 this time, in chronological order:
After fixing these, the install succeeds.
If you are looking to fix the issues in dependencies rather than the conflict/depend situation, I think all it would take (at least for anyone having problems similar to mine) is to move the msxml3 dependency warning to the very start of the install process, and to turn on the virtual desktop while the installs are happening.
winetricks isn't a proper package manager, it's a shell script that makes
winetricks doesn't control those Microsoft installers, which is where the
Yes, it's unfortunate, but I don't see a practical solution to the issue
The conflicts stuff was added to avoid even more complicated issues with
On Sat, May 16, 2015 at 7:09 PM, Score_Under email@example.com
Thanks for your quick reply. Hmm, I started from scratch on a new wineprefix anyway. I tried
Man this is not fun - yes I have the same error
It seems to be a little erratic, for some reason it will not download the dotnet installer yet the download URL works.
All I get is the conflict error .I have reinstalled winetricks several times now same each time
Hi, can you try this? It's what eventually got it working for me:
I'd advise you to do everything from the terminal.
For each terminal that you want to work in, you must first point it to the correct wineprefix with the correct winearch. To do that:
export WINEPREFIX="$HOME/.wine32-dotnet" WINEARCH=win32
That will tell wine to work in a
From there you can do steps 2 to 4 and with a bit of luck it should work. You will need to use that wineprefix for whatever you're doing in .NET under wine, which means you'll need to run the command above before running your program too. I get around that hindrance on my local machine by creating a script which launches my program:
#!/bin/sh export WINEPREFIX="$HOME/.wine32-dotnet" WINEARCH=win32 exec wine /path/to/whatever.exe
Then I run that script instead of the exe file, which ensures it uses the right wine settings when it runs.