With VS Update 4, we can now use Release Management with Visual Studio Online.
With Release Management server : no problem.
With Visual Studio Online : I can't manage to create a automated deployment.
My process always fail to "Deploy Step" with this log message "The given key was not present in the dictionary".
My environment is localized in different cloud service in Azure.
Do you have an idea of where the problem may come?
We are not supporting standard environments in VSO as of now and from the error message (which is bad), it looks like you are trying to run a release on a standard environment.
Recently we have blocked creation of new standard environments but have not touched the existing standard environments.
Can you please try running a release on a VNext azure environment & share whether it works for you or not?
Related
I am having a new issue when deploying Azure Cloud Services via Visual Studio 2015 SP1.
This is driving me up the wall and I am curious if anybody else has seen this? Basically, I can build just fine, I just can't package for or publish to a Cloud Service - the error is:
CloudServices232: The role MyProject.AsyncWorker is using an unsupported TargetFrameworkVersion v4.6.1.
This wasn't happen a few weeks ago, but now I can't publish it. Yes I am targeting .NET 4.6.1 - but that has been WORKING JUST FINE for a while now and I followed all the steps to run install.cmd and manually deploy it.
This appears to be a new build-time error (it used to be a warning).
I am setting up Visual studio online Release management and I am referring this link
https://www.visualstudio.com/en-us/get-started/build/hosted-agent-pool
to select Hosted Pool Agent in Visual studio online.. But it is missing for me.. I am refering this link in order to solve the below issue
Please help
Error
There are issues with the request or definition that will prevent the build from running:There are agents that are capable of running the build, but they are not online. If the agent is configured to run as a service, ensure that the "VSO Agent ({agent name})" service is running.The value specified for SourceVersion is not a valid commit id.
VS online release management does not yet work with hosted pool. You need to setup your own agents for a few more weeks until that support comes in.
I think I misunderstood the whole Azure development concept. I thought I could run the Visual Studio IDE within Internet Explorer or something along those lines.
You can, but you'll use an RDP client (like mstsc.exe) instead of internet explorer. You can create a Virtual Machine in Azure that has visual studio installed on it and develop on that VM. There are a number of images already in the platform that support this scenario if you're an MSDN subscriber, I believe.
Even if you're not an MSDN subscriber, you can create a VM and set it up for development yourself. Then you can use your remote desktop client to log into that machine from anywhere and develop on it instead of your local box. This isn't limited to a Window dev env't either, of course.
I use this in scenarios where I have a constrained laptop but good connectivity and a desire to get some work done. You could use this to develop with a full IDE from a Surface RT, e.g. :)
I think I misunderstanded the whole Azure development concept, I
thought I could run Visual Studio IDE within Internet Explorer or
something
Azure is a web hosting environment in a nutshell. I think you are talking about Visual Studio Online in which you can run VS IDE inside browser.
Once you finish writing code in Visual Studio Online, you can deploy it to Azure.
Visual-Studio-Online-Monaco
channel9 - Visual Studio Online Monaco
I've got an Visual Studio Team Services account, I was an "early adopter" and have only recently started being interested in the build features.
Everywhere seems to suggest that a hosted build controller is just there when you create a new build definition.
I'm getting a TF225001 error when I try to create a new build definition. I've searched high and low to try and find a way to fix this.
I've associated my Visual Studio Team Services account with my Azure account/subscription and can confirm that it's linked.
I've specifically set my Visual Studio Team Services login to be a member of the build administrators group and anything else specific to build.
I still get the error after logging in and logging out.
Is there a delay with linking an account to Azure and being able to see the hosted build controller?
Try the following troubleshooting steps:
Go to the Builds section of the Team Explorer toolbox in Visual Studio
Click Actions -> Manage Build Controllers
In the list you should see a controller named "Hosted Build Controller (Hosted)" and an agent named "Hosted Build Agent"
Select the controller, click Properties and ensure the Build Controller is enabled (don't worry if it's offline - that is normal - but it should be enabled)
Select the agent and do the same thing
Turns out there was an issue on the Microsoft end.
If anyone gets a TF225001 error when trying to create a new build definition and there aren't any build controllers in the manage build controllers window. You will need to contact the visual studio online product team.
They made a change to something which allowed me to see the Build Controller and that allowed me to create a build definition.
We are trying to evaluate and eventually migrate to the windows azure cloud platform.
I am stumbling on the installation process...
I'm currently following this tutorial.
I can't get the Windows development Fabric interface working like on this picture.
When I install the app fabric sdk (downloaded here) I get no .exe program to simulate the cloud...
I installed Windows AppFabric which is not what I need (I think).
I keep on being directed on AppPlatformInstaller which do not install what I need but I'm sure is part of my solution.
You are downloading wrong SDK. For Windows Azure Cloud platform you must download and install Windows Azure SDK And Tools for Visual Studio.
Then you will have a folder %Program Files%\Windows Azure SDK\v1.5\bin. There will be devfabric and devstore folders, under which the local development Frabric and Development Storage executables will reside.
Then if you are targeting .NET based solutions, you will have new project templates in Visual Studio, and everything shall be running smoothly. On the other hand, if you are targeting open source solutions you might want to follow the like provided by Ben.
As for Windows AppFabric - yes, it is wrong in terms that it is not related to Windows Azure at all.
Let us know if you have any issues when downloading and installing latest Windows Azure SDK And Tools for Visual Studio
You may want to check out the docs available from the Microsoft Interoperability Team. They maintain an entire site dedicated to running PHP on Windows Azure
http://azurephp.interoperabilitybridges.com/articles/build-and-deploy-a-windows-azure-php-application
Basically to get it working just install the Windows Azure SDK and with Windows Azure SDK for PHP. Build your PHP application and then run the package command. Your PHP application will be rolled into a Windows Azure project and launched in the local dev fabric