I was previously using Team Foundation services free account on the cloud with my Hotmail account. Now I am try to install TFS on a server computer. Everything worked fine. But then I noticed that I dont see the "Process" Menu option in my on Premise TFS account, while this shows up in the other account.
So, how can I enable "Process" menu option in my On Premise TFS web portal? So that I can configure the Work Item types and the process.
Below is my snapshot of my cloud account that does have the "Process" menu option.
While here is the image of On Premises account that has a very simple menu option.
The Process option menu only shows in Team Services (the cloud), there isn’t this option in On-Premises TFS web portal.
If you work in an on-premises TFS, and want to customize a process template,
you can download the zipped template file using the Process Template Manager. You'll need to use a version of Visual Studio that is at the same version level as TFS. You can install the latest version of Visual Studio Community for free.
Please see Upload or download a process template and Customize a process template for details.
To configure the Work Item types and the process please see Add or modify a work item type.
Related
I need to add a colleague to my development environment (specifically VisualStudioOnline - TFS) and the doc I've read about how to do this shows differently than what I see when I try.
I am the only user of Visual Studio 2012 in my small company. I am using Visual Studio Online for Source Control (as I understand it, this exposes Microsoft Visual Studio Team Foundation Service - Version 15.115.26417.0 as a "service" (i.e. this is the cloud...there is no on-premise TFS installed). Currently, I am using a LOCAL workspace (the default) and TFVC (not GIT).
I added my NewUserA to the Administrators group on the dev server. When click menu item Team to Connect to TFS, I am prompted to sign-in with my "Microsoft" account.
However, when I try to add NewUserA to my TFS, the dialog below seems unable to search for the existence of NewUserA:
It seems to want an "identity" of NewUserA (which suggests an email address too) so it sort of makes sense that this prompt does not look for locally added Windows users.
I am quite confused and would appreciate being helped thru this.
If your VSTS account isn't connected to Azure Active Directory and you're not synchronizing your on-premises AD to AAD, then of course it won't be able to find users from your on-prem domain. If that's the case, you can add users by email address and they'll be prompted to sign up for a Microsoft account (if they don't already have one) using that address. This is different than an organizational account, which is what you'd use if you were connected to Azure AD.
I have a question about Sharepoint Online debugging.
I've created a Sharepoint app with Visual 2015, destined to sharepoint-online and it's sharepoint hosted. Inside, I have a very simple workflow.
When I try to debug it, the following message appears:
Is it necessary to have an Azure account to debug a workflow? Are there any other options in workflow development?
If it helps, the deployment environment is Office 365.
It is necessary to have an Azure account to debug SharePoint Online/Office 365 workflows. This is because you can't access certain components that are used for debugging a local SharePoint workflow. Instead Microsoft created the Relay Service component of the Microsoft Azure Service Bus. (A secure component that they charge for hosting)
Before this component was released it does't appear debugging was possible. (See article below)
Debugging Workflows In SharePoint 2013 Online using Azure.
If you have an MSDN subscription or work for a Microsoft partner organization you should receive some free access to Azure.
Workflow debugging for SharePoint Online requires a Windows Azure Service Bus connection.
To enable remote debugging:
With a project selected in Solution Explorer, Right click on the Project menu ans select Properties.
Click the Debug tab.
Select the Use remote machine check box.
In the Use remote machine field, enter the name of the remote machine, using the format \\domain\machinename.
I'm running Visual Studio 2013 Premium and I've installed Microsoft Azure Tools for Microsoft Visual Studio 2013 v 2.5. I'm signed in with my Microsoft Account that also has admin permission in my Azure subscription.
The problem is that I can't see any web apps in the server explorer; I want to try remote debugging. I see a bunch of other Azure artifacts, but no web apps. Service bus and SQL databases lists content I expect. In screenshots I've seen on various MSDN posts, there should be a separate web apps node. I see an App Services node that doesn't list anything. All web apps are listed when I go to manage.windowsazure.com and portal.azure.com.
The App Service node has a context menu that allows me to create a new site. I did that and things got created correctly but nothing is displayed under the node.
This problem exists on both my home machine and work machine; both running a version of Windows 8.1. On my home machine I've re-installed the Azure tools without any effect.
I thought this too, for months. They renamed web sites to web apps, and are still seemingly renaming/moving things around. I just discovered my web site now live in Azure\App Service\<resource group> within Server Explorer. I can't see the individual slots, though I don't know or remember if that was possible previously...
I'm having a similar issue. Mine is a bit more complicated in that I have multiple subscriptions and the App Service node under Azure is only displaying the app service (web site) for my MSDN subscription but nothing from my corporate subscriptions. Yet all the other nodes like SQL Databases does show the complete list across all subscriptions.
Fixed! I updated the Azure tools to version 2.6 (I had 2.5). I then right-clicked on the Azure node and selected "Manage and Filter Azure Subscriptions". I made sure that all my subscriptions were selected and then clicked the tab "Regions" and made sure all the regions were also selected. I previously had filtered the regions to only North America as I have no intentions of creating a website in Asia...;)
After I saved the changes the Azure node refreshed and all the sites appeared as expected. I think the core issue was the filtering of the regions. Even though all my sites are located in Central-US and that check box was clicked, it wasn't until I removed all filtering for Regions that my sites finally appeared.
I created a website in the Azure portal, but now I can't find out how to import this into a TFS project. I have visual studio 2013. They seem completely disconnected in terms of importing a project from what the Azure portal creates. Thanks!
Jerelo - the way you solve your issue depends what type of website you deployed and how it was deployed originally. Many of the pre-baked Website images for items like Drupal or Wordpess are not designed to be imported into TFS and auto-deployed.
You would need to download your files via FTP (http://blogs.msdn.com/b/kaushal/archive/2014/08/02/microsoft-azure-web-site-connect-to-your-site-via-ftp-and-upload-download-files.aspx) and then setup source-control deployments by selecting the "Set up deployment from source control" option in the Portal.
Visual Studio Online is the only TFS source you'll be able to use right now, otherwise you have Dropbox, Git or Mercurial deployments Detailed options are listed here: https://github.com/Azure/azure-content/blob/master/articles/web-sites-deploy.md
I have a single web project that I want deploy in Azure.
I want to create one IIS web site per country and I want to be able to deploy each web site independently (not all of them at a time). How to do this?
Well,
you have two options:
Use Windows Azure WebSites to host your websites
Use Windows Azure Accelerator for WebRoles or your own project similar to that approach.
However you have to note that the second option is a project that is no longer being supported due to avialability of Azure Websites. With Azure Websites, you can have almost everything you get with the Accelerator. You can host your websites on a dedicated instances, and manage them individually. You can update/deploy your website data via FTP/GIT/TFS/WebDeploy, whichever method you are most happy with. The only downside of websites which I see, is the lack of Startup Tasks and the ability to customize your environment (Windows, IIS settings, etc).
When you have set up your Azure account you can go the the web sites section and start the construction of your Azure web spaces, the interface in the preview is very straight forward to use and intuitive.
For deployment using the publish command in from Visual Studio 2012 (which I found the easiest) here are the steps you will need to undertake:
For each of your countries you will need to set up the web site
in azure.
Then for each of those web sites you have created go
to their dashboard page and download the publish profile settings.
It is these settings that you can import into you Visual Studio
solution by selecting the publish command and browsing for the
settings profile file you downloaded and importing it.
Then in future when
you right click on the web site in your solution and select publish
it will publish to your web site in Azure.
I have created a fictional website for Spain below is the link you will need in order to initiate a publish from Visual Studio.
------------ EDIT -------------
For Visual Studio 2010 I met some difficulties trying to publish, in fact the publish profile you can download was not importable to Visual Studio 2010, well at least I could not figure it out.
Instead I created a deployment user by clicking on the 'Reset Deployment Credentials' link on the Azure dashboard (see the link in the image), created the user and then published via FTP from Visual Studio 2010.
What I would like to flag up is the maintenance issue of having one site for each country rather than one site with Localization, (if it is a language issue). A small change multiplied just 20 times for 20 different countries becomes a larger task and if you have lots of little changes it soon becomes a large task to maintain them all.