4 ms·

Not happy at all! I love the old Visual Studio 6.0 IDE, the new devenv.exe is getting more slower after each version. Go back to native,Microsoft!

pjmlp 10y ago
They did. "Getting Started with .NET Native" - https://msdn.microsoft.com/en-us/library/dn600165%28v=vs.110%29.aspx https://msdn.microsoft.com/en-us/library/dn600165%28v=vs.110...
- piyush_soni 10y ago
  I think the parent comment meant Visual Studio is slowing down with each new release (they switched to WPF for developing it with VS 2010).
  - pjmlp 10y ago
    I got it, but given that VS is still way faster than any Java IDE I have to use on my hardware, specially Android Studio, I just made that snarky remark. Also I doubt very much that we could have had Rosyln with VC 6.0 architecture, stuck in C++ and COM.
tonyedgecombe 10y ago
It's certainly slow at starting up, beyond that I haven't seen a problem.
mikerg87 10y ago
I'm not sure native is the way forward but I agree that Visual Studio is starting to show its warts. The 2GB memory limit is starting to be a problem for more and more of us. On a long enough timeline I hope to see VS code replace Visual studio
frik 10y ago
Me too VS 6 and VB 6 were really awesome. Microsoft was at the tipping point in 1999, then the dotNet thing happened and a lot of failures like dotNet based Shell/Explorer and WinFS for the failed Longhorn what turned into WinVista. Then the WinMobile 6.5 to 7 thing happened. The dotNet Framework seems to be legacy now - right? WinForms is legacy now. Silverlight is legacy. dotNet DirectX APIs are legacy. dotNetCore is the new thing, but in v1. UniversalApp based on C++ API seems to replace WinAPI - correct? Anyway WinAPI is still going strong, and almost all applications are WinAPI based. Sometimes I would like to go back in time to 1998/99. But the good thing the WWW succeeded (and "The Microsoft Network" failed and original dotNet vision of software as a service got postponed by many years).
mlsarecmg 10y ago
Visual Studio is on WPF, so you can forget it. WPF is an abandoned platform. It is a wonder they're still trying though, even their web-based IDE (VS-code) is faster.
- pjmlp 10y ago
  Funny, just a few months ago WPF got a few updates in VS 2015, WPF blog was reactivated and BUILD had a few sessions on it. I have been doing greenfield WPF applications for companies in the life sciences industry in the last three years, and they will not move away from it any time soon.

pjmlp 10y ago

They did. "Getting Started with .NET Native" - https://msdn.microsoft.com/en-us/library/dn600165%28v=vs.110%29.aspx https://msdn.microsoft.com/en-us/library/dn600165%28v=vs.110...

piyush_soni 10y ago
I think the parent comment meant Visual Studio is slowing down with each new release (they switched to WPF for developing it with VS 2010).
- pjmlp 10y ago
  I got it, but given that VS is still way faster than any Java IDE I have to use on my hardware, specially Android Studio, I just made that snarky remark. Also I doubt very much that we could have had Rosyln with VC 6.0 architecture, stuck in C++ and COM.

tonyedgecombe 10y ago

It's certainly slow at starting up, beyond that I haven't seen a problem.

mikerg87 10y ago

I'm not sure native is the way forward but I agree that Visual Studio is starting to show its warts. The 2GB memory limit is starting to be a problem for more and more of us. On a long enough timeline I hope to see VS code replace Visual studio

frik 10y ago

Me too VS 6 and VB 6 were really awesome. Microsoft was at the tipping point in 1999, then the dotNet thing happened and a lot of failures like dotNet based Shell/Explorer and WinFS for the failed Longhorn what turned into WinVista. Then the WinMobile 6.5 to 7 thing happened. The dotNet Framework seems to be legacy now - right? WinForms is legacy now. Silverlight is legacy. dotNet DirectX APIs are legacy. dotNetCore is the new thing, but in v1. UniversalApp based on C++ API seems to replace WinAPI - correct? Anyway WinAPI is still going strong, and almost all applications are WinAPI based. Sometimes I would like to go back in time to 1998/99. But the good thing the WWW succeeded (and "The Microsoft Network" failed and original dotNet vision of software as a service got postponed by many years).

mlsarecmg 10y ago

Visual Studio is on WPF, so you can forget it. WPF is an abandoned platform. It is a wonder they're still trying though, even their web-based IDE (VS-code) is faster.

pjmlp 10y ago
Funny, just a few months ago WPF got a few updates in VS 2015, WPF blog was reactivated and BUILD had a few sessions on it. I have been doing greenfield WPF applications for companies in the life sciences industry in the last three years, and they will not move away from it any time soon.