Installing .NET 4.0 requries deletion of all in .wine ?

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
spflanze
Level 1
Level 1
Posts: 9
Joined: Sat Jan 21, 2017 12:27 pm

Installing .NET 4.0 requries deletion of all in .wine ?

Post by spflanze »

I need .NET 4.0 to get Quicken working. I am looking at the instructions on page:
https://appdb.winehq.org/objectManager. ... &iId=17886

The given instruction sequence begins with the command:
rm -fr ~/.wine

Is it really necessary to do that? That commend would wipe out a lot of work I did installing programs and setting their configurations, and their data.
User avatar
dimesio
Moderator
Moderator
Posts: 13207
Joined: Tue Mar 25, 2008 10:30 pm

Re: Installing .NET 4.0 requries deletion of all in .wine ?

Post by dimesio »

Native .NET requires a clean wineprefix. If you have other things in the default wineprefix you want to keep, install .NET and Quicken to a separate one. https://wiki.winehq.org/FAQ#Can_I_store ... 2F.wine.3F
spflanze
Level 1
Level 1
Posts: 9
Joined: Sat Jan 21, 2017 12:27 pm

Re: Installing .NET 4.0 requries deletion of all in .wine ?

Post by spflanze »

What other such installations require a clean prefix?

Is it possible to upgrade .NET without starting again a clean prefix?
User avatar
dimesio
Moderator
Moderator
Posts: 13207
Joined: Tue Mar 25, 2008 10:30 pm

Re: Installing .NET 4.0 requries deletion of all in .wine ?

Post by dimesio »

A clean wineprefix is necessary for .NET apps. It is highly recommended for any apps that require winetricks or other tweaks to work, and if you haven't used one, it is the first thing to try if you run into problems. Many experienced users routinely keep everything in separate wineprefixes.

No, you can't upgrade .NET without a clean wineprefix. In addition, you need to install it with winetricks, as that will remove wine-mono and work around known bugs. Note also that 64 bit .NET doesn't yet work in Wine and 32 bit .NET has problems in 64 bit wineprefixes, so when you create the new wineprefix, make it a 32 bit one.
spflanze
Level 1
Level 1
Posts: 9
Joined: Sat Jan 21, 2017 12:27 pm

Re: Installing .NET 4.0 requries deletion of all in .wine ?

Post by spflanze »

I see a recent release of .NET 4.6.2 here:
https://appdb.winehq.org/objectManager. ... &iId=34702

And test results here:
https://appdb.winehq.org/objectManager. ... stribution

In the test results page does "amd64" in the header mean this .NET release was tested on a computer having a 64 bit architecture, and not necessarily that the testing was done in 64 bit wine prefix?

Will the installation instructions at:
https://appdb.winehq.org/objectManager. ... &iId=25478
work to install .NET 4.6.2 downloaded from:
http://repacks.net/forum/viewtopic.php?t=7
?
User avatar
dimesio
Moderator
Moderator
Posts: 13207
Joined: Tue Mar 25, 2008 10:30 pm

Re: Installing .NET 4.0 requries deletion of all in .wine ?

Post by dimesio »

"amd64" refers to the architecture of the operating system, not the wineprefix.

The recommended way to install .NET is with winetricks, which does more than just run the installer, but winetricks uses the official installers from Microsoft. According to https://appdb.winehq.org/objectManager. ... &iId=34702 the repack does run in Wine and there is a request to add it to winetricks (https://github.com/Winetricks/winetricks/pull/714), but it doesn't look like it's been done yet.
spflanze
Level 1
Level 1
Posts: 9
Joined: Sat Jan 21, 2017 12:27 pm

Re: Installing .NET 4.0 requries deletion of all in .wine ?

Post by spflanze »

It is convenient to use winetricks. But I need to do what I can so I will not have to create a new prefix for as long as possible. That means I need to install .NET 4.6.2 now. I cannot wait for it to be added to winetricks because I need Quicken working in my Ubuntu OS asap.
User avatar
dimesio
Moderator
Moderator
Posts: 13207
Joined: Tue Mar 25, 2008 10:30 pm

Re: Installing .NET 4.0 requries deletion of all in .wine ?

Post by dimesio »

spflanze wrote:But I need to do what I can so I will not have to create a new prefix for as long as possible.
I'm not really sure what you mean by this. You will have to create a new wineprefix for .NET apps whether you use winetricks or not.
Locked