AWS provides a Visual Studio extension, available in the marketplace, called “AWS Toolkit for Visual Studio”. This extension supports both VS 2017 and VS 2019. If you add this extension to Visual Studio, it provides quick access to many features, as well as including some additional templates for AWS focused projects. Figure 1 – Extensions for Visual Studio Code. The Extension pane opens up. On the search box, search for “AWS Toolkit” and hit Enter. The very first item on the list will be the AWS Toolkit extension. Select it and click on Install button: Figure 2 – Install AWS Toolkit for Visual Studio Code. Once the toolkit is installed on your. Microsoft Visual Studio 2017 is the version used in the examples. The AWS Toolkit for Visual Studio 2017. Download the latest version of AWS Toolkit for Visual Studio. If you have not already done so you will need to create an AWS account and a user profile which will be used by Visual Studio to upload your projects to AWS Lambda. For installing AWS Toolkit on Visual Studio Enterprise 2017 (15.7.4), I find Extensions and Update menu from Tools main menu, click Online menu (left side) and then type AWS Toolkit and press download. Then I close VS and VSIX installer start for installing AWS Toolkit. After while, it shows me a message like this.
Aws Toolkit For Visual Studio 2017 Not Working
| AWS Toolkit - unable to redeploy Posted on: Jan 7, 2020 6:29 AM | | This question is not answered. Answer it to earn points. |
I'm following the tutorial on how to deploy a .NET application to AWS (https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_NET.quickstart.html).
When I get to the 'Publish to Amazon web Services' dialog in the Visual Studio toolkit, the option to redeploy to an existing environment is disabled.
I've set up a profile and added the Access Key ID and Secret Key. Initially I tried using an IAM user, but it won't work even when I use the root access key. |
|
| Replies: 3 | Pages: 1 - Last Post: Apr 18, 2020 2:08 PM by: P. Johnson |
|
|---|
|
| Re: AWS Toolkit - unable to redeploy Posted on: Jan 7, 2020 8:53 AM | I am not sure from your description what is disabled.
If the radio button is enabled, but the 'Next' button is not, the environment needs to be 'Ready' and the actual environment to deploy to needs to be selected.
If, however, the redeploy radio button is disabled, then make sure that your account profile and region are set correctly. One of the most common problems is the region..
Edited by: DrNetAWS on Jan 7, 2020 8:54 AM |
|
|
| Re: AWS Toolkit - unable to redeploy Posted on: Jan 19, 2020 10:23 AM | I am experiencing a similar issue.
When attempting to redeploy a .net core 3.0 app using AWS Toolkit for Visual Studio 2019 the 'Redeploy to an existing environment' functionality is broken. For the most part, the redeploy radio button is disabled. When the screen first loads it shows a list of the existing environments to redeploy to but then as soon as the radio button is selected the list vanishes and the radio button becomes disabled. Closing & restarting the process often results in the radio button being disabled and the list being empty. Closing the Visual Studio Solution, and re-opening it resets the behavior. When the screen first loads again it shows the list of existing environments but as soon as an environment is selected the list quickly vanishes and the radio button returns to a disabled state.
Visual Studio Professional 2019
Version 16.4.3
AWS Toolkit for Visual Studio 2017 and 2019
Version: 1.15.2.1 |
|
|
| Re: AWS Toolkit - unable to redeploy Posted on: Apr 18, 2020 2:08 PM | I've had the same issue and found that switching to a different profile in the dropdown then switching back to the one I actually want to deploy with enables the redeploy radio button and populates the list.
Don't know why but it works for me.
You can just create another profile if you haven't got one already... as a heads up though, when I added my second profile I seem to remember it didn't add a carriage return from the last line of the default profile which corrupted my aws config file. I just went into the file and added a carriage return and a blank line between the profiles which fixed the issue.
Hope this helps. |
|
|
| | Answered question | | Unanswered question with answer points still available | | Unanswered question |
| Ace: 2000+ pts | | Expert: 750-1999 pts | | Guide: 300-749 pts | | Enthusiast: 50-299 pts | | Newbie: 5-49 pts | | Amazonian |
|
Visual Studio
Aws Toolkit For Visual Studio 2017 Tutorial
