fernandocarvalho <wineforum-user@xxxxxxxxxx> wrote: > >Then, for the next release of wine, we could make sure that every new wine release, is >capable of running Visual Studio. Give us a real good compelling reason why this should be so. We are busy enough with trying to make 3,000 games and office applictions run (or more.) There are things in VS that will never work with Wine and that's just fine. We are trying to get MingWin to work and Cygwin to work as well. This will allow for building of Windows executibles from Linux/UNIX and to run them in Windows. That would be considered a massive step forward. >So we can maintain a certain compliance with key features of windows. That's why we concentrate on applications over a broad spectrum. >If Visual Studio starts working in a good shape, we can be sure that many applications >will also work, because a great portion of them are build using Visual Studio. It won't and never will. Applications use .NET and other 'features' of Windows as well. The goal should be: 1. Get legacy applications to work in Wine as they do in Windows. 2. Get current applications to work in Wine as they do in Windows. 3. Get cygwin/mingwin to build Windows applications in UNIX/Linux. 4. Get Visual Studio to work in Wine. The first is mainly done. The second is where a lot of the messages in this forum come from. The third is a purely developer issue. The fourth may or may not happen as time goes along. Remember, we are following the Microsoft path and they have been known to throw a wrench into the works on a regular basis. And yes, I've been at this since the introduction of Windows95 to get Win32s applications to run on OS/2 (Project Odinn...) James McKenzie
