I'm using Visual Studio 2015 in the community version.
Today I saw that since some days there is an update to Version "Update 1". I was wondering, that my windows or visual stuido did not tell me that there is a update available.
Is this normal in VS, do I always have to keep it up to date by downloading the newest installer?
The reason you didn't see it is that VS has two actions. The first is that we publish a VSUpdate for people to find and download directly. After a period of time, then we publish an atom feed file that VS will download and use to notify you. What you were seeing is that we made VSU1 available on Nov 30th, but we didn't publish the atom feed file until Dec 14th. (And even then, VS only fetches the updated atom feed file once every 24 hours, so it could have been Dec 15th when your VS would have gotten the file that caused the notification).
Keeping up-to-date manually by keeping an eye on tech blogs is faster than waiting for Visual Studio to inform you.
You can find the update on MSDN and download it there, or use the link in this Microsoft Blog post on the release of VS2015 Update 1 to download it.
Update:
This morning my Visual Studio Professional 2015 suddenly drew a yellow box around the Notification Center icon, and upon clicking it told me that '"Visual Studio 2015 Update 1" is available'.
Related
Trying to install 'Visual Studio 2015 with Update 3' using the .exe installer provided for the visualstudio.com website. I also tried the standard version (without the update).
The black/grey installer opens, the green bar moves along the progress bar once and it crashes. I get a white pop-up window saying 'Microsoft Visual Studio Community with Updates has stopped working'.
I can't seem to find any other situations like mine on Google or StackOverflow.
I have Visual Studio 2017 also installed. Why do I need 2015 too? I'm helping (trying) another student who is using VS2015 and has problems - however, I can't even get it downloaded!
Thanks in advance for any help.
One possible solution is to not worry about 2015 and just help him by using 2017. It's hard to tell for sure if this will resolve your issue, as there is not info on exactly what you are trying to help him with.
If you go this route, I would save out the solution file just after loading it with _vs2017 tacked on the end, or something similar, so that you do not overwrite the info in his solution file. (Edit: The purpose of this is just in case it breaks something for him - it may not be a problem, he may be able to load your 2017 solution file fine). I've moved fluidly between 2017 Community and 2015 Express or Community with some solutions without a problem.
I do realize there are some issues that this may not be a solution for, but it should be an option, especially for those that are more language-based. The main problems with this solution would be if other student is using features or libraries that are deprecated in 2017, or directly struggling with getting VS 2015 features to work.
Go to control Panel -> Programs and features -> turn on windows features ,
Disable .net 3.5
check for windows update,
Then restart the system. Now it will work . 100% working .
Have fun.
After Windows 10 auto installed the Anniversary Update, along with installing Visual Studio 2015 Update 3 (using Visual Studio Enterprise Edition), any time I try to use the Find in Files, or Replace in Files window has a scrambled UI, and no am unable to click / use any of the controls.
I have attached screen shots of the Find in Files, Replace in Files for reference purposes.
Any ideas on how to fix it. Never realized how much I depended on the Find in Files tool until it's been taken away from me!
The issue seems to have fixed itself with the Oct 12 windows update. From looking at the descriptions of the 'Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3194798)'. Unable to duplicate this issue anymore
Sorry for dupplicate.
I installed VS 2013 with Update 3 on disk E. By using a software, I merged disk D and E to one partition. And the data was lost.
But, i restarted my pc, i could still uninstalled some software. VS 2013 is not one of them.
VS said that it needs a source to complete. I can't provide it. Nothing in disk E, it includes VS 2013 source.
After that. I linked to visualstudio.com and download new version. It's VS 2013 with Update 4.
I downloaded iso file, and burned to my usb.
When running as administrator, it shows me 1 error and many warning. Like this:
The form specified for the subject is not one supported or known by the specified trust provider.
The installer was stopped.
I had referenced many relate, some ideas are:
-- Uninstall VS 2013 Update 3. Restart and try to install VS Update 4. I can't do this.
-- Read this link: Visual Studio 2013 Setup: common issues and workarounds. I read and... still didn't see any solution to solve my trouble. The installer didn't tell me "Why" or give me any error code about the problem.
So, my problem is:
I have VS 2013 with Update 3 on my system, and the source was lost. I can't uninstall it.
I want to install new VS 2013 with Update 4 within Update 3. But I don't know how to do that.
Can you give me any solution?
Thanks so much!
I don't understand what is meant by "I want to install new VS 2013 with Update 4 within Update 3". However, I can provide you the steps to uninstall an update of VS 2013.
Go to Control Panel->Programs->Programs and Features.
Now on the left you will see View installed updates on the top left of the side bar as shown below.
Now under VS 2013, you should be able to see all the updates. Right click an update and click Uninstall.
Good Luck!
I am trying for last two days to download VS 2013 SP 1 update. I succeed to download only "VS2013.1" (1,165kb) application and when trying to start it its only shows for milliseconds VS 2013 black update screen and close. I downloaded from external link and also through VS Notification.
Any solution for this problem ?
I found solution! NOD ESET Smart Security was producing this issue. I disabled it for 10 min. and download started as usual.
For a couple of weeks now I have been unable to merge Views within Visual Studio 2013 in response to conflicts when getting Source Code from Visual Studio Team Services. I am sure I used to be able to this (we recently moved from Visual Studio Professional 2012 so I cannot be one hundred percent certain - automerging may have been sufficient in the early days of the project).
The "Accept Merge" and move to next change/conflict buttons are all greyed out and inoperable. See screenshot snippet-
This originally only happened with Views, but now seems to affect some other classes. Changes are highlighted and indicated on the scroll bar so the diff tool otherwise appears to be functioning. This only originally affected me, but now affects a new colleague into the team.
I can still either Keep Local Version or Take Server Version but this is rarely sufficient. This leaves me manually altering the local copy to apply changes highlighted by the merge tool. (Edit - See a better workaround in "Second Update" below).
Has anyone come across this before?
Visual Studio 2013 Premium (patch RTM/Update 1/Update 2 - all with the same problem), with Resharper 8.2 (originally 8.0.2) C# and Web Essentials installed. Running on Windows 7 Professional x64.
Project is ASP.NET 4.5 using MVC 5.1.2 (now additionally updated from MVC 5 where the problem first occurred) (upgraded from MVC 4 following the upgrade instructions on the ASP.NET website) in C#, using latest versions of Razor (3.1.2) and Entity Framework (6.1.0 RTM).
Edit: Initially a repair install of Visual Studio 2013 appeared to have fixed the issue. It has now however returned exactly as it was before. Since it took an hour to do the repair I cannot repeatedly do this in order to merge views. I am currently able to round trip the solution between Visual Studio 2012 Update 4 and Visual Studio 2013 in order to do merges in Visual Studio 2012 where it is working normally.
Second Edit: I am currently manually resolving conflicts by selecting the desired code (local/server), saving the merge window and then closing it which will prompt to accept the merge result. This seems to function but is obviously sub-optimal. It may however be helpful for other users.
In the event, installing Resharper 8.1 on top of 8.02 appears to have fixed it fixed it briefly before the problem returned yet again. I had previously completed a repair install of Visual Studio Premium 2013 as well - which briefly seemed to have fixed it before it broke again. I only mention it in case the fix is cumulative.
I am unclear if it was a bug in Resharper that was somehow preventing the merge, or a persistent problem with the installation that the upgrade cleaned up (Resharper removes previous versions and then installs updates, rather than attempting to install over the top). Update - I am extremely confident that this is not related to ReSharper and that it was the configuration of Visual Studio as a result of re-installing the extension and not the extension itself that fixed the issue.
In either case, the issue (for now) seems to have disappeared and this seems to be related to the upgrade, or is an extremely strong co-incidence.
Colleagues with the same versions of Visual Studio and Resharper, working on the same project, the same version of Windows and (in one case) the same hardware were not affected, so it seems likely it is an edge case niche issue caused by corrupted data somewhere.
I have a current working theory that this is related to different patch versions of Visual Studio (for example Visual Studio 2012 Update 2, Visual Studio 2013 RTM, Visual Studio 2013 Update 1, Visual Studio 2013 Update 2. This only affects Visual Studio 2013 for us.
Simple solution I use is carry on with your manual merge process once you are done simply Close the Merge-* tab (the one you are using to merge files) this will bring up a prompt for confirming if you want to Save the changes made (this is the merge changes you made to your local file) click 'yes' Now it comes back to Resolve Conflicts tab and brings up another prompt asking if you want to Accept Merge Result, click 'yes'(this is same as the button Accept Merge)
Since you have VS2012 installed and merge is working there, you can create a link to its TF.exe in VS2013, similar to one on the picture below, and fix the issues there. Set Command to c:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\TF.exe and Arguments to resolve.
You do that in Tools->External Tools.