Looking for good techniques to justify "great than normal" machine for developers. The company I work for buys the same underpowered $500 dollar systems for everyone, and looking for ways to prove ROI or arguments to use. Sorry, I didn't say this in the initial question, the stack is VS 2008, SQL 2005/2008. As duties dictate we are SQL admins as well as Web/Winform/WebService Developers. So its very typical to have 2 VS sessions and at least one SQL session open at the same time.
- R – Visual Studio – rewrite / lifespan
- R – Proving that replacing hardware will improve developer performance
- C# – Tools for Building an OCA (Occasionally Connected Application)
- C# – No connection could be made because the target machine actively refused it
- .net – PowerShell script to return versions of .NET Framework on a machine
- .net – ‘Microsoft.ACE.OLEDB.12.0’ provider is not registered on the local machine
- Visual-studio – Where is Developer Command Prompt for VS2013