There is a windows progam I'd like to use in wine. It currently doesn't work in Wine as it requires .NET 4.5.2. I'm worndering how difficult it would be to debug for someone who knows C programming? Would the debugging invlove debugging .NET 4.5.2 to run on Wine, debugging Wine to work with .NET 4.5.2, debugging the program to work with Mono, or something else? As far as I've been able to tell thus far, rundll32 is part of the problem. I'm not looking for a solution at this time, I just want an idea of how hard it is to debug programs requiring .NET 4.5.2. So, I can decide if it's worth it. I know the answer will be subjective and not really accurate. But a ballpark answer will help. I've seen other programs that have been made to work with Wine, I assume they took a little work and skill to get going. I don't currently know enough about the process to even guess how much work though.
I'd appriciate your thoughts.
How hard to debug?
Re: How hard to debug?
Debugging Wine starts with running your app in the latest development release of Wine and and looking at ordinary console output. In the case of .NET apps, start with wine-mono, and if there isn't already a bug filed for whatever doesn't work, file one. Then try the app with native .NET, and if that doesn't work and there are no bugs already filed, file one for that, too. Follow the instructions in the AppDB for installing .NET. https://appdb.winehq.org/objectManager. ... &iId=31023
