After a recent purchase (Apr 2013) of Resharper 7.1, although the VS IDE did not crash, The Visual Studio IDE Editor demonstrated strange behavior when refactoring code. My first instinct was to disable Reshaper refactoring since Visual Studio Ultimate has DevExpress installed and there might have been a conflict. From the Visual Studio IDE, I selected the Resharper\Options\ and a dialog displayed a message that Developer Express 7.1 was executing in Trial Mode. The dialog had "Trial Version" for a Serial Number.
I found this odd as I am running DevExpress 12.2.
I checked the Resharper installation directory and found DevExpress - 7.1 DLLs. I also noticed the DLLs had been altered in Jan 2013.
Apparently, the Resharper extension was distributed with DevExpress trial DLLs, I immediately uninstalled Resharper and a refund request in process.
Since uninstalling Resharper, the Visual Studio IDE crashes (with the typical message to generate a Microsoft Error Report). Visual Studio restarts.
I then uninstalled Visual Studio, DevExpress 12.2 (DX and CodeRush).
The environment still crashes...
I am posting this with hope that another developer might have a solution or can recommend steps to help me diagnose these crash events.
Thanks!
Tim Peer
Related
I keep seeing a progress bar at the bottom right of my Visual Studio 2015 environment that constantly appears each time I'm typing that says "Update background files". I've narrowed it down to being related to Resharper, but I can't figure out why this happens or how to turn it off! I've tried to clean all caches but it doesn't help.
The process is very slow and annoying. Anyone know how to stop this from happening? I'm using the latest version of Resharper v9.0.1 on Visual Studio 2015.
Thank you
ReSharper 9.0.1 does not support the latest builds of Visual Studio 2015 (AFAIK it supports first builds of VS2015 Preview). So you need to install at least ReSharper 9.2 to support VS2015 RTM or ReSharper 2016.2 to supports VS2015 Update 3.
[Update]
I understand I can use 2015 side by side with VS 2010, but we've had problems just polluting our environment. If there is a chance someone has done this, it could save me a lot of time and energy instead of going with an install only to find out it doesn't work. It's also unfortunate this isn't documented anywhere.
So just like the title says.
To give some more background we're hoping to use VS2015 with our testers to kick start using selenium, but our task/bug management is all on TFS2010.
I don't want to distort the testers' environment, neither can I play with any of our dev machines to try this out physically. A VM will just not really run on our, not so fast machines.
My google-fu didn't get me to far. The VS2015 Express features does mention TFS, but I want to know specifically if it supports TFS 2010. Additionally I found a MSDN page. This talks about the various VS and TFS versions but nothing here about VS Express
Related SO posts I found:
Visual Studio 2015 & TFS 2010 Not specific about VS express or not, no definitive answer
Visual Studio 2015 with TFS 2010 More unrelated, this is about builds going wrong
You should be able to run VS2010 and VS2015 side-by-side, but not on the same solution/project files.
Once you open an older project in 2015, a project conversion will happen. If I recall correctly, project compatibiliy started to stabilizer around VS2012, but don't quote me on that, I'd say it is not likely.
You will NOT be able to open the same project in both at the same time afaik, so it's a one-time shift that'd meet your needs.
As far as task tracking systems go, you could also opt in on VSTS and do a one-time export of your existing bugs/tasks. Shouldn't take you more than a day or so to plan and migrate those over.
You can open the project with VS2015 but it will be upgraded to a newer state. We recently done this and could not go back using VS2010. Otherwise you can version control and keep both projects, i.e. the old implementation and the upgraded one. You could try with VS2015 Community Edition.
You sure can run both versions side by side, but not on the same project. Also, the Microsoft Test Manager that comes with Visal Studio 2015 will not connect to TFS 2010. It tells you that it needs an older version of MTM. I am still working out the kinks on our systems.
I am having difficulty in installing Visual Studio 2015 Enterprise (Update 1). After installation completes, I get a warning saying "Not all features installed correctly". See below snip for details
In control panel programs list I found that VC++ 14.0.23506 (both x64 and x86) are installed.
I am able to open visual studio, but when I try to create a new project I get following error regrading c# compiler error
I know performing a clean install again is a solution, but I have poor internet speed and would like to avoid downloading the whole thing again. Any help in fixing this would be great.
PS: I have VS 2013 professional and VS 2012 express also installed, both of which are working fine
Try uninstalling Visual Studio 2015, those VC++ 2015 x86 and x64 runtimes, and reinstalling Visual Studio 2015. Looks like it didn't finish installing properly because you already had the runtimes installed.
This question already has answers here:
Multiple Errors Installing Visual Studio 2015 Community Edition
(23 answers)
Closed 6 years ago.
I was trying to install visual studio 2015 community edition on my system using the downloaded ISO file. There occurred an error showing the installation failed. The error was like:
team explorer for visual studio 2015
fatal error during installation
I have compared the SHA-1 hash value of my downloaded iso file with one provided at microsoft site. They are correct and matching. I have tried all possibilities including reinstall, repair etc. Still not working.
PS: I have already installed visual studio 2008 on my system and its working properly.
Answer from another question asked on stackoverflow, source:
Multiple Errors Installing Visual Studio 2015 Community Edition
I spent a whole week trying to solve this issue.
What finally did it for me was disabling my anti-virus programs.
Before I stumbled upon my solution, I went through a lot of other solutions. I
thought, I'd post some of the solutions that might prove to be useful for those who are still having trouble with installing Visual Studios 2015 Community Edition.
Solution 1: Minimal Installation
Try installing with minimal extra features. Run the Visual Studios 2015 installation, then click "Custom" and on the following screen, uncheck everything and proceed with the installation.
Solution 2: Delete installation cache
Perhaps the installation failed due to corrupt files in the cache. When installation fails, remove all Visual Studio cache related items and do a full re-installation. To do this, run command prompt (Run as Administrator) and type: "cd /programdata/package cache/" then press enter. Then type "del /f /s *.msi /f /s *.cab" then press enter.
Now run the Visual Studios 2015 installation again.
Solution 3: Delete temporary file data stored on your computer
Open up File Explorer and go to "C:\Users\[Your User Account Name]\AppData\Local\Microsoft". Then delete the following folders: VSCommon, VisualStudio, Blend, VsGraphics, ApplicationInsights, vshub, Team Foundation, Web Platform Installer and MsBuild. After this, run the Visual Studios 2015 Installer again.
Solution 4: Enable all four evaluations of Symbolic links
First, check to see if all four evaluations are enabled. Open up command prompt (Run as Administrator) and type "fsutil behavior query SymlinkEvaluation". All 4 evaluations should be enabled. If they aren't then type "fsutil behavior set SymlinkEvaluation L2L:1 R2R:1 L2R:1 R2L:1". Once those 4 evaluations are set, clear up temporary files and clear installation cache (see Solution 2 and Solution 3) then run the Visual Studios 2015 installation again.
Solution 5: Repair the Redistributables
Perhaps, the problem is that your VC-redistributables are faulty and are in need of repair. To do so, run "Add/Remove programs" and look for all the x86 and x64 versions of Microsoft Visual C++ [Year] Redistributable (Version). Then press Change for each of them and when the uninstallation screen pops up, press Repair. I did it for all the versions I had previously installed: 2012, 2013 and 2015. Therefore, I repaired 6 of them: 2012: x86 and x64, 2013: x86 and x64, 2015: x86 and x64.
Solution 6: Check to see if x86 and x64 sizes are the same
As mentioned by others in this discussion, do a search for vcruntime140.dll and see if the x86 and x64 versions. They should NOT have the same size. If they do, see solution 5 or you can manually delete them (** Be cautious when deleting files from the Windows folder!) and re-install them (from here: https://www.microsoft.com/en-ca/download/details.aspx?id=48145). Also do the same check for msvcp140.dll. I personally did a search for these files in "C:\Windows\SysWOW64 and C:\Windows\System32" and compared the files from the two folders. Moreover I also checked for differences of vcruntime140.dll and msvcp140.dll in "C:\Program Files\Microsoft Visual Studio 14.0" and "C:\Program Files (x86)\Microsoft Visual Studio 14.0"
Solution 7: Temporarily disable all Anti-Virus Protection and Firewalls
For me, it turned out that the problem stemmed from having ByteFence Anti-Malware and Norton Security with Backup protection. I disabled real-time protection from ByteFence Anti-Malware and I disabled Auto-Protect and Smart Firewall from Norton Security with Backup. Before I ran the installation again, I repeated Solution 2 and Solution 3 (scroll up). And Voila, installation was successful. But how did I find out that the Anti-Virus Program was the culprit? Read Solution 8.
Solution 8: Carefully monitor Visual Studios Installation Process for Intrusions
I resorted to this solution in order to find out the problem. After reading Ezh's article, I decided to download Process Monitor v3.2 and Process Explorer v16.1. I was carefully monitoring 3 programs side-by-side: Process Monitor, Process Explorer and the Visual Studios 2015 Installer, and I watched very closely all the processes that the installer was invoking. Then I noticed that when VSIXInstaller.exe process came on and attempted to install something from a remote server, it kept failing over and over again because my Anti-Virus Program would suddenly appear on screen (as a process) and decide to hog/block some important DLL files that VSIX installation needed. Temporarily disabling the anti-virus program solved my issue!
Solution 9: Complete Windows format and re-installation
If all else fails, and you are really desperate to get Visual Studios 2015 working, I suggest a complete Windows re-installation. At this point, the problem is most likely some type of interference/intrusion with a program which you do not know of.
After a tough day of reinstalling and uninstalling of VS2015 again and again (both Professional and Enterprise, both with updates and without) on Windows 10 nothing seemed to help. Finally this approach worked:
Uninstall the crashing version of VS2015 completely
Uninstall C++ 2015 Redistributables - both x64 and x86 version
Restart the computer
Manually delete remaining dlls from both system32 and SysWOW64 system folders (their names end with *140.dll - but be careful and do a backup!)
Download "Microsoft Visual C++ 2015 Redistributable Update 3" from here - https://www.microsoft.com/en-us/download/confirmation.aspx?id=53840 - both x64 and x86 version
Install the "Microsoft Visual C++ 2015 Redistributable Update 3" - both x64 and x86 version
Restart the computer if needed
And finally - Install the VS 2015
Working!
I 've tried all the workarounds that are in "Mai Benanami" answer without success and what finally do the trick was to uninstall all visual studios and all Microsoft Visual C++ XXX Redistributable x86 and x64 versions.
Then, run the Visual Stuido installer again.
Hope it helps!
What C# compiler does Visual Studio 2013 use? If I were to install Visual Studio 2015 with its new Roslyn compiler, would that affect my Visual Studio 2013 installation?
I ask because we have some tests that are known to fail when our code is built with Visual Studio 2015. Some numbers differ at the eight significant figure. The solution when Visual Studio 2015 is released will probably be to increase the tolerances on the tests, but I'd like to understand how Visual Studio decides which compiler to use.
Can Visual Studio 2013 be explicitly set to use the old compiler? Or an msbuild script?
What C# compiler does Visual Studio 2013 use? If I were to install
Visual Studio 2015 with its new Roslyn compiler, would that affect my
Visual Studio 2013 installation?
Installing Visual Studio 2015 Preview will not affect your Visual Studio 2013 installation, and the old C# and VB compilers that live in .NET Framework installation folder within the Windows directory are not replaced. Instead, Visual Studio 2015 Preview uses and includes a preview of the next version of the Microsoft Build Tools, MSBuild 14.0, that is installed in the 32-bit Program Files folder under \MSBuild\14.0 and contains the new Roslyn compilers and code analysis libraries.
For C++, nothing substantial has changed, and as the compilers live in the \VC\bin subfolder of the particular Visual Studio installation, they will not affect each other.
Can Visual Studio 2013 be explicitly set to use the old compiler? Or
an msbuild script?
It's not necessary since Visual Studio 2013 can only use the old compilers, unless you installed and enabled the Roslyn CTP extension which has become obsolete by now.
No. Installing Visual Studio 2015 doesn't change the compiler used by VS 2013. At the command line, you can choose between by running the corresponding msbuild.exe
The test failures were due to .NET Framework 4.6 , rather than a change in compiler.
Fixed the problem by setting the 'use legacy JIT' environment COMPLUS_useLegacyJit variable per https://github.com/Microsoft/dotnet/blob/master/docs/testing-with-ryujit.md
Installing VS2015 will replace the .NET Runtime and update it to 4.5.3 - I don't know whether the JIT compiler is replaced, but it is possible.
In this case you could observe differing test results regardless of which C# compiler was used.
Anyways, installing 4.5.3 runtime is a major change to the machine and can't live side-by-side with non-preview runtimes so I'd not recommend it on a production machine. For example the Debugger API from Microsoft, CLRMD (Microsoft.Diagnostics.Runtime nuget package) no longer can connect to a 4.5.3 runtime - it's been reported here for example.
I would assume there are more breaking changes to be discovered.
Maybe VS 2015 does not affect the compiler used by VS 2013, but it definitely affects Roslyn (if you install VS 2015 your old, pre-VS2015 Roslyn code could stop working). For me it introduced problems with compiling anonymous types in ConfigR scripts.
I faced the issue by installing VS Professional 2015 Release side by side VS professional 2012. My MVC 3 Project created in VS 2012/ .net 4.0 I am not able to open now. I am able to open it in VS 2015/ .Net 4.0 only.