How can I use or just enable the REST API in an on-premise installation of TFS 2015? I only can find (a lot) information about using API with Visual Studio Online out there.
Most of the API's are there by default, but not all API's supported by VSO are supported by TFS, especially some of the API's currently under development, may not have shipped with TFS 2015. There is nothing you need to do in addition to "enable" these. They're just there.
Related
Does TFS 2008 support test management om Internet Explorer 11
Internet Explorer 11
TFS2008 is a very old server version and out of support for a long time( Released over 10 years).
Highly recommend you to move to a newly versioned TFS server. Detail process of the upgrade, you could take a look at my answer in this question: Migrate Project to TFS2018
There is not any official document which declare this related info. After go through Web portal supported browsers of Azure DevOps client compatibility:
To connect with the web portal, you can use the following browsers
with Azure DevOps Services and Azure DevOps on-premises. Edge,
Firefox, and Chrome automatically update themselves, so Azure DevOps
supports the most recent version.
Most of the Microsoft product support down-level compatibility, guess IE11 should be compatible with the web portal of TFS 2008. But not totally sure if test management also work properly. Better to double confirm this in your TFS environment.
Lastly, please upgrade your TFS 2008 to higher version which could get official support and some new features.
I need to develop an application for my distributed computing class, with one central server and multiple graphical clients. I was thinking of trying WCF for this, since I am already familiar with making .NET standalone desktop applications using Windows Forms or WPF.
Since I have never worked with WCF before, I am trying to follow a tutorial posted on MSDN, which has defining a service contract as its first major step.* Part of this involves creating a WCF Service Library project, which is supposed to be available as a template under the language of my choice (I am going to use C# here). However, I do not see this project template listed as an option in the new project dialog, and looking for WCF in the search bar returns no results.
How can I make this project template available for use in Visual Studio 2017?
* It should probably be noted that the tutorial mentions that it is written with Visual Studio 2012 in mind. Has anything changed since then that I should be aware of as far as the tutorial is concerned?
Open the installer, choose Individual Components and scroll down to Development Activities. Check the WCF checkbox:
I ended up re-running the Visual Studio Installer to modify my current setup. WCF is not explicitly listed anywhere, but I figured it might have been included as part of the .NET Core or ASP.NET workloads (which were not marked for installation the first time around). After adding these workloads to my installation and restarting Visual Studio 2017, I can now see the WCF project templates listed under C#.
Tried everything. Deploying same type of web project (Net.Core 1.1) with VS2015 at the very same location using exactly same parameters works without any problems.
Is there any known issue with release RC.4+26206?
This what my server log says:
IISWMSVC_AUTHORIZATION_SERVER_NOT_ALLOWED
Only Windows Administrators are allowed to connect using a server connection. Other users should use the 'Connect To Site or Application' task to be able to connect.
Process:WMSvc
User=sludr
Ok... Found a solution. Same reason as documented here: .net core web deploy requires admin permissions, so VS2017 requires right now a windows account of group Administrators to publish net core projects.
Hopefully this will be fixed soon.
Note: The official VS 2017 RTW still has this bug.
I have several build definitions setup in TFS 2012. They all use Web Deploy and Web Packages and deploy to my dev and test servers and work just fine.
I can't, however, figure out what the "deployed" tab in TFS Web Access > Builds is used for?
The 'deployed' tab seems to be related to Azure integration somehow.
I found this post on the TFS Deployer website. It's even possible to mark a build as 'deployed' via PowerShell, which seems quite interesting. It would be nice to have our deployed builds showing in that tab, and by integrating with TFS Deployer this seems possible.
I'm relatively new at creating custom content for Sharepoint 2010 and have been having some difficulty understanding how to get non-design related components (ie. web parts, custom classes, ...) into a Sharepoint site. I have created a new visual web part on the company's development server and deployed it successfully from Visual Studio 2010 and also packaged the solution into a WSP file.
What is the best way to go about getting that web part onto the production server? There is currently no Visual Studio install on the production server but from searching around I get the feeling that it might be possible to do this remotely using Powershell or STSADM. Has anyone faced a similar situation?
Use PowerShell. Stsadm is considered to be obsolete and is included in SharePoint 2010 only for backwards compatibility with SharePoint 2007. So, since you are new to SharePoint, pretend Stsadm doesn't even exist.
My PowerShell scripts keep evolving, but they are based on samples from Ted Pattison:
Chapter 2: SharePoint Foundation Development (scroll down to Using Windows PowerShell Scripts to Automate Tasks in Visual Studio)
PowerShell Boot Camp for SharePoint Professionals