Visual Studio 2013 Update 1
This morning we made available the final version of Update 1 for Visual Studio 2013. This is a targeted update, addressing some key areas of customer feedback since the Visual Studio 2013 release. For example, we heard your feedback about running Visual Studio in environments without IE10+, and have made several improvements to this experience in Update 1. Full details of the changes are available here. Download the update now or wait to get it through Visual Studio update notification in the coming weeks.
This update arrives as we finish up a great wave of Visual Studio 2013 launch events. Two million developers watched the Visual Studio launch videos online, and tens of thousands joined in person at events around the world. Video overviews of all areas of Visual Studio 2013, .NET 4.5.1, Team Foundation Server 2013 and Visual Studio Online are available now on the Visual Studio Channel on YouTube.
The team was also honored to have Visual Studio 2013 recognized as an InfoWorld 2014 Technology of the Year Award winner last week.
Today's release of Update 1 continues our commitment to delivering regular updates for Visual Studio. We're well underway on Update 2 now, our first major feature update, which we are looking forward to delivering this spring.
Namaste!
Comments
Anonymous
January 20, 2014
Shukriyaa!Anonymous
January 20, 2014
> This is a targeted update, addressing some key areas of customer feedback since the Visual Studio 2013 release. Are you saying you fixed the GUI and brought back setup and deployment projects?Anonymous
January 20, 2014
Has search by wildcard made its way back that's what I want to knowAnonymous
January 21, 2014
I only update with an update that includes Setup & Deployment, Windows Forms and WPF improvements and fix the user interface and icons.Anonymous
January 21, 2014
Awesome , thanks so muchAnonymous
January 21, 2014
Add a file to project, then delete that file but not in the project. Sometimes, when intellisense fails to update in time, the navigate popup (ctrl+,) can list this false file. If you try to open this file from navigator, the navigator will go into bug state and remains on screen , unable to close, unable to navigate into any file. It seems like some internal exception is not caught. This problem is especially bad with large c++ project. I turned off the navigator preview option, if that matters.Anonymous
January 21, 2014
Get well soon!Anonymous
January 21, 2014
No SSDT-BI support yet I presume. right?Anonymous
January 21, 2014
Not sure what peoples complaints are about the VS UI. Though I do miss the MSI template, not sure why Microsoft choose to ditch that feature as InstallShield limited edition is pretty... Limited to say the least. It requires upgrading if you want to use 90% of it's features. The other 10% I can power shell or batch scripts for, so it begs the question of what's the point of the limited edition of Installshield?Anonymous
January 22, 2014
The comment has been removedAnonymous
January 22, 2014
@DLLE - I've reported this issue for you at connect.microsoft.com/.../navigate-to-ctrl-can-get-stuck-after-deleting-files.Anonymous
January 22, 2014
ROSLYN!!!! Nope. :(Anonymous
January 22, 2014
Thank you @LukeAnonymous
January 29, 2014
je veux etre memebreAnonymous
February 01, 2014
Can't wait to get thisAnonymous
February 02, 2014
This update is really Buggy here (Win7/X64)! It even crash during startup phase without any project loaded causing Windows error reporting. I cannot use it and uninstalled it immediately.Anonymous
February 03, 2014
@TorstenR: I've reported this issue for you at connect.microsoft.com/.../update-1-crashes-on-win7-x64. Feel free to add additional details to the report.Anonymous
February 13, 2014
The comment has been removedAnonymous
February 13, 2014
The comment has been removedAnonymous
February 14, 2014
Holy cow, I just installed Update 1, and now I'm restarting VS2013 every 5 minutes because it locks some PDBs (a simple console app using a simple WCF service). I'm just about fed up enough with it to revert to VS2012. Not what I was hoping for out of a bug fix pack at all.Anonymous
February 14, 2014
@Keith Patrick: Regarding the WCF debugging issues you mention, any chance you could report these at connect.microsoft.com/VisualStudio with details about your repro? You also mentioned not being a fan of automatic brace completion. This can be configured in Quick Launch (ctrl+q) searching for "automatic brace completion". On the comment/uncomment icon, VS2013 actually uses an icon that is nearly identical to VS2010.Anonymous
February 14, 2014
@Luke Hoban (MS) - There's already an item for it (connect.microsoft.com/.../533411). MS marked it fixed, even though as you can see from the comments that it's actually gotten worse with VS2013. This is a typical workflow for MS Connect issues, which is why I gave up on entering bugs there (about half of mine get closed for one reason or another, while the rest get replied to with a "We'll look at it in a future version", which I interpret as "Hopefully you'll forget about it in a few years")Anonymous
February 19, 2014
@Keith Patrick regarding your comment that Intellisense has stopped working for you but restart cured the issue, we would like to follow up with you to hear more about the problem if you are still experiencing it. I saw your response regarding Connect, but would definitely encourage you to open a Connect bug on this issue so we can take a look. Thanks Mark (VS Editor Team)Anonymous
February 24, 2014
I installed Update 1 some days ago. In the last days it occured multiple times that intelli-sense (in C#) didn't worked anymore, but I cannot see an action responisble for that. Before installing the update, this happened only very seldom, so I think it has to do with the update. As a consequence, some wrong errors are shown in the text-editor (red-underlined code-parts), while the code compiles without problems.