i've got multiple microsoft accounts linked to multiple tenants. I've registered my first teams app (using the Office Toolkit functionality "Configure for SSO...") on the wrong tenant.
Is there some way to remove the stored credentials? I even tried making a new solution, but visual studio seems to have stored those credentials somewhere, just can't find where.
I am the engineer of VS extension of Teams Toolkit. We have identified this requirement from GitHub issue https://github.com/OfficeDev/TeamsFx/issues/1685, and will treat it as a new feature in the following release. So far, you can follow the workaround in that GitHub issue thread and thanks for your patience.
Only solution I could find.
Open Visual studio and go to Extensions -> Manage Extensions
Uninstall Teams toolkit
Install toolkit again
It should allow you to sign in again when you configure SSO
Related
I'm using the Visual Studio extension MAT 4.0 on VS2015 to localize some WPF and WinForms applications. As of May 1 (yesterday) the "Generate Machine Translations" feature stopped working. According to the exception message this is because the MS Translator service has been moved from DataMarket to Azure.
I've tried subscribing to the translation service on Azure (as instructed by the exception message), but I don't think MAT is using the logged in VS user's account. Still doesn't work.
TranslateApiException: Invalid authentication token. Microsoft DataMarket is retired. Please subscribe to Microsoft Translator, in the Cognitive Services section at https://portal.azure.com. Please visit https://cognitive.uservoice.com/knowledgebase/articles/1128340-announcements-action-required-before-april-30-20 to find detailed instructions. : ID=1230.V2_Soap.GetTranslations.4EAC0341
Apparently this move has been planned for some time, so I'm baffled as to why there isn't an update to the Toolkit.
Anybody have any insight on this?
The fix for MAT for VS 2017 is current in testing. The fix is being back ported to MAT for VS 2013 & VS 2015.
Please note that one key change is the need to have a Azure subscription as reported in the announcement. Setting up the free 2m char as it should cover the major of usage cases.
I will post here when the fix is ready as well as the instructions for connecting the provider to the Azure service.
UPDATE: The fix has been posted that uses the user provided Azure subscription. fixed versions is MAT 4.0.1610 (VS 2015/VS2013) and MAT 4.0.8610.0 (VS 2017).
After installing the update, you will need to supply the provider the access key or you will receive a message with a link to he instructions. The details are here: https://multilingualapptoolkit.uservoice.com/knowledgebase/articles/1167898
I have a Visual Studio subscription.
I'm trying to implement Application Insights in a Web API application in Visual Studio.
The wizard is trying to associate AI with my Visual Studio subscription. Rather, I want to integrate with my company's Azure subscription.
So, how is this done? Do I have to contact the Azure admin and add me to Azure? I have seen responses like "add you as a co-administrator". This is pretty dumb, when you're a developer.
Our company Azure subscription has Active Directory integration. So what. How do I register with the company Azure subscription that I want to implement services as a developer in the company??
Can someone provide some insight or references? The documentation is ponderous on this point.
If I understand your question correctly, you need to obtain an Instrumentation Key from a resource that is created in your company's Azure portal. Then, you can install application insights in your project and use that instrumentation key.
If, on the other hand you are asking why you have to be a co-administrator then you are correct. This was the case for a while but not anymore.
Account admin can now assign new users to specific resource groups. Each resource group can contain one or multiple resources. Read more: https://learn.microsoft.com/en-us/azure/active-directory/role-based-access-control-configure
I'm trying to test Azure by publishing a basic web app. After signing in to Azure from Visual Studio, I'm met with the following message:
Sorry but we didn't find any Windows Azure subscriptions associated with your account.
You can sign in with a different account or sign up for a Windows Azure subscription.
I use Windows 8 with an attached ecu account, and have signed up to a trial Azure account under the same credentials (which I can log in to normally fine).
Results[1] from a similar problem suggest the accounts are mixed up, and to contact an admin with the ticketing system to rectify[2]. However selecting "Having issues with sign in or signing up for an account?" links me to a page, which quickly redirects me to another broken page and I am unable to proceed.
What is the best course in action in either:
publishing the app to Azure
contacting Microsoft about fixing my trial Azure account
Thank you
[1] http://social.technet.microsoft.com/Forums/en-US/1b61b9a9-e763-4893-acc1-aa60a7d0b03d/msdn-subscriition-free-access-to-windows-azure-cannot-setup-account?forum=windowsazurepurchasing
[2] http://azure.microsoft.com/en-us/support/options/
Found the answer on social.technet.microsoft.com
I found this article first, so I hope this helps others that find this before the MS article.
https://social.technet.microsoft.com/Forums/azure/en-US/40ac7a3d-12f0-47c5-9cee-97dd5867ddf0/unable-to-sign-in-when-trying-to-publish-web-role-to-azure?forum=windowsazuredevelopment
I know this is an old thread, but I was recently having a problem with visual studio 2015 where I could not sign in to Azure. I came across this SO entry. It was not helpful, but I eventually did find the answer.
The answer was to repair Visual Studio. It takes awhile to run but once it finished I was back in business with Azure in Visual Studio.
https://msdn.microsoft.com/en-us/library/aa983433%28v=vs.90%29.aspx?f=255&MSPPError=-2147217396
My clients have bought an Office 365 SharePoint 2013 site and I'm in the process of configuring it.
Their business rules require a very complicated Workflow which can just about be developed in SharePoint Designer. However, as I'm an experienced Visual Studio .NET developer I'd rather do it programmatically and hopefully save some time.
At present I can't figure out how to connect my desktop version of Visual Studio to the Cloud-based SharePoint site. I've downloaded the Workflow Manager tool but I'm struggling to figure out how to configure the Farm Databases etc. Available documentation seems patchy.
Has anyone out there found a way of doing this? This link suggests that it might not be possible.
Thanks
Edward
According to this article it's possible, though probably not really nice.
You will have to deploy your Workflow as a SharePoint App. Which means you will only be able to call the webservices.
Another option which might be worth looking at is Nintex, which has a module for office 365 as well.
Nintex has alot of useful functions, though I don't know how good the office 365 version is.
You would have to check whether it suits your requirements.
I try to upgrade a plug-in that was on webaccess 2008. Whe were using WebAccessSession to get the user name of the current user logged (WebAccessSession.Current.Connection.UserName ). I Imagine now that it is in tfsConnection but I'm not sure.
Is there any documentation that tells what really changes between Team Foundation Server 2008 and Team Foundation Server 2010?
No documentaion that details things at the level that you are looking for I'm afraid. As far as I know, plugging in to Web Access is not supported via any specified API so any integration you have done yourself would be classed as unsupported so you'd be on your own when it comes to figuring those sorts of changes out. Sorry.
As far as your question about Web Access, this blog post from Hajan Eskci details what's happening with Web Access:
Team System Web Access in TFS 2010 Beta1
Until now, Team System Web Access was published as an out of band power tool. In this release and beyond, Web Access is now an integrated part of TFS, and it is installed by default when you install TFS.