:: تكنو ماسي ::
Microsoft Visual Studio Team Foundation Server 2015 Update 2.1
Idea to app
Includes code repositories, continuous integration, bug and task tracking, and agile planning tools
Work in any ********, including ****, Python, HTML5, **********, C#, and many more
Use Visual Studio, Eclipse, Xcode, or your own IDE or code editor - works with any Git client
Collaboration tools for the entire team
Team Foundation Server provides a set of collaboration tools that work with your existing IDE or editor, so your Team can work effectively on software projects of all shapes and sizes.
Unlimited, private, secure
Store and collaborate on code with unlimited private repositories. Use Git for distributed version control to maximize collaboration or use Team Foundation version control (TFVC) for centralized version control. Collaborate on code easily with pull requests and code reviews, while defining and managing permissions to secure your repositories.
Kanban, Scrum, dashboards
Be agile, on your terms. Capture, prioritize, and track work with backlogs and customizable Kanban boards. Work items link directly to code to ensure transparency, and can be used to build rich dashboards for easy reporting.
Build, validate, deploy
Catch quality issues early with continuous integration (CI) builds that compile and test your application automatically after any code change. Use continuous delivery to automatically deploy applications or websites that pass tests or model your release pipelines to match your existing release processes.
Eclipse, Xcode, and more
Use your favorite ******** and development tool. Version control supports any ********, as well as any Git client (including Xcode). **** teams can access code and work items through a free plugin for Eclipse - and run continuous integration builds based on config files from Ant or Mavin.
Open and extensible
We make it easy to integrate your custom tool or third-party service with Team Foundation Server using open standards like REST APIs and OAuth 2.0. We also support a set of ready-made integrations that can be easily configured from your account dashboard.
What's New in Update 2.1:
* FIXED BUGS:
* Agile Tools:
* On product backlog, if the mapping view is off and the work item Add Panel (quick create) isn't open, you will receive an error when you bulk edit work items by selecting Edit selected work items(s)... in the context menu. You can dismiss the error and try again, and the operation will succeed. The error message resembles the following: 'Cannot read property '-105' of undefined'
* In Internet Explorer, you are unable to use the button to maximize a long text field or use the save button after you edit the text in a work item. You receive the following error message: '******5007: Unable to get property '********' of undefined or null reference.'
* When you use the Client Object Model (or any of the tools that use Client Object model. For example, Visual Studio or your custom tool), you are unable to save large attachments to work items, even though the same attachments work fine with web-access forms.
* When you use hyperlinks in work item templates, they don't appear in web access. The hyperlinks work correctly in Visual Studio.
* In Safari and Chrome under some circumstances, if you go to the backlog and right-click on a work item and try to assign or move to an iteration, the menu doesn't appear.
* In Simplified Chinese, Traditional Chinese, Japanese, and Korean ********s model, Build does not work.
* During Test Results publishing, XAML builds may result in failures due to the COMException in BeginDataStoreInit() function. This is resolved by resetting the TFS cache on the build server.
* If you have a build definition that has a gated check-in trigger, and you create a draft of that same definition and then try to trigger a build by making a check-in, you receive the following error message: ' Your check-in validation could not be queued for build definition. Details: An item with the same key has already been added.'
* If you create a Maven build task, and you use SonarQube together with Maven, you see your credential in the build. This issue occurs only if you turn on debug and have a password that includes a backslash () or a double quotation mark (").
* After you upgrade to Team Foundation Server 2015 Update 2, You may see performance degradation because of QueryBuildInformation.
* Extensions with cross platform Build tasks do not work.
* The Backup tool has failures if the tlog backup is longer than 100 minutes.
* You cannot upgrade if IIS_USRS does not have the right "Impersonate a client after authentication". During Readiness Checks in the Upgrade Wizard, you receive the following error message: ' VS402818:The built-in security group IIS_IUSRS does not have the required user right 'Impersonate a client after authentication'. Grant this user right to the IIS_IUSRS group and then re-run the readiness check.'
* In the activity log, the parameters are blank for some failed commands.
* "Trial" has been removed from the name of the download from VisualStudio.com.
* Web experiences do not work correctly if a TFS Server is configured to be accessible through both HTTP and HTTPS.
* Version Control:
* An event log error may be logged every time when a user leave a code comment on changesets or shelvesets.
* Team Foundation Version Control displays a GUID in the usernames in code review emails.
* If there are multiple build definitions configured for the repository, the status badge might show the wrong build definition name for the build
* When you create a pull request, the associated work items list only includes the first 25 commits instead of inspecting all the commits in the pull request.
* When you add a link from a work item to a version control item at latest, the link is broken and appears as "vstfs:///VersionControl/LatestItemVersion/undefined"
* In Team Foundation Version Control, if you branch across projects or move a branch to another project, your branch may lose its parent relationship.
* Test Tools:
* When you upgrade Team Foundation Server 2015 Update 2 RC to Update 2 RTW, you cannot see the option to use Test Plans in the "Run Functional Tests" task.
* Extensions that work in Visual Studio Team Services and deliver content (HTML, **********, CSS, and so on.) from their own service or domain may not work in on-premises Team Foundation Server. You may receive the following error message: 'resource from origin has been blocked from loading by cross-origin Resource Sharing policy'
* Release Management:
* The email option in the release management approvals are not enabled if there is more than one approver in an environment.
* Security in release environments are too strict. Denying access to one environment may restrict it in others.
* You may not consistently receive code review *****s.
* If your Team project has a space, your notifications may have invalid links.
Buy Premium From My Links To Get Resumable Support,Max Speed & Support Me
Download ( NitroFlare )
Download ( Uploaded )
Download ( Rapidgator )
Microsoft Visual Studio Team Foundation Server 2015 Update 2>1