One of my coworkers created a bot with Microsoft Bot Framework and we started to use it as an organization app. He created the manifest in his teams account within App Studio. I'll continue to work on that bot, so i want to see the app in my App Studio manifest editor. How can we change the owner of the app without changing app id ?
If the coworker is still around, then inside App Studio there is an option to Download the manifest. In your own App Studio instance, there's an option then to "upload" a manifest. Just for information, the app can be in both of your App Studios at the same time, because having it there is not really registering it in Teams or anything like that.
Ideally, to really use it inside your organisation, you should deploy it to your internal company catalog properly, so that it is visible more widely, can be upgraded independently, etc., rather than using App Studio to deploy, for exactly the reasons you're running into. To do that, inside the "App store" there's an option on bottom of the left menu to upload for the entire company.
Related
There are lots of examples of people having a similar problem to mine, but none of them are the problem that I'm having.
I'm running the Community edition of Visual Studio 2019 (maybe that's the problem). I've already created a free Azure account using the same username/pw/email as the account that I have the version of Visual Studio installed as (note that Azure didn't used to support Core, but it does now).
I'm following this Microsoft Doc on how to create a ASP.NET Core web app with Azure. I've created the project, and it's time to "publish" the web app.
Seems simple: right click on the project >> Publish. Here is the first window, where I should make sure that App Service is highlighted, then hit Create New and Create Profile.
In the next window I can either create my Azure account (which I already have) or sign in. This option seems strange, being that I'm clearly already signed in. Perhaps they mean signed into Azure? In any case, I choose "Already have an account (sign in)" because I do. If I were to choose the first option to create an account, it would tell me that I already have an account.
Next, it asks me to sign into Microsoft Visual Studio account (of which I'm already signed in -- my picture is on the upper right corner of the IDE). I do it anyways:
Next I put in the password (I'll spare you this screenshot -- I showed the last one to illustrate that it wanted me to sign into Visual Studio when I'm already signed in), and...
Nothing.
It takes me back to the App service window. According to the Microsoft doc, the wizard should continue to creating the resource group.
What I've tried:
getting to "Publish" without signing into Visual Studio
getting to "Publish" without signing into Azure (note that the email/pw associated with the Azure account is the same as my Visual Studio account, and I have access to the Azure account; I can go to the Dashboard, at least)
and every variation of being signed into one and not the other or none or both
repeated the entire thing while running Visual Studio 2019 as admin
from the "Pick a publish target" window selecting select existing instead of create new. It takes me to the same window that create new does
instead of .NET Core, using just plain old .NET Framework 4.7.2
What I haven't tried
Uninstalling and reinstalling the Azure SDKs. I'm scared if I do that, then Microsoft won't let me re-install them (because I already have once), and besides, this seems to be a problem with signing in.
Maybe there's some config that I'm missing, either in Visual Studio or Azure?
Maybe it's because I'm using the free Visual Studio version AND the free Azure?
Maybe it knows that I'm laid off and broke, and just wants to push the nail in?
I'm stuck. Does anyone know anything about this?
This question involves both Azure accounts and Visual Studio.To deal with this problem, we can start with these two aspects.
First, we can publish the created project using FTP. If the project runs normally, it means that there is no problem with the free subscription account. The problem may appear on VS.
Second, we can devenv.exe / resetuserdata to clear the personal account cache information on Visual Studio.
I solved the problem, just enable yours directories in visual studio 2019.
Thanks :)
I solved this problem.
After 30 days of a free trial account, when you want to deploy for example a new Azure app service you can see the label "(disabled) free". This is why you cannot proceed with Visual Studio publishing anymore.
I had the same problem with you. I created a new Microsoft account and then a new Azure account. Now Visual Studio allows me to proceed with creating a new profile in order to publish my app.
I hope I helped you.
Since Azure is being updated rather often, I have yet to find an updated guide on how to do remote Azure debugging specifically for Visual Studio 2017.
I would simply like to know how to attach to the process running on the Azure server so that I can debug my web app.
If you are talking about debugging a web site or api hosted in app service or service fabric, you should try using Cloud Explorer. My experiences with it have been very good.
Its pretty simple. When you open up Cloud Explorer, it shows all subscriptions and resources available to your account(s). When opening e.g. the app services for your subscription, you deployed application will be visible. You can then simply right click and say "attach debugger", as can be seen here:
You can add multiple accounts to visual studio, and select the one that has access to the resource.
This is a more extensive tutorial on how to use the Cloud Explorer:
https://learn.microsoft.com/en-us/azure/vs-azure-tools-resources-managing-with-cloud-explorer
There were different ways of doing this, but I think a few of them are outdated.
Anyways, this is what worked for me:
Turn on Remote Debugging under Azure Portal -> Your web app -> Application Settings
Attach to the process in Visual Studio 2017 -> Debug -> Attach to Process.. -> Input YourWebAppName.azurewebsites.net:4020 and hit
ENTER
It'll ask for credentials. My AD credentials did not work here, which brings us to step 4..
Azure Portal -> Overview -> Get publish profile. It'll download the publish profile for your web site. In that file, you'll find
msdeploySite, userName and userPWD. Use them for step 2.
You should now be able to see the w3wp process and attach your debugger to it.
These answers/sites helped me find the solution:
https://blogs.msdn.microsoft.com/benjaminperkins/2017/01/09/cannot-publish-to-soveriegn-cloud/
https://blogs.msdn.microsoft.com/benjaminperkins/2017/06/06/remote-debug-your-azure-app-service-2017-including-asp-net-core/
https://stackoverflow.com/a/35738995/2504659
I have different accounts with different VSO subscriptions. I'm trying to connect to a different account (from the one I'm logged in VS-2015) so that I can check in code in the repository that I have in that account. But when trying this, Visual Studio brings me to the profile website, from which is basically a dead end - what am I supposed to do from there?
The "Connect to Team Foundation Server screen sometimes just freezes after authentication, and doesn't go anywhere from there.
So clearing the settings file, which is named CurrentSettings usually in the folder C:\Users\your user name \Documents\Visual Studio 2015\Settings (Windows) - helped get passed this issue.
Also, when you are brought to the VSO Profile page (the one I showed in my picture question) you have to select the project you are trying to open.
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.
I am new to publishing to Azure websites straight from Visual Studio. I am running VS 2015, have setup my Azure website with 1 channel so far and have successfully published to the website. I then, went about my week (several reboots) and finally came back to the project, made some changes then tried to publish with the saved publish settings. The password was missing! And, as you know, it is not really a password but rather the hash of the password.
How do you save this information so you are not forced to build a new publish every time you restart Visual Studio? I now have a half dozen publish profiles, all for the one site!
In your publish profile, next to Resource Group, click "Manage in
Cloud Explorer".
In Cloud Explorer, navigate to your App Service.
In the bottom window, click "Download Publish Profile".
In this file you can find your password.
Make sure you are signed in with your azure account by entering your credentials every so often.
If you are signed in, try not changing or clicking on the password field. Just click on publish without touching the previous info.
I always either import the XML from Azure Web portal, or I select the website by signing into Azure in Visual Studio.
Please let me know if this helped.