Visual studio 2013 community


Visual Studio Community Edition 2013

Yesterday Microsoft released a new Visual Studio 2013 edition – Visual Studio Community 2013:

Internally it is Visual Studio Professional 2013 with Update 4 (that normally costs $499) excluding SharePoint, Office, LightSwitch and Cloud Business Applications from the installer, but now is free for non-enterprise organizations. The exact license wording is following:

  • “Any individual developer can use Visual Studio Community to create their own free or paid apps.
  • An unlimited number of users within an organization can use Visual Studio Community for the following scenarios: in a classroom learning environment, for academic research, or for contributing to open source projects.
  • For all other usage scenarios: In non-enterprise organizations, up to 5 users can use Visual Studio Community. In enterprise organizations (meaning those with >250 PCs or > $1MM in annual revenue), no use is permitted beyond the open source, academic research, and classroom learning environment scenarios described above.” (source)
  • “Example 1: A University wants to use Visual Studio Community 2013 for training students enrolled in the “Data structures and Programming” course and for a “Big Data” academic research project that requires building a cross-platform mobile application. Further the University also plans to customize its ERP software and automate processes through its internal LOB applications. Visual Studio Community 2013 use is allowed by academic institutions for classroom learning environment and academic research and hence the University can use the software for its coursework and the research project. However Visual Studio Community 2013 cannot be used for developing and testing its internal LOB applications.
  • Example 2: A Fortune 500 firm has outsourced the development of its store-locator mobile application to a small agency. The application is not an open source project. The agency has 5 employees working on the project and would like to use Visual Studio Community 2013. Since the agency is a contractor developing this application for the Fortune 500 firm, and since the application is not an open source project, the agency cannot use Visual Studio Community 2013 for developing and testing the application.
  • Example 3: A Fortune 500 ISV is working on a mobile application which is released under the Open Source Institute (OSI)-approved open source software licenses. Employees and contractors developing and testing this application may use Visual Studio Community 2013.”(Visual Studio and MSDN Licensing White Paper)

Microsoft previously offered another free Visual Studio edition – Visual Studio Express, but it did not support third party add-ins and extension. Visual Studio Community 2013 supports all add-ins and extensions that work with Visual Studio Professional 2013 (it even returns Professional as the Edition property of the Visual Studio DTE automation object). “Soma mentioned in today’s Connect event that Visual Studio Community Edition may retire Visual Studio Express Editions in future, but this is not decided yet” OneCode Team. “We’re not currently planning to release an Express edition in the 2015 wave. The community edition will become our first and best free offering for developers creating non-enterprise apps.” Doris Chen.

You can download Visual Studio Community 2013 with Update 4 here (Web installer 1.2 MB or ISO 6.9 GB).

This entry was posted in Visual Studio news and tagged Visual Studio 2013. Bookmark the permalink.

visualstudioextensions.vlasovstudio.com

Требования к системе Visual Studio 2013

Требования к системе для семейства продуктов Visual Studio 2013 приведены в таблице ниже. Дополнительные сведения о совместимости см. в разделе Целевая платформа и совместимость Visual Studio 2013.

Чтобы просмотреть требования к системе для конкретных продуктов, щелкните закладку ниже.

Скачать

Вы можете скачать Visual Studio 2013 по ссылке My.VisualStudio.com. My.VisualStudio.com требуется бесплатная подписка Dev Essentials или подписка Visual Studio.

Visual Studio 2013

Требования к оборудованию
  • Процессор с тактовой частотой 1,6 ГГц или большей
  • 1 ГБ ОЗУ (1,5 ГБ при выполнении в виртуальной машине)
  • 4 ГБ доступного пространства на жестком диске
  • Жесткий диск 5400 об/мин
  • Видеоадаптер с поддержкой DirectX 9 и разрешением экрана 1024x768 или выше
Дополнительные требованияВ Windows 8.1 и Windows Server 2012 R2 требуется обновление из статьи базы знаний KB2883200 (доступно в Центре обновления Windows). Требования к оборудованию
  • Процессор с тактовой частотой 1,6 ГГц или большей
  • 1 ГБ ОЗУ (1,5 ГБ при выполнении в виртуальной машине)
  • 11 ГБ доступного пространства на жестком диске
  • Жесткий диск 5400 об/мин
  • Видеоадаптер с поддержкой DirectX 9 и разрешением экрана 1024x768 или выше
Дополнительные требованияТребуется обновление из статьи базы знаний KB2883200 (доступно в Центре обновления Windows). Требования к оборудованию
  • Процессор с тактовой частотой 1,6 ГГц или большей
  • 1 ГБ ОЗУ (1,5 ГБ при выполнении в виртуальной машине)
  • 20 ГБ доступного пространства на жестком диске
  • Жесткий диск 5400 об/мин
  • Видеоадаптер с поддержкой DirectX 9 и разрешением экрана 1024x768 или выше
Дополнительные требованияТребуется обновление из статьи базы знаний KB2883200 (доступно в Центре обновления Windows). Требования к оборудованию
  • Процессор с тактовой частотой 1,6 ГГц или большей
  • 1 ГБ ОЗУ (1,5 ГБ при выполнении в виртуальной машине)
  • 20 ГБ доступного пространства на жестком диске
  • Жесткий диск 5400 об/мин
  • Видеоадаптер с поддержкой DirectX 9 и разрешением экрана 1024x768 или выше
Дополнительные требованияТребуется обновление из статьи базы знаний KB2883200 (доступно в Центре обновления Windows). Требования к оборудованию
  • Процессор с тактовой частотой 1,6 ГГц или большей
  • 1 ГБ (32-разрядные) или 2 ГБ (64-разрядные) ОЗУ (дополнительные 512 МБ для узла, если он запущен в виртуальной машине)
  • 3 ГБ доступного пространства на жестком диске
  • Жесткий диск 5400 об/мин
  • Видеоадаптер с поддержкой DirectX 9 и разрешением экрана 1024x768 или выше
Дополнительные требованияВ Windows 8.1 и Windows Server 2012 R2 требуется обновление из статьи базы знаний KB2883200 (доступно в Центре обновления Windows). Требования к оборудованию
  • Процессор с тактовой частотой 1,6 ГГц или большей
  • 1 ГБ ОЗУ (1,5 ГБ при выполнении в виртуальной машине)
  • 20 ГБ доступного пространства на жестком диске
  • Жесткий диск 5400 об/мин
  • Видеоадаптер с поддержкой DirectX 9 и разрешением экрана 1024x768 или выше
Дополнительные требованияТребуется обновление из статьи базы знаний KB2883200 (доступно в Центре обновления Windows).
Requirements Поддерживаемые операционные системы
<FONT SIZE="3" COLOR=#5c2d91>Visual Studio Express 2013 с обновлением 5 для Windows Desktop Требования к оборудованию
  • Процессор с тактовой частотой 1,6 ГГц или большей
  • 1 ГБ ОЗУ (1,5 ГБ при выполнении в виртуальной машине)
  • 5 ГБ доступного пространства на жестком диске
  • Жесткий диск 5400 об/мин
  • Видеоадаптер с поддержкой DirectX 9 и разрешением экрана 1024x768 или выше
Дополнительные требованияВ Windows 8.1 и Windows Server 2012 R2 требуется обновление из статьи базы знаний KB2883200 (доступно в Центре обновления Windows).
Windows 7 с пакетом обновления 1 (SP1) (x86 и x64)Windows 8 (x86 и x64)Windows 8.1 (x86 и x64)Windows Server 2008 R2 с пакетом обновления 1 (SP1) (x64)Windows Server 2012 (x64)Windows Server 2012 R2 (x64)
<FONT SIZE="3" COLOR=#5c2d91>Visual Studio Express 2013 с обновлением 5 для Web
Windows 7 с пакетом обновления 1 (SP1) (x86 и x64)Windows 8 (x86 и x64)Windows 8.1 (x86 и x64)Windows Server 2008 R2 с пакетом обновления 1 (SP1) (x64)Windows Server 2012 (x64)Windows Server 2012 R2 (x64)
<FONT SIZE="3" COLOR=#5c2d91>Visual Studio Express 2013 с обновлением 5 для Windows
Windows 8.1 (x86 и x64)
<FONT SIZE="3" COLOR=#5c2d91>Visual Studio Community 2013 с обновлением 5
Windows 8.1 (x86 и x64)Windows 8 (x86 и x64)Windows 7 с пакетом обновления 1 (SP1) (x86 и x64)Windows Server 2012 R2 (x64)Windows Server 2012 (x64)Windows Server 2008 R2 с пакетом обновления 1 (SP1) (x64)
<FONT SIZE="3" COLOR=#5c2d91>Visual Studio Premium 2013 с обновлением 5 Требования к оборудованию
  • Процессор с тактовой частотой 1,6 ГГц или большей
  • 1 ГБ ОЗУ (1,5 ГБ при выполнении в виртуальной машине)
  • 20 ГБ доступного пространства на жестком диске
  • Жесткий диск 5400 об/мин
  • Видеоадаптер с поддержкой DirectX 9 и разрешением экрана 1024x768 или выше
Дополнительные требованияТребуется обновление из статьи базы знаний KB2883200 (доступно в Центре обновления Windows).
Windows 8.1 (x86 и x64)Windows 8 (x86 и x64)Windows 7 с пакетом обновления 1 (SP1) (x86 и x64)Windows Server 2012 R2 (x64)Windows Server 2012 (x64)Windows Server 2008 R2 с пакетом обновления 1 (SP1) (x64)
<FONT SIZE="3" COLOR=#5c2d91>Visual Studio Professional 2013 с обновлением 5
Windows 8.1 (x86 и x64)Windows 8 (x86 и x64)Windows 7 с пакетом обновления 1 (SP1) (x86 и x64)Windows Server 2012 R2 (x64)Windows Server 2012 (x64) Windows Server 2008 R2 с пакетом обновления 1 (SP1) (x64)
<FONT SIZE="3" COLOR=#5c2d91>Visual Studio Test Professional 2013
Windows 8.1 (x86 и x64)Windows 8 (x86 и x64)Windows 7 с пакетом обновления 1 (SP1) (x86 и x64)Windows Server 2008 R2 с пакетом обновления 1 (SP1) (x64)Windows Server 2012 (x64)Windows Server 2012 R2 (x64)
<FONT SIZE="3" COLOR=#5c2d91>Visual Studio Ultimate 2013 с обновлением 5
Windows 8.1 (x86 и x64)Windows 8 (x86 и x64)Windows 7 с пакетом обновления 1 (SP1) (x86 и x64)Windows Server 2012 R2 (x64)Windows Server 2012 (x64)Windows Server 2008 R2 с пакетом обновления 1 (SP1) (x64)
Дополнительные сведения
  • Эта версия Visual Studio лучше всего работает с Internet Explorer 10 или более поздней версии. Если Internet Explorer 10 не установлен на компьютере, некоторые функции могут работать непредвиденным образом.
  • При разработке для Windows Phone 8.0 требуется Windows 8.1 (x64) или более поздней версии.
  • При разработке для Windows Phone 8.1 требуется Windows 8.1 (x86) или более поздней версии.
  • Для эмуляторов Windows Phone, Windows 8.1 (x64) Профессиональная или более поздней версии и процессора, поддерживающего Client Hyper-V и преобразование адресов второго уровня (SLAT).
  • Если компьютер соответствует требованиям к операционной системе, но не соответствует требованиям к оборудованию для эмуляторов Windows Phone, средства разработки Windows Phone будут установлены и запущены. Однако эмуляторы Windows Phone 8.0 и 8.1 не будут работать, и вам потребуется использовать устройство для развертывания или тестирования приложений на Windows Phone.

Team Foundation Server 2013

Requirements Поддерживаемые операционные системы
<FONT SIZE="3" COLOR=#5c2d91>Team Foundation Server 2013 с обновлением 5 Требования к оборудованию
  • Процессор с тактовой частотой 1,6 ГГц или большей
  • 1 ГБ ОЗУ (1,5 ГБ при выполнении в виртуальной машине)
  • 10 ГБ свободного пространства на жестком диске для обычной установки
  • 600 МБ доступного пространства на жестком диске (языковой пакет)
  • Жесткий диск 5400 об/мин
  • Видеоадаптер с поддержкой DirectX 9 и разрешением экрана 1024x768 или выше
Windows 7 с пакетом обновления 1 (SP1) (x86 и x64)Windows 8 (x86 и x64)Windows 8.1 (x86 и x64)Windows Server 2008 R2 с пакетом обновления 1 (SP1) (x64)Windows Server 2012 (x64)Windows Server 2012 R2 (x64)
<FONT SIZE="3" COLOR=#5c2d91>Team Foundation Server Express 2013 с обновлением 5 Требования к оборудованию
  • Процессор с тактовой частотой 1,6 ГГц или большей
  • 1 ГБ ОЗУ (1,5 ГБ при выполнении в виртуальной машине)
  • 5 ГБ доступного пространства на жестком диске
  • Жесткий диск 5400 об/мин
  • Видеоадаптер с поддержкой DirectX 9 и разрешением экрана 1024x768 или выше
Дополнительные требованияВ Windows 8.1 и Windows Server 2012 R2 требуется обновление из статьи базы знаний KB2883200 (доступно в Центре обновления Windows).
Windows 7 с пакетом обновления 1 (SP1) (x86 и x64)Windows 8 (x86 и x64)Windows 8.1 (x86 и x64)Windows Server 2008 R2 с пакетом обновления 1 (SP1) (x64)Windows Server 2012 (x64)Windows Server 2012 R2 (x64)
Дополнительные сведения
  • Эта версия Visual Studio лучше всего работает с Internet Explorer 10 или более поздней версии. Если Internet Explorer 10 не установлен на компьютере, некоторые функции могут работать непредвиденным образом.

Visual Studio 2012

Requirements
<FONT SIZE="3" COLOR=#5c2d91>Visual Studio 2012 с обновлением 5 Требования к оборудованию
  • Процессор с тактовой частотой не ниже 1,6 ГГц
  • 1 ГБ ОЗУ (1,5 ГБ, если для запуска используется виртуальная машина)
  • 1 ГБ доступного пространства на жестком диске
  • Жесткий диск 5400 об/мин
  • Видеоадаптер с поддержкой DirectX 9 и разрешением 1024x768 или выше

К началу страницы

www.visualstudio.com

Visual Studio 2013 Update 4

November 12, 2014

Today, we are happy to announce the availability of Visual Studio 2013 and Team Foundation Server 2013 Update 4 Release to Manufacturing (RTM).

Download Visual Studio 2013 Update 4

This update is the latest in a cumulative series of feature additions and bug fixes for Visual Studio 2013. You can download Visual Studio 2013 and Team Foundation Server 2013 from My.VisualStudio.com. My.VisualStudio.com requires a free Dev Essentials subscription, or a Visual Studio Subscription.

What's new in Visual Studio 2013 Update 4

Visual Studio updates:

Team Foundation Server updates:

Microsoft SQL Server Database Tooling updates:

Other changes:

-Bug Fixes & Known Issues

In addition, several Visual Studio 2013 products are available for download with Update 4, including the following:

To get more details on these releases, go to the Related Releases section below.

Watch the Visual Studio 2013 Update 4 episode of Visual Studio Toolbox to learn about new features in this release:

CodeLens

With CodeLens indicators you can learn about your code while staying focused on your work. You can find code references, changes to your code, related TFS items, and unit tests – all without looking away from the code. Learn more about CodeLens.

Reduced data storage requirements for CodeLens with TFVC

The size of CodeLens data stored in the TFS database has been reduced. The data has been reformatted and duplicated information removed.

By default, CodeLens now only processes changes from the last 12 months to calculate team indicators. You can change this duration by using the TFSConfig CodeIndex command.

C++ Diagnostics

GPU Usage

A new GPU Usage tool in the Performance and Diagnostics hub helps you determine whether the CPU or the GPU is the performance bottleneck. This tool lets you collect and analyze GPU usage data for DirectX applications.

You can use this tool for both Windows Desktop and Windows Store apps; support for Windows Phone and remote diagnostics will ship in a later release. You can also inspect the timing of each individual GPU event if a supported graphics card is present and latest drivers are installed.

Faster browsing

Visual Studio now scans or rescans large solutions and updates the symbol database more quickly. Browsing should be more responsive, and operations such as Go To Definition should not be blocked, even if the database has not been completely updated. A non-blocking message will warn you that your results may be inaccurate.

JavaScript IntelliSense

You can now get IntelliSense in JavaScript modules loaded with RequireJS. Learn more about RequireJS.

We have made improvements in the JSON and HTML editors.

JSON Editor Improvements

We made a few improvements in the JSON editor, including loading the JSON schema asynchronously, caching child schemas, and improving IntelliSense. We also have the following new features:

  • JSON Schema validation. We added a JSON schema validation feature, based on the schema selected in the drop-down list.
  • Un-minify the context menu button. You can right-click the JSON editor and select Un-minify context menu button to un-minify any long arrays in the JSON file.
  • The Reload Schemas context menu button. Visual Studio caches the schema downloaded from internet, and will use the cache even after you restart Visual Studio. If you know the schema has changed, you can use the context menu to download the changed schema in the active JSON document and use it immediately.

HTML Editor Improvements

We improved the HTML editor with some bug fixes, updated IntelliSense for web standards, and introduced the following new features:

  • Better client template formatting. The HTML editor no longer parses or formats double-curly syntax {{…}}, so we don’t flag the content as invalid HTML or try to format it as HTML. This is great for Angular, Handlebars, Mustache and other double-curly template syntaxes.
  • Support for custom elements, polymer-elements and attributes.We no longer validate unknown attributes for custom elements, because there can be many custom-made tags in different frameworks. There will no longer be squiggles under the unknown elements.
  • HTML element tooltips. We now supply tooltips for HTML elements in the editor.
  • #region support. The HTML editor now supports region folding. You can use a surrounding snippet to surround the current selection as well.
  • viewport fix for the LESS editor. In the LESS editor, @viewport no longer shows verification warnings.
  • Many more snippets. We now provide more snippets to make your developing experience easier.
  • CSS auto-sync. Saving the CSS file or changing it externally (for example, with a LESS/SASS compiler) causes the whole CSS file to reload in the browser. If the file couldn’t auto-sync, Ctrl+S causes an automatic reload without needing to refresh the linked browsers(Ctrl+Alt+Enter). This feature can be disabled in the toolbar.

Azure WebJobs

In Visual Studio 2013 Update 4 we’re releasing some new features that will make it easier than ever to build, deploy, and debug Azure WebJobs, and to add background processing to Azure Websites. WebJobs are now represented as nodes in the Visual Studio Server Explorer, so you can link directly to the WebJobs dashboards to see how your WebJobs are running. You can also use the Server Explorer to start and stop continuous jobs and run on-demand or scheduled jobs. We’ve also enabled one-click remote debugging of continuous WebJobs, so if you need to see how your continuous WebJob is processing incoming queues or blob messages, you can step through your code as it’s running live in the cloud.

WebJobs SDK

The WebJobs SDK is pre-installed in the Azure WebJob project templates. As before, you can create a new WebJob project using the Azure WebJob project template.

ASP.NET MVC 5.2.2

Template packages are updated to use ASP.NET MVC 5.2.2. This release doesn’t have any new features or bug fixes in MVC. We made a change in Web Pages for a significant performance improvement, and have updated all other dependent packages we own to depend on this new version of Web Pages.

ASP.NET Web API 5.2.2

In this release we have made a dependency change for Json.Net 6.0.4. Get more details about what's new in this release of Json.NET 6.0 Release 4. This release doesn’t have any other new features or bug fixes in Web API. We have subsequently updated all other dependent packages we own to depend on this new version of Web API.

ASP.NET Web API OData 5.3.1 beta

See what's New in ASP.NET Web API OData 5.3.

SignalR 2.1.2

Template packages are updated to use SignalR 2.1.2. See SignalR 2.1.2.

Microsoft Owin 3.0 package

Template packages are updated to use Microsoft Owin 3.0 NuGet packages. See this Katana 3.0 release note.

Application Insights

With Update 4, Application Insights Tools for Visual Studio has more performance improvements and bug fixes. It is fully compatible with projects that had Application Insights added with Visual Studio 2013.3. This update includes:

  • Seamless integration with the workflow to publish to an Azure website
  • Improved solution integration and project detection. (For example, Application Insights is no longer included in unsupported projects like Python.)

To learn more about changes to Application Insights data in the Azure Preview Portal, go here.

Developer License Renewal

When your developer license is within 15 days of expiring, you will start to see a new notification in the notification hub. Click the notification when you’re ready to renew your license, and then click I Agree on the renewal window. You must have an internet connection to renew your license. After your license expires, you won’t be able to debug or deploy your Windows Store apps, or open the XAML or HTML designers.

Release Management

Improve the process of managing the release of your app. Deploy your app to a specific environment for each separate stage. Manage the steps in the process with approvals for each step.

You can create release templates that use deployment agents to deploy your app, or you can create release templates that use Windows PowerShell, Windows PowerShell Desired State Configuration (DSC), or Chef. To help you know which type of release you are setting up, terms have been added to the UI to make your choices clearer: agent-based or vNext (without agents). This simply helps you identify that you are using the correct environments and components for your release templates and release paths.

Use the Release Management service for Visual Studio Team Services

Now you can setup a release pipeline from check-in through to deployment without having to install and maintain an on-premises Release Management server. Use the Release Management service for Visual Studio Team Services to set up your release. (This service is in preview.)

From your Release Management client, connect to your Visual Studio Team Services account. Create a release definition for your app from the RM client. When you release your app to each stage, the Release Management service is used.

Release to Azure from Visual Studio

You can now create a release definition directly from within the Visual Studio IDE using Release Management as a service with a Visual Studio Team Services account. You must use an Azure subscription to deploy to your Azure VMs with this release definition. Learn more about this here.

Use tags when you deploy to an environment

Now you can use tags with the servers in your Azure or standard environments when you deploy without agents. For example, if you have multiple web servers in your environment then you can tag them all with WebServer. Set up your deployment actions for your tags. When a stage is deployed, these actions are performed on any server with this tag. So you only have to create the set of actions once for multiple servers.

With tags you can also switch the deployment order from parallel to sequence.

Access to system variables for your deployment sequences or scripts

By popular user demand, you can now access system variables just like other configuration variables and use them in your release template if you deploy without agents. You don't have to hardcode these any more.

Supported variables:

  • Build directory
  • Build number (for component in the release)
  • Build definition (for component)
  • TFS URL (for component)
  • Team project (for component)
  • Tag (for server which is running the action)
  • Application path (destination path where component is copied)
  • Environment (for stage)
  • Stage
  • Release id
  • Release name

Reduce the need for configuration files to deploy your builds

If you deploy without using agents, you can now set up configuration variables for your release at the following levels: global, server, component, action. This extra flexibility means you might no longer need to maintain configuration files with your build. If variables have the same name, the value is determined based on this order of precedence: action, component, server, global. (Action has the highest precedence to override the other values).

Manual intervention for a release path

Now you can add manual steps to a stage in any release path, even if you deploy without agents. Add a manual intervention activity into your deployment sequence. When the notification is triggered in that sequence, the deployment pauses and you can run some manual steps before continuing with the rest of the automation for the release path.

Build drops stored on TFS servers

If you have set up your build definition to copy the build output to the server and not a UNC path, you can now use these builds that are stored on the server if you deploy your app without agents.

Deploy from a build drop using a shared UNC path

You can now use Release Management to deploy to servers using build drops located on a shared UNC path. You can deploy only if both the target server and the Release Management server have access to the shared UNC path, and you deploy your app without deployment agents.

Usability improvements

You can now select servers and components from the drop-down list in the action for all types of release templates. You can also give actions friendly names to make it easier to identify them.

Mix and match Azure and standard environments

Previously for a release path that deployed to servers without agents, each stage in the path could only use either all Azure environments or all standard environments. Now you can mix and match your environments. For example, your test stage might deploy to an Azure environment, but your production stage deploys to on-premises production servers using standard environments.

Test

Find out quickly if a test case belongs to other test suites

As test cases can belong to more than one test suite, it's good to check if there are any other associated test suites before you make changes to a test case. Now you can quickly view all the test suites associated with a test case.

View recent test results for a test case

Quickly see the test result history for a test case to see if it has passed or failed recently. Just select the test case, view the details pane, and choose test results.

Real-time lightweight charts to show testing status

Now you can create snapshot and trend charts for test cases from the Charts tab in the test hub. You can also create snapshot charts for test results. Pin these charts to your home page so that all the team can see the test status.

Learn more and see examples of these charts.

Filter by tags in the test hub

Tag test cases in a suite with any tag that is important to you. For example, tag all the tests related to login so that you can rerun these tests if a bug is fixed for the login page. Then you can filter on that tag from the test hub. You can add and edit tags when you edit a test case, or bulk edit tags in the grid view.

Version control

Review and merge code with Git pull requests

Pull requests are a critical component of the developer workflow in Git. Now developers can use pull requests to help review and merge their code. Pull requests enable developers working in branches to get feedback on their changes from other developers before adding their code into the mainline. Any developer participating in the review can see the code changes, leave comments in the code, and give a “thumbs up” approval.

Plan and track work

The many small improvements to Team Foundation Server (TFS) with Update 4 help make it easier for you to use our tools to get your work done faster.

Visualize trends and aggregate field values

Query-based chart authoring now includes trend charts: Stacked Area, Area, and Line. You can visualize trends across a one-week, two-week, or four-week time range. Also, in addition to field counts, you can now sum a field value across work items returned in a flat-list query. These new chart types can be pinned to your home pages too. Learn more about how to view the status of your progress.

Quickly reorder backlog items

If you had a large backlog, it was hard to drag and drop items to a different position. The context menu for backlog items now contains options to move an item directly to the top or to a specific position in the backlog. Be aware that with this change, we removed the field that tracks backlog priority from the work item forms in the default TFS process templates.

Full screen mode support for backlog views, boards, queries

If you’re running a daily standup or viewing large backlogs, it's useful to be able to maximize the screen space and see as many items at once. Now you can hide all the chrome in the UI and have full-screen views of the backlog and boards. The toggle to enter full screen mode works for all the pages under the Backlogs and Queries tabs in the Work hub. Press ESC to return to the full work item view.

Full screen mode support for all HTML/rich-text fields

You can now enter full screen mode for rich-text fields to help improve the readability and usability. For example, the Steps to Reproduce field can be maximized as shown below. The button toggles the text area between full screen mode and the work item view. Press ESC to return to the full work item view.

Better triage experience

To improve the triage experience when you review query results, you can go back to the query by pressing Alt+Q. This keeps your position in the query.

Assign backlog items to iterations within hierarchical views

From hierarchical views, you can now assign product backlog items to iterations with drag and drop.

In-line search for area and iteration fields from the work item form

Often when triaging or assigning work items it’s necessary to change the area and/or the iteration path. Finding the path you want in large, deeply nested trees can be difficult. With inline search, values that match what you type are instantly highlighted. For example, type Team to highlight all path entries that contain the work Team in their name.

Open hyperlinks quickly

If you have a hyperlinks defined within an HTML field, press the CTRL key and click the link. Previously it was a two step process to click the link, and then click the “navigate to…” command at the top of the text area.

Teams choose whether or not to track bugs on their backlog

Teams now have greater flexibility in how they track bugs. While team projects created with the Scrum process template include bug tracking on the backlog, other process templates don't. Each team can now choose to view the bugs with the product backlog or turn off including them.

More details about adding bugs to the task board are here.

Work item form enhancements

Track work and share information more easily using some of the new features listed below and highlighted in the work item form pictured.

  • Send a nicely formatted email directly from the work item form using the new email icon.
  • Return directly to the query result you navigated from. If you like to use the keyboard, press ALT+Q. Or you can use the browser back button to do the same thing. This keeps your position in the query.
  • Enter full screen mode from all queries and all work items. Just click the command in the toolbar to remove all the chrome and maximize your screen real estate.
  • Open a work item in a new browser tab with the context menu command for query results.
  • Copy and paste of query results now formats the results much better for pasting into email or a document.

More items in your Kanban board

There is no longer a hard limit on the number of items in the first and last columns of the Kanban board. Now you can configure this limit to have up to 999 items.

Easier way to link work items

In Visual Studio, there has always been a dialog box to find a work item that you want to link to, but with Team Web Access you could only type the work item ID to find it. With Update 4, you get a similar dialog box to find the work item you want to link to. You can run an existing query or find the work item based by searching for its title.

Access level name changes and feature access

With Update 4, all access levels have been renamed. The new names correspond to the same names used for Visual Studio Team Services licensing.

  • Stakeholder (previously was Limited)
  • Basic (previously was Standard)
  • Advanced (previously was Full)

With this change, the feature set support for the Stakeholder access has been enhanced. Stakeholders have access to the project home page and most of the “work” related functionality. This includes the ability to view the backlog, add and edit items, run work item queries and more.

Any number of users can be assigned a stakeholder license at no charge. See more details here.

These are the added features for Update 4:

  • SQL Server 2014 is now supported.
  • Schema compare supports MSBuild with text and XML output.
  • Token-based authentication for Azure SQL Database node in Server Explorer is supported -for Microsoft accounts and organizational accounts.
  • From the Azure Preview Portal for Microsoft Azure SQL databases, you can now open the database schema directly in Visual Studio.
  • Extensibility for Static Code Analysis.
  • Filtering for the editable data grid.
  • Save your data compare settings to a file (.dcmp).
  • Additional actions are available when you connect to the TSQL editor.
  • PDW tools are now part of Visual Studio Express 2013 for Windows Desktop

Other Changes: Bug Fixes & Known Issues

For a complete description of technology improvements, bug fixes and known issues in this release see the KB article for Visual Studio 2013 Update 4.

Azure SDK 2.5

This release provides new and enhanced tooling for Azure development with Visual Studio 2013 Update 4 and now Visual Studio 2015 Preview, including Azure Resource Manager Tools, HDInsight Tools, and the ability to manage Azure WebJobs from Server Explorer. Learn more about this release from theAzure SDK 2.5 release notes.

Download Azure SDK 2.5 now.

Team Explorer Everywhere 2013 Update 2

TEE 2013 Update 2 improves how TEE stores credentials which makes signing in to Visual Studio Team Services much easier. This release also adds the capability to browse Git repositories within TEE. Read more about this here.

Download TEE 2013 Update 2 now.

Visual Studio Tools for Unity (VSTU) 2.0 Preview

VSTU is Microsoft’s free Visual Studio add-on that enables a rich programming and debugging experience for working with the Unity gaming tools and platform. VSTU 2.0 Preview adds support for Visual Studio 2015 Preview. Better visualization for objects in watch and local windows has been added too.

Recent releases

2.0 VSTU -find out more about this release here.

1.9.1 VSTU - find out the details of the new features and bug fixes from this blog post.

1.9.2 VSTU - the minor features and bug fixes are listed here in this change log.

To get started with the latest version of VSTU, download the tools from the Visual Studio Gallery: VSTU for Visual Studio 2013, VSTU for Visual Studio 2012, and VSTU for Visual Studio 2010.

Kinect for Windows 2.0 SDK RTW

Here are the details for this release:

  • Kinect for Windows software development kit 2.0 features over 200 improvements and updates to the preview version of the SDK. The SDK is a free download, and there are no fees for runtime licenses of commercial applications developed with the SDK.
  • Ability to develop Kinect apps for the Windows Store. With commercial availability of SDK 2.0, you can develop and deploy Kinect v2 apps in the Windows Store for the first time. Access to the Windows Store enables you to reach millions of potential customers for your business and consumer solutions.
  • Availability of the US$49.99 Kinect Adapter for Windows that enables you to connect a Kinect for Xbox One sensor to Windows 8.0 and 8.1 PCs and tablets. Now developers can use their existing Kinect for Xbox One sensor to create Kinect v2 solutions, and consumers can experience Kinect v2 apps on their computer by using the Kinect for Xbox One sensor they already own. The adapter is available in over two dozen markets—rolling out later today—and will be available in a total of 41 markets in the coming weeks.

For more details, go here.

Download the Kinect for Windows software development kit now.

Visual Studio Tools for Apache Cordova CTP3

Formerly known as Multi-Device Hybrid Aps for Visual Studio, Visual Studio Tools for Apache Cordova makes it easy to build, debug, and test cross-platform apps that target Android, iOS, Windows, and Windows Phone from one simple Visual Studio project. Learn more here.

CTP3 includes the following improvements over CTP2:

  • Update on save for Ripple – No need to rebuild!
  • The ability to debug an iOS version of your app right from Visual Studio when deployed to the iOS Simulator or a connected device on a Mac
  • Improved security and simplified configuration for the included remote iOS build agent
  • An improved plugin management experience that includes support for adding in custom plugin to your project from Git or the filesystem
  • Support for Apache Cordova 4.0.0

Download the latest update of Visual Studio Tools for Apache Cordova now.

Office Developer Tools for Visual Studio 2013 – November 2014 Update

This release includes the new Office 365 API Tools, which make it easy to develop apps that connect to Office 365 APIs. Simply choose the Add->Connected Service item on the project context menu and the dialog will guide you through the process of creating the app entry in Azure Active Directory and adding the appropriate references and configuration in your solution. The tool supports most project types in Visual Studio 2013, including ASP.NET MVC, ASP.NET Web Forms, WPF, Windows Forms, Universal Apps, Apache Cordova and Xamarin.

Download the latest update of Office Developer Tools for Visual Studio 2013 now.

TypeScript 1.3

TypeScript 1.3, available as a separate download for Visual Studio 2013 Update 4, adds protected member access and tuple types, allowing for more natural object-oriented patterns and more precise array types.

Learn more and download here.

Visual Studio Community 2013 is a new edition that enables you to unleash the full power of Visual Studio to develop cross-platform solutions. Create apps in one unified IDE. Get Visual Studio extensions that incorporate new languages, features, and development tools into this IDE. (These extensions are available from the Visual Studio Gallery.) Learn more about Visual Studio Community 2013.

Download Visual Studio Community 2013 now.

Top of Page

www.visualstudio.com

RTM-версия Visual Studio 2013 с обновлением 5 (2013.5)

20 июля 2015 г.

Сегодня мы рады объявить о выпуске окончательной первоначальной версии обновления 5 для Visual Studio 2013 и Team Foundation Server 2013.

Скачивание. Вы можете скачать Visual Studio 2013 по ссылке My.VisualStudio.com. My.VisualStudio.com требуется бесплатная подписка Dev Essentials или подписка Visual Studio.

Это обновление является последним в накопительной серии технологических улучшений и исправлений ошибок для Visual Studio 2013. Регулярные обновления позволяют улучшать и расширять возможности Visual Studio и Team Foundation Server, чтобы обеспечивать поддержку последних нововведений в разработке ПО, предназначенных для создания современных приложений и управления ими.

Примечание. Поддержка по Visual Studio 2013 предоставляется только для этого текущего обновления, которое считается пакетом обновления для Visual Studio 2013. RTM-версия Visual Studio 2013, выпущенная в ноябре 2013 г., будет поддерживаться только в течение года после выпуска текущего обновления. Дополнительные сведения см. в политике жизненного цикла службы поддержки Майкрософт.

Обратите внимание: все предыдущие версии средств для Apache Cordova несовместимы с обновлением 5. Если вы ранее установили ознакомительную версию для сообщества расширения средств для Apache Cordova, его необходимо удалить перед установкой Visual Studio 2013 с обновлением 5. Если требуется поддержка Apache Cordova, рекомендуем использовать Visual Studio 2015.

Новые возможности в Visual Studio 2013 с обновлением 5

Облачное нагрузочное тестирование из центров обработки данных Azure по всему миру

Настройка инфраструктуры, необходимой для нагрузочного тестирования, при помощи Visual Studio Team Foundation Service стала еще проще: теперь можно выполнять облачное нагрузочное тестирование из любого поддерживаемого центра обработки данных Azure по всему миру.

Подробности о выборе расположения для нагрузочного теста.

Токен запроса текущей итерации

Теперь можно выполнять из Visual Studio запросы с токеном @currentIteration к Visual Studio Online или Visual Studio Team Foundation Server 2015.

Подробности о токене запроса текущей итерации.

Поддержка переименования командных проектов для локальных рабочих областей

Добавлена возможность обновления локальных рабочих областей после переименования командного проекта. При выполнении получения или возврата сопоставление рабочей области будет автоматически корректироваться и в нем будет использоваться новое имя командного проекта.

Подробности о переименовании командного проекта.

Исправления ошибок

Отладчик

  • Теперь поддерживается захват буферов глубины на оборудовании версии 9.3. Это обеспечивает поддержку отладки графики для приложений на базе Unity, выполняемых на Windows Phone.

Интегрированная среда разработки Visual Studio

  • Критическое уведомление в Центре уведомлений может указывать, что вам требуется получить или продлить лицензию разработчика. Если закрыть это сообщение и затем открыть другой проект, критическое уведомление отображается повторно.
  • При создании приложения Магазина Windows, для которого требуются регистрации WinRT, вы перестаете получать исключение System.TypeLoadException во время выполнения.
  • Предположим, что вы указали Spartan в качестве браузера по умолчанию в Windows 10 Insider Preview. При нажатии клавиши F1 на ключевом слове или в окне инструментов может оказаться, что все обращения к справке вызывают ошибку и вы не можете получить из нее материалы.
  • Если вы ранее подключались к другой коллекции, ветвление было недоступно до перезапуска Visual Studio. Это обновление устраняет данную проблему.
  • Это обновление убирает бесполезное сообщение после попытки записать после изменения набор ожидающих изменений в ранее переименованный командный проект.
  • Некоторые правки больше не теряются в серверной рабочей области для ожидающих изменений в клиенте.

Team Foundation Server

  • Документы SharePoint с именами, содержащими слишком много символов Юникода, теперь открываются правильно с помощью Team Explorer.
  • В Team Foundation Server 2013 с обновлением 4 вы не можете отправить отзыв с помощью Feedback Client, если находитесь на уровне лицензий заинтересованных лиц. Но в Team Foundation Server 2013 с обновлением 5 вы можете отправить отзыв с помощью Feedback Client, если находитесь на уровне лицензий заинтересованных лиц.
  • Когда вы изменяете рабочий элемент одновременно с другим пользователем в Веб-доступе, указанные ниже проблемы больше не возникают.
    • Рабочий элемент успешно сохраняется. Но если вы изменили поле "Состояние" и задали в поле "Причина" значение, отличное от используемого по умолчанию, в поле "Причина" восстанавливается значение по умолчанию.
    • Рабочий элемент не сохраняется, и появляется сообщение об ошибке "Поле «Состояние» не может быть пустым".
  • Теперь вы можете использовать хранилище для данных, различающихся лишь пробелом (например, "Debug" и "Debug ").
  • Команда tf merge больше не переходит в бесконечный цикл в prc_PendMerge для циклически переименованных папок, откуда ранее были удалены вложенные папки.
  • Являясь пользователем Git, теперь вы можете создать пустой клон тега заметки для репозитория Git, размещаемого в экземпляре Team Foundation Server.
  • Рабочие элементы, у которых значения поля DateTime выходят за пределы текущего периода летнего времени, неправильно отображаются в Веб-доступе.
  • При восстановлении резервных копий базы данных с помощью средства резервного копирования Team Foundation Server файл журнала (LDF) и файл данных (MDF) больше не восстанавливаются в одном расположении, если SQL Server настроен для разных расположений.
  • Внесены новые усовершенствования производительности для отчетов, например "Успех сборки за период времени", "Панель мониторинга сгорания", "Сгорание и темп работ" и "Обзор историй".
  • При скачивании изменений в удаленном репозитории файл конфигурации больше не заменяется специально созданным файлом. Файл конфигурации находится вне репозитория. Замена этого файла неправильным файлом позволяет пересопоставить команды Git, чтобы выполнять произвольные команды от вашего имени. В этой ситуации неправильный файл может попасть в репозиторий Git.
  • Теперь при наличии разрешения на просмотр событий вы можете получать уведомления команды, если у создателя подписки команды такое разрешение отсутствует.
  • Мы улучшили производительность при использовании Team Foundation Server в Веб-доступе.
  • Закрепленные диаграммы теперь отображаются лучше. Условные обозначения больше не скрыты, а также улучшено выравнивание диаграмм.
  • Отдельные правила для рабочих элементов, связанные с их вложениями, и ссылки на эти правила теперь работают как нужно.
  • Если у вас есть средство, которое препятствует регистрации COM во время запуска среды CLR (например, ведение fusion-журнала), теперь вы можете отключить запросы на вытягивание, чтобы агент заданий работал нормально.

Известные проблемы

Общие

[Примечание.] Внимательно следуйте указаниям в этом разделе. При неправильном изменении реестра могут возникнуть серьезные проблемы. Перед внесением изменений создайте резервную копию реестра для восстановления в случае возникновения проблем.

Подключаемый модуль средства записи веб-тестов для Internet Explorer не загружается при попытке записать веб-тест производительности из Visual Studio. Чтобы обойти эту проблему, удалите следующие разделы реестра.

  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\Component Categories
  • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Discardable\PostSetup\Component Categories64

Модульное тестирование

При обновлении до Visual Studio 2013 с обновлением 5 с более ранней версии может не выполняться сборка существующих проектов приложений модульного тестирования (Windows Phone) Visual C#. Чтобы обойти эту проблему, исправьте установку Visual Studio 2013 с обновлением 5.

www.visualstudio.com

Visual Studio 2017 15.4 Release Notes

Developer Community | System Requirements | Compatibility | Distributable Code | License Terms | Blogs | Known Issues

If you are accessing this page from a translated language version, and want to see the most up-to-date content, please visit this Release Notes page in English.

In this article, you will find information regarding the current release for Visual Studio 2017. Click the button to download the latest version.

For help with installation, please refer to our installation and offline installation documents.

Feedback

We’d love to hear from you! For issues, let us know via the Report a Problem option in the upper right-hand corner of either the installer or the Visual Studio IDE itself. The icon is located in the upper right-hand corner. You can track your issues in the Visual Studio Developer Community, where you can ask questions and find answers. You can also make a product suggestion through UserVoice or get free installation help through our Live Chat support.

Need professional support right now? See available support options.

Release History

You can learn more about how we ship our releases and how to identify different versions in the Visual Studio 2017 Release Rhythm document.

Known Issues

Please refer to the Known Issues section.

Release Date: October 19, 2017 - Visual Studio 2017 version 15.4.1

Top Issues Fixed in this Release

These are the customer-reported issues addressed in this version:

Release Date: October 9, 2017 - Visual Studio 2017 version 15.4.0

Summary: What's New in this Release

Top Issues Fixed in this Release

The Developer Community spoke and we listened. This list provides the 10 highest voted issues fixed in this release.   Deleting a file from the Solution Explorer doesn't delete the actual file.   Copy/Paste causes VS to hang with a popup "formatting text".   VS2017 15.3 freezes in debug when Threads window is open.   Visual Studio freezes and shows a busy notification during and after debug session.   Auto-complete adds parentheses at the wrong place.   Open same file twice in IDE results in a pop-up dialog with message "This document is opened by another project".   Test Explorer forgets settings for Default Process Architecture and Keep Test Execution Engine Running.   Visual Studio 2017 update install failed due to corrupted file.   Browse online extensions throws "The magic number in the GZip header is not correct." error.   Solution build fails with docker compose error.

See customer-reported issues fixed in Visual Studio 2017 version 15.4.

Details: What's New in this Release

Visual Studio Improvements

Setup and Installer
  • We added a launch banner in the installer to signal Visual Studio has been successfully installed (Figure 1).

(Figure 1) Successful installation with new launch banner
  • The installer now uses auto-proxy detection for downloads.
  • If a non-critical component (one that doesn't directly impede Visual Studio IDE) fails, the installer now displays a warning instead of a failure. The change makes it clearer that Visual Studio is okay to use even though there are issues you need to address and correct.
  • Creating an offline layout uses shorter paths that allow administrators to host offline installs in deeper network folder hierarchies.
  • We display a message at the end of your install when an individual package install fails or you have download issues (Figure 2). This message provides you with links to the Developer Community to get more help so that you can address issues that may be affecting your computer’s ability to install Visual Studio in its entirety.

(Figure 2) Error dialog with potential solutions
  • We resolved an issue where the installer was incorrectly setting the installed date/time in Add or Remove Programs after updating Visual Studio.
Editor
  • We fixed a screen reader problem where the Freedom Scientific’s JAWS screen reader could not use IntelliSense in the Visual Studio editor.
  • We added the popular Productivity Power Tools navigation feature Control Click Go To Definition to the core Visual Studio product.
    • For supported languages (currently C#, VB and Python, with more languages coming in future releases), holding down the Ctrl key will allow you to click on a symbol in the Visual Studio editor and navigate to its definition.
    • If you prefer to keep the older Ctrl+Click word selection behavior, you can control the feature’s key usage via Tools > Options > Text Editor > General > Enable mouse click to perform Go To Definition, which lets you select other modifier keys, or turn off the feature if you wish.
Extensibility

We fixed a bug where installed extensions did not display update notifications in Visual Studio and also were not automatically updated.

Lightweight Solution Load

We resolved a bug that caused build failures when a solution was opened with Lightweight Solution Load enabled.

Live Unit Testing

  • Live Unit Testing provides support for the three popular unit-testing frameworks: xUnit, NUnit, and both MSTest version 1 and MSTest version 2.
  • If you have not enabled Live Unit Testing, Visual Studio IDE displays a gold bar when you open a solution with existing unit tests. The gold bar provides you with more information about the feature, how to enable it, and the required prerequisites.
  • The Task Status center shows background processing notifications so you can easily address key problems while using Live Unit Testing.
  • We changed the name on the right click gesture names for inclusion/exclusion from Live Test Set – Include/Exclude to Live Unit Testing Include/Exclude. We also removed the Reset clean from the menu bar and moved it under Tools/Options/Delete persisted data.
  • We made several fixes so your system can better detect when a project has not loaded and avoid a crash in your Live Unit Testing. We added build performance improvements that avoid reevaluation of MSBuild projects when your system knows nothing has changed in the project file.

Tools for Universal Windows Platform Development

Visual Studio 2017 version 15.4 release brings you many updates to the Universal Windows Platform development tools. Read below to see what's new!

Windows Fall Creators Update Support

Visual Studio 2017 version 15.4 release brings first class support for developers targeting the Windows Fall Creators Update SDK. When you install the Universal Windows Platform Development workload with Visual Studio 2017 version 15.4, you will automatically get the Windows 10 Fall Creators Update SDK.

Updated XAML Designer for UWP Projects Targeting the Windows Fall Creators Update SDK

We have made significant updates to the XAML designer for UWP projects targeting the Windows Fall Creators Update SDK, prioritizing performance and reliability improvements, as well as the ability to render Fluent design artifacts. Please read the Visual Studio update to the XMAL Designer blog post for more details.

Note: The XAML Designer experience will be the same unless you are building a UWP application targeting the Windows Fall Creators Update.

XAML Edit & Continue Improvements

You can now edit or remove XAML resources with XAML Edit & Continue. In addition, you can also add ControlTemplates. To leverage these new features, make sure you are targeting the Windows Fall Creators Update SDK and running the application with the latest Fall Creators Update to Windows applied.

.NET Standard 2.0 Support

The Windows Fall Creators Update brings support for .NET Standard 2.0 to UWP development. In order to leverage the new APIs with .NET Standard 2.0, you need to set the minimum version target of your application to the Windows Fall Creators Update SDK. You will then have the ability to reference .NET Standard 2.0 NuGet packages, class libraries, and APIs directly from your UWP application.

Note that some libraries that support .NET Standard 2.0 may not work correctly or may require additional steps to work with UWP applications. In particular this can be the case for UWP applications compiled with .NET Native, which has known limitations with reflection. If you find this during testing we recommend you contact the library owner and ask for possible workarounds or fixes. One example of this is the Entity Framework Core 2.0 NuGet package, which currently has a few known issues with UWP that will be fixed in an upcoming patch release (for more information see the documentation on .NET implementations supported by EF Core).

Windows Application Packaging Project

Visual Studio 2017 version 15.4 release brings in new project templates to help you package any Windows projects into an .appx container, allowing for modern distribution or submission to the Windows Store.

To get started with the Windows Application Packaging Project, go to File > New > Project and select the new Windows Application Packaging Project template under the Visual C# > Windows Universal node (Figure 3).

(Figure 3) Windows Application Packaging Project

In the new project, you can add a reference to your existing Windows projects, such as WPF, WinForms, or MFC by right clicking on the Applications node in the Solution Explorer and selecting Add Reference. You then have many of the existing UWP tools that you are used to, such as packaging, manifest editing, and Store association.

Web Development Tools

  • .NET Core 2.0 is available during installation and is included by default for Web Development, and .NET Core Workloads.
  • Razor pages scaffolding is now supported.
  • You can publish to container registries, including Azure Container Registry, and Docker Hub.
  • Azure Functions tools are included in the Azure workload.
  • When publishing an Azure Web Job, you can publish as a triggered web job using cron expressions.

Visual Studio Tools for Xamarin

Xamarin Live enables developers to continuously deploy, test, and debug their apps, directly on iOS and Android devices (Figure 4). After downloading the Xamarin Live Player - available in the App Store or on Google Play - you can pair your device with Visual Studio and revolutionize the way you build mobile apps. This functionality is now included in Visual Studio and can be enabled by going to Tools > Options > Xamarin > Other > Enable Xamarin Live Player.

(Figure 4) Animation of the Xamarin Live Player pair, deployment, and live edit modes

Visit the Visual Studio Tools for Xamarin release notes for a complete list of changes in Visual Studio 2017 version 15.4.

Visual Studio Tools for CMake

Visual Studio 2017 version 15.4 brings the folowing improvements to CMake:

  • The version of CMake included with the Visual Studio Tools for CMake has been upgraded to version 3.9.
  • Folders containing multiple, independent CMakeLists are now supported.

For more info check out what's new in CMake in 15.4.

Linux C++ Improvements

You can now target Linux from your CMake projects. This enables you to work on your existing code base that uses CMake as your build solution without having to convert it to a VS project. If your code base is cross-platform you can target both Windows and Linux from within Visual Studio. For more information, see the Visual C++ for Linux Development with CMake blog post.

Visual Studio Tools for Unity Improvements

  • We improved support for the Experimental .NET 4.6 option in Unity 2017.1.
    • You have added support for the Set Instruction Pointer feature under the new runtime.
  • We provide support for user defined assemblies (assembly.json) in Unity 2017.2.
  • We made general improvements in Expression Evaluation while debugging.

Visual Studio Tools for Apache Cordova

The Android SDK is now being installed to a private location under %programdata%. This will allow users to manage their shared SDK installation elsewhere without affecting any VS-TACO scenarios.

R Tools for Visual Studio

Support for RMarkdown:
  • Live editing of RMarkdown files
  • R code formatting supported within code blocks
  • Smart indent in R code blocks
  • Brace matching and code completion
Remote Connectivity:
  • Windows Remote R support was added in the previous release
  • Linux connectivity is now available as well
General Improvements:
  • Roxygen colorization and Intellisense
  • R linting (similar to LintR)
  • R Plot history multi-select
  • Improved smart indent in multiline expressions including dplyr pipe
  • Accessible UI including viewers and grid

Blogs

Take advantage of the insights and recommendations available in the Developer Tools Blogs site.

The Developer Tools Blogs keep you up-to-date on all new releases and include deep dive posts on a broad range of features. For insights into the .NET world, check out the DotNet Blog. You can find detailed expertise in each language area team blog — C#, VB, C++ and, F# — to name a few.

Known Issues

See all existing known issues and available workarounds in Visual Studio 2017 version 15.4.

We are fully committed to listening to your feedback. Visit the Developer Community site to find the latest issues, log new issues, and upvote existing issues.

Visual Studio 2017 Release Notes History

Visual Studio 2017 Preview Release Notes

See customer-reported issues fixed in Visual Studio 2017 version 15.4.

Visual Studio 2017 version 15.3 Release Notes

See customer-reported issues fixed in Visual Studio 2017 version 15.3.

Visual Studio 2017 version 15.2 Release Notes

See customer-reported issues fixed in Visual Studio 2017 version 15.2.

Visual Studio 2017 version 15.1 Release Notes

See customer-reported issues fixed in Visual Studio 2017 version 15.1.

Visual Studio 2017 version 15.0 Release Notes

See customer-reported issues fixed in Visual Studio 2017 version 15.0.

Top of Page

www.visualstudio.com

Welcome to Visual Studio 2015

 

For the latest documentation on Visual Studio 2017, see Visual Studio 2017 Documentation.

Welcome to Visual Studio! We’ve got everything you need to create great apps for devices or desktop apps, for the web and in the cloud. Write code for iOS, Android, and Windows in one IDE. Get great IntelliSense, easy code navigation, fast builds, and quick deployment. Visual Studio increases your productivity and makes it easy to do your work alone or as part of a larger team.

Download Visual Studio Community for free to start coding right away. If you want to do cross-platform development, make sure that you install the optional packages. (You can get more features with other editions of Visual Studio.)

Jump right in, create a new project, and start writing code. Choose the type of app you want to create. Or you can take a tour of the Visual Studio IDE to get familiar with the tools.

And don’t forget to explore our code gallery to find samples to help you write your app more quickly!

You can install Visual Studio 2015 by downloading it from Visual Studio Downloads. To learn more about the installation process, see Install Visual Studio 2015.

Add your own Visual Studio extension to include a tool or script that you often use while coding. You can create custom menu items and tool windows to integrate your own tools into the Visual Studio IDE. You can extend the Visual Studio editor to analyze and fix code, or add a new project type to include just what you need.

To find the latest version of the Visual Studio Extensibility Tools (VS SDK), see Visual Studio SDK.

You can use the .NET Compiler Platform (Roslyn) to write your own code analyzers and code generators. Find everything you need at Roslyn.

Find existing extensions for the VS IDE created by Microsoft developers as well as our development community.

You can use Visual Studio to build apps for Android, iOS, and Windows devices. Learn more about it at Cross-Platform Mobile Development.

For information about Universal Windows Apps (UWP), see Universal Windows Apps.

Choose the tools you need based on your app requirements and the language you want to use.

  1. Xamarin for Visual Studio: A common code base in C# for all devices

  2. Apache Cordova with Visual Studio: A common code base for HTML, CSS, and JavaScript or Typescript

  3. Visual Studio Tools for Unity: 2D/3D game development in C#

  4. C++ for Cross-Platform Development: Shared code libraries and apps in C++

  5. Visual Studio Emulator for Android: Visual Studio Emulator for Android: Debug and test your Android apps no matter the IDE

You can connect to these services out of the box (assuming that you have an account for each service):

ASP.NET 5 is a major Update to MVC, WebAPI and SignalR, and runs on Windows, Mac, and Linux. ASP.NET 5 has been designed from the ground up to provide you with a lean and composable .NET stack for building modern cloud-based web apps and services.

Check in your code

If you work on a team, you need to share the latest versions of the code too so everyone on the team is using the same codebase. Visual Studio seamlessly integrates with Visual Studio Team Services or Team Foundation Server to provide version control with Git or TFVC (Team Foundation Version Control). Use Visual Studio Team Services to store your code in the cloud with no maintenance of a local server. Use Team Foundation Server if you want to have an on-premises server. Every time you create a code project, you have the option to add it to version control. Learn about which version control system is best for your needs: Use version control.

Build your app

You can build your app locally and make sure that it works correctly. Then use the debugging tools to fix any issues with your app. Or you can build projects on shared build servers or in the cloud. Automate your build process to build the code that the devs on your team have checked into version control. For example, you can build one or more projects nightly or every time that code is checked in.

Test your app

Create unit tests to improve the quality of your app. These tests can be run every time you check in, and as part of your build.

Plan, create and run manual and automated tests for your app. Test plans, suites, test cases and your test results are stored in the cloud with Visual Studio Team Services or on-premises with Team Foundation Server. Learn more about testing the application.

Deliver your team’s code faster

Remove barriers between members of your team and improve collaboration. Go further and automate the release of your app to each stage in your development all the way to production. Monitor your app's performance and availability when live. Collect real-time usage data about how your customers are actually using your app. See DevOps and Application Lifecycle Management for more details.

msdn.microsoft.com

Compare Visual Studio Product Offerings

Supported Usage Scenarios Contributing to Open Source Projects Non-enterprise organizations 1,for up to 5 users Development Platform Support 2 Integrated Development Environment Live Dependency Validation Architectural Layer Diagrams Visualize solutions with Dependency Graphs and Code Maps 3 3 Advanced Debugging and Diagnostics Code Map Debugger Integration .NET Memory Dump Analysis Performance and Diagnostics Hub 4 Web Load & Performance Testing Microsoft Fakes (Unit Test Isolation) Manual Testing with Microsoft Test Manager Exploratory Testing with Microsoft Test Manager Fast-forward for Manual Testing with Microsoft Test Manager Cross-platform Development Remoted iOS Simulator for Windows Share code between Android and iOS with Xamarin Native iOS and Android UI Designers Collaboration Tools and Features Team Explorer (third-party development tools support)

www.visualstudio.com


Смотрите также