To deploy and publish a website in visual studio I get a message telling "the solution needs to be under source control on VSTS or GitHub".
what if I ignore this kind of publishing and publish it as before versions of VS and how can I ignore it?
Chick the publish Button next to Profile and not the Start button. They are 2 different publish options.
Related
Using Visual Studio 2017 with Data Lake Tools v. 2.3.1000.1, I am unable to submit a U-SQL job directly to Azure. I only have the option to submit locally:
This is the case even though I am connected to Azure through the "Server Explorer" tool window, from which I can access my U-SQL databases, view jobs that were previously submitted to Azure, etc.:
Using Visual Studio 2015, I have no such issue:
Am I forgetting a setting or a property somewhere, or is this perhaps a bug in Data Lake Tools for VS2017?
Do you still have the issue?
I sometimes see this happen if I open an existing solution and the tabs are already open, and I have not yet logged in. I then log in and the drop down menu of the open window will not be refreshed.
I close and reopen the script and it normally shows up.
Another reason, that I think will be addressed soon, could be that you have a filter on your cloud view explorer on which subscriptions you expose. If you hid the subscription there with your ADLA account, you will not see it in the pull down.
In any case, please let us know if you still have the issue and none of the two suggestions help.
I am trying to deploy an application to aws from within visual studio (2017), but the publish and publish to aws beanstalk options do not appear when I right click the project in the solution explorer. I have installed the aws toolkit, and when working with other projects, the options are present. I'm still new to visual studio, so it's possible I'm missing a simple step, but any help would be appreciated, as I have spent several hours searching for an answer.
I am trying to take an existing .net core API project and run it as a lambda function (Which should be possible).
I have installed the VS 2017 SDK for AWS. While following tutorials, I am supposed to be able to right click my project and select deploy to AWS Lambda. The only option I have is "Publish To Elastic Beanstalk"
However, when I create a brand new empty function in Visual Studio (New Project). I do have the ability to Publish To Lambda
But I can't seem to figure out the difference between the projects. Every nuget/tooling reference between the two projects is identical when it comes to AWS Packages.
My answer was the following, in my csproj I had the following line :
<DotNetCliToolReference Include="Amazon.Lambda.Tools " Version="1.5.0" />
Notice there is a small space after Tools. No complains from VS though so it was super hard to spot, and only exists because you have to edit the csproj manually when adding DotNetCliTools.
I would like to build in Visual Studio Online and then Web Publish to Amazon.
Is this possible? Or does it only publish to Azure?
It publishes to wherever you like.
Use the PowerShell, Batch, or ShellScript task to deploy to whatever system you like in whatever way that you want.
Better yet, create a professional release pipeline with release management and deploy to many environments.
I ran MSBuild with the following parameters added...
/P:DeployOnBuild=True
/P:DeployTarget=MSDeployPublish
/P:DeployIISAppPath=MyWebsite
/P:AllowUntrustedCertificate=True
/P:MSDeployPublishMethod=WMSvc
/P:CreatePackageOnPublish=True
/P:MsDeployServiceUrl=https://DOMAIN/MsDeploy.axd
/P:UserName=User1
/P:Password=******
I have taken a look at alerts management for TFS 2012 after installing power tools, and I can see about four types of alert templates:
Work Item
Code Review
Check In
Build
I was wondering if there was a possibility of having a supported way to register alerts under “Publish” event-type, manageable directly via the Alerts explorer.
If not, I thought of some workarounds:
If this cannot be done and managed via the Alerts explorer, can I customize an alert to be triggered on Publish event via a Web Service? If so, does the TFS API support such customization?
I can also instead go with a continuous delivery approach and set an automated publish upon successful build of a solution, with an email alert on Build-Event Success (which would also mean that a solution has been published).
Which approach would be a supported way for setting "on publish"-event alerts for web solutions via TFS?
My suggestion would be not to use the Publish in Visual Studio but instead to use a Build to publish your solution (either triggered on check-in, or manually triggered). Then you can easily setup an alert on that build. Using a build instead of VS-Publish is also considered a better practice because it gives you more power and flexibility for the deployment process.