I've recently moved to a new computer and I am no longer able to see any of my alerts that I setup in Visual Studio 2010 and Alerts Explorer. However, I'm still receiving the alert emails when the events fire. I am using the same domain login and I have the same permissions (administrative permissions so that shouldn't be a problem). I have VS Power Tools installed (version 3.3.40818.0). I have the latest services packs & hot fixes installed for VS and TFS.
When I open the Alerts Explorer, I can only see one system event under the Build Alerts that I can't delete. I want to clean up the "spam" I'm receiving but I can't delete the alerts because I can't see it.
Without me having to go into the TFS database and fiddling around with tables and records I don't know much about - how do I get my alerts back in my Alerts Explorer? My old machine is not available anymore.
You can use the BisSubscribe tool (available on the TFS server) to unregister unwanted alerts, but unfortunately you'll need to search the database for the IDs of the alerts you want to remove. This post should give you directions: http://social.msdn.microsoft.com/Forums/pl-PL/tfsadmin/thread/01e7d1e2-2f5c-415f-81f3-a28e86be0c93.
Related
I understand that TFS Local Workspaces are designed to help users work more seamlessly when not connected to the TFS server; however, unlike when using Server Workspaces, I cannot see the status of a file from Visual Studio Source Control Explorer. Our team is connected to the TFS Server 90% of the time. It seems that Local Workspaces should be able to communicate file checked-out status back to the TFS Server when connected. As a team manager I would like to know what files team members currently have checked out in several scenarios, while still retaining the flexibility offered by Local Workspaces.
I want to know how often team members are checking in their code (or not).
I want to know if someone is already working on a file before checking it out as well.
I want to handle a lost/broken laptop scenario by knowing which files had un-checked-in changes.
Is there a way to do this with Visual Studio Source Control Explorer or another tool?
Generally the items checked out will display automatically when you navigate to the specific items in Source Control Explorer. Reference below screenshot.
I want to know how often team members are checking in their code (or
not).
You just need to check the changesets history.
I want to know if someone is already working on a file before checking it out as well.
Just navigate to the specific items in Source Control Explorer as I mentioned above, it will shown the status in Pending Change column.
I want to handle a lost/broken laptop scenario by knowing which files had un-checked-in changes.
Generally the files with status displayed under Pending Change column are the files which have un-checked-in changes.
However there is a tool called Team Foundation Sidekicks which is a suite of tools ( includes Code Review Sidekick, Shelveset Sidekick, Labels Sidekick, History Sidekick, Workspace Sidekick and Status) for TFS administrators and advanced users providing rich GUI for administrative and advanced version control tasks, you can use it to check and track the things you required. (Unfortunately it's no available for VS 2017, the latest version 6.0 only works for VS 2015)
We've created an Outlook add-in which integrates our custom CRM with Outlook. A command button is added to messages in read and compose mode. A function file is called on the button click.
The add-in manifest passes validation and installs properly on all machines. However on Outlook 2016 desktop (only) we are seeing an error on some machines. The exact error message says: “We’re sorry, we couldn’t access [NCS Outlook Add-in]. Make sure you have a network connection. If the problem continues, please try again later.” ([NCS Outlook Add-In] is the name of our add-in.)
Note that this message appears IMMEDIATELY after clicking the add-in command button. It does not first say “[NCS Outlook Add-in] is working on your request” like it add-ins do when an error has occurred.
We have tried Outlook logging and haven't found anything useful in the logs. We've checked settings and disabled other add-ins. We have also tested across machines with user accounts. The same user will have the error on one machine and not the other. In short, it seems that the error is machine specific and not profile related.
Version of Office 365 installed: 1705 (Build 8201.2209).
We experienced this exact behavior in Outlook 2016, the solution was to enable protected mode for the restricted and internet zones.
The easiest way to change this is in IE.
In Internet Explorer, click the Tools button, and then click Internet Options.
Click the Security tab, and then select the Restricted Sites Zone.
Select the Enable Protected Mode check box, and then click OK.
Restart Internet Explorer.
Here is a little more information:
https://support.microsoft.com/en-us/help/2761180/apps-for-office-don-t-start-if-you-disable-protected-mode-for-the-rest
Try this:
1) Close Outlook
2) Rename the folder C:\Users\%USERNAME%\AppData\Local\Microsoft\Outlook
to C:\Users\%USERNAME%\AppData\Local\Microsoft\Outlook.OLD
(Where %USERNAME% is current User Name.)
3) Start Outlook, Setup User Profile
4) Add/Test Add-In.
If that works, then something broken on old Outlook profile. But if same problem: Exit Outlook, delete the Outlook folder and rename Outlook.OLD back to Outlook.
I ran into this exact same problem after uninstalling Visual Studio 2015 on my development machine. (I had been using Visual Studio 2017 for Outlook add-in development.)
The problem went away as soon as I reinstalled Visual Studio 2017. The Outlook 2016 installation had nothing to do with the problem, I never changed Outlook or its profile at all.
This would indicate that the problem is somehow related to the SDK tooling on the machine...perhaps something to do with the .Net framework?
If I ran into this problem on a customer machine I would try reinstalling or repairing the .Net framework, or perhaps reinstalling Outlook (assuming it contains some add-in tooling that is broken.)
Just passing this on in case it helps anyone else.
We are just integrating Visual Studio Team Services as our new workflow and setting up automated builds on commits to master. Currently the individual who commits to master and instigates a new build will get a notification email when the build fails or succeeds.
We thought we would all get a notification but it does not appear that way. We have looked at notification settings in VSTS but have so far not found any setting that would allow all of us to be notified on build completion. Is there a setting we are missing or is this a feature that is not currently supported?
Notifications
The VSTS Build Succeeded notification can be customized to report only on certain statuses using the Filter Criteria options, by creating the subscription for a team or group the notification will be sent to all members of the group:
If you need more advanced filters, consider routing your notification to an alternate email address and point that to IFTTT or Microsoft Flow. Or using the Build notification step in Microsoft Flow directly.
Visual Studio CD tools
The VSTS CD Tools integrate build notification directly into Visual Studio. This results in a toast notification whenever you have Visual Studio open:
Catlight
Another great tool to get build notifications is Catlight, it runs from the task tray and will even notify you when Visual studio isn't open:
Siren of Shame
And a 4th option is Siren of Shame, which also offers integration with a USB emergency light that will start blinking when the build fails:
AnyStatus
AnyStatus is a notification tool that comes as a Visual Studio add-in, or stand-alone tray icon (desktop app) that will notify upon status of build changes.
It has support for many Continuous Integration systems, including TFS vNext.
Here's is the configuration screen for adding a new project:
Here is the status screen, which appears when clicking the tray icon:
Here is the tray icon (immediately after triggering a build):
The tray icon shows a tick when all builds are OK, and a red X when at least one has failed. It shows a 'play' icon when at least one build is in progress.
Maybe node-build-monitor could be interesting for you. We use it for our teams on a dedicated screen. But you can open it in a browser tab and enable desktop notifications, too.
It's open source with a lots of contributers and support for many services.
https://marcells.github.io/node-build-monitor
If anyone is getting the dreaded "An error occurred while sending the request." with Catlight, try running it as administrator. Fixed it for us.
Visual Studio 2015
Visual Studio 2013
Until recently used TFS for source control with Microsoft live id with my yahoo email.
Recent transition from TFS to VSTS.
Couple weeks ago devops switched my VSTS account to use company email instead of yahoo email.
After that in VS I couldn't use source control anymore,
was getting error: "TF30063: You are not authorized to access usga.visualstudio.com\DefaultCollection."
and not being able to bind to source control.
Devops removed my company-email-account and reactivated my yahoo-email-account
and source control in VS started to work again, and with VSTS now.
I have not used Visual Studio for a week or so.
Today I discovered that:
My solutions lost Source Control Bindings.
I can Not bind my solutions to Source Control Again in Visual Studio.
When I re-bind it tells me that status is 'invalid'.
I do Not get any other errors.
Happens for all solutions that used to work fine with source control.
I seem to have access to www.visualstudio.com -> mycompany.visualstudio.com
and can see my projects there.
Please help me to undestand what is going on and rebind.
Many thanks
This should be a cache related issue, try to delete VS and TFS cache and restart VS.
Also try to remove your account info which stored in Credential Manager （Control Panel-All Control Panel Items-Credential Manager-Windows Manager）
Then reconnect to VSTS in Visual Studio use your personal account, make sure selected the used workspace, get latest; or directly delete the old workspace, create a new one.
My issue was resolved the following way:
1. when I've started to use TFS four years ago, I've created Microsoft Live Id account using my Personal email
this year when our devops were switching us from TFS to VSTS
they have tried to enforce rule of everybody to use their Office email for MS Live Id account. So they have created new account for me with Office email
Then I have described issues
Problem was resolved by switching me back to using original MS account with my Personal email.
And
I had to delete existing workspaces in Visual Studio 2015
and create new ones for my solutions to rebind code to VSTS.
For some reason I had to repeat this process few times.
Hope it helps
Earlier this year I successfully deployed a MVC app to Azure from Visual Studio.
Now I'm trying to do the same thing again, but now I am told my azure account "has no subscription".
However I am 100% positive I do have a subscription associated with my email. My old MVC app still runs and I can see my Pay-as-you-go is properly charged.
What I Have tried to fix it
Emptied my browser caches, history, cookies etc.
Removed my account from Visual Studio, restarted, and added them again.
Formatted my computer and reinstalled everything (not really because of this problem, but the timing was perfect).
Updated the Azure SDK to the newest 2.9.5.
I did the following things above based on advice from these pages:
Visual Studio not finding my Azure subscriptions
Unable to publish to Azure with VS2015
No subscription found in windows azure account
But alas, no luck.
The only thing that comes to thought is I tried to add an Azure Pass to my account, but without luck. But I can't see how that should change anything...
So my question is: How do I make Visual Studio recognize my current Pay-as-you-go subscription, so I can publish my services, apps, etc. from Visual Studio directly?
Or at least: What has gone wrong? Whom can I contact to get help with this?
As always, thank you for your time and patience, and please write a comment if you need further information.
You may try to connect first via the server explorer (ctrl+alt+s). (The server explorer has an azure root node, if the azure sdk installed)
If you have connected, the publish wizard won't ask (usually) for sign in again.
In my case, the solution was as follows:
Open Server Explorer in Visual Studio, right-click on Azure and select "Manage and filter subscriptions":
Screenshot of Manage Subscriptions Dialog
Click the Certificates tab, click Import, then click Download subscription file. This will take you to the azure portal page where you can download a .publishsettings file for your subscription. After downloading that file, click the Browse button in the Import dialog shown above and select that file.
I had the same issue. To solve it I opened the server explorer (ctrl+alt+s) and refreshed the Azure connection. It still said 0 subscriptions, but in the publishing options I could connect without any issue.