I have a custom build task ready to go and I would like to upload it to my TFS server. I don't see much guidance out there for how to do this. Is there any way it can be uploaded through some kind of an "Add Task" workflow in the UI, or does it need to be done via the TFS2015 instance API?
Any step-by-step instructions would be appreciated.
FYI, I'm using the following visual studio template:
https://marketplace.visualstudio.com/items?itemName=JoshGarverick.VSTSExtensionProjectTemplates
I'd like to see it here:
If you have packaged the extension (custom build task), then just need to upload the extension VSIX files to TFS 2015 as mentioned by Daniel, then install the extension. After completed the installation the custome task step will displayed there.
Go to http://server:8080/tfs/_gallery/manage to upload the extension
Related
I want to execute a post-build script from TFS which copies a folder in my TFS to the Build drop location.
I have very little knowledge of how to do this.
Kindly provide with the code.
I am using VS2015, tfs 2015.
i also have VS 2013, TFS 2013
TFS 2015 Build has an out of the box template 'Visual Studio' that already does this using the PublishBuildArtifacts task.
Look at leveraging this task in your build def in order to accomplish what you are looking for.
https://msdn.microsoft.com/en-us/Library/vs/alm/Build/steps/utility/publish-build-artifacts
https://github.com/Microsoft/vso-agent-tasks/tree/master/Tasks/PublishBuildArtifacts
In XAML build, you can check in your script, and specify a post-build script path in your XAML build definition.
This script gathers some of the typical binary types from the typical locations and copies them to the folder from which TFBuild copies and drops to your staging location. Check more information about Run a script in your XAML build process at website: https://msdn.microsoft.com/library/dn376353%28v=vs.120%29.aspx
In vNext build, you can simply add a PublishBuildArtifacts task as Mr. Kraus mentions. About how to use this task, check: http://www.codewrecks.com/blog/index.php/2015/06/30/manage-artifacts-with-tfs-build-vnext/
We used to set up our dev machines to receive build notifications in the task bar.
However, the process we've followed - as per this description - doesn't apply any more with Visual Studio 2015 as the Build Notification app is no longer part of the package?
Any ideas what happened to it? Replacements? Work-arounds?
Update 4/2016: Nothing appears to have changed with Update 2 - new build definitions still don't show up..
The BuildNotificationApp is still a part of the VS 2015 and can be found here: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\BuildNotificationApp.exe. However, it looks like only XAML build definitions are visible to this tool.
The new vNext features can be accessed via the new REST API. I failed to find the explicit confirmation from the official source, but most likely the app was not made compliant with this new approach.
Basically, you have the mail notifications as the only option. Make sure the mail server settings are configured properly for the application tier, and create the appropriate email alert.
I am working with Virto Commerce server 2.4.561 and I'm having a great deal of difficulty successfully publishing to Azure from Visual Studio. Based on the documentation provided, it's not clear to me what the appropriate method is. Most guidance related to Azure assumes that I am using Git deployment. But in this case I am not. I am coding locally on my dev machine and I would like to be able to use web deployment to deploy directly to Azure from Visual Studio. However, the guidance found here seems to suggest that if you want to do your own deployment, you need to use deploy.cmd. I'm not exactly sure why that is. I can only guess that it has something to do with how the modules need to be packaged up.
I am able to run deploy.cmd and it appears to succeed, but I end up with an artifacts folder with 2,000+ files and folders in it and I am left to use old-school FTP to sync all those files up with the Azure website. Is this how it is meant to be done? I have tried to deploy directly from Visual Studio to Azure, and it appears to succeed, but the site does not behave correctly. Specifically, the custom modules I've built don't load correctly.
What is the right way to do this?
There is a way to publish your custom module directly from Visual Studio, but you still need a working Virto Commerce in Azure beforehand, and the easiest way to set it up is to use the Deploy to Azure button in GitHub.
In the Azure portal create a new virtual application /MyModule with
physical path site\wwwroot\admin\Modules\MyModule. It will be used
for publishing a custom module.
Download the source code from GitHub with the same version as you have published to Azure, add your custom module to the solution and build it.
In Visual Studio right-click on your module project and select Publish.
On the Profile screen select Microsoft Azure Web Apps as a publish target and select your Azure Web App.
On the Connection screen select Web Deploy as a publish method and add /Module to the site name. So your site name should look like this: myvc/MyModule.
On the Preview screen click the Start Preview button and make sure the file list contains only files related to your module and the action is Add for each of them.
When you click the Publish button, Visual Studio will upload all module files to the physical directory configured for the virtual application myvc/MyModule. For subsequent publishing it will upload only modified files.
Update: You should restart the Web App via the Azure portal after publishing in order to load the new version of your code into the application. Thanks to N1njaB0b for reminding.
I am a newbie in Visual Studio and have my projects deployed on Visual Studio Online. How can I download the successful build files from Visual Studio Online to my machine. Because as far as I know, after successful completion of the build, we can only download logs as zip file.
I know it is a bit late to answer this question, but in case someone still looking for solution, I used this one:
When creating build definition, in "Build Defaults" pane selected "Copy build output to the following Source Control folder".
In textbox I typed "$/[Your project root]/Drops" where [Your project root] is the root name of your project base.
After that I can build with this definition and in "Drops" folder start appearing folders with build results.
I know this old but I just had this problem. Assuming you have a task of "Publish Artifacts". You can click on the result of a build and there will be an Artifacts tab that let you download the folder created in the publish artifacts task mentioned.
When working on a website in Visual Studios and adding PDF files, they won't Publish to the site via the "Publish" command. Does this have something to do with the filetype?
Thanks in Advance,
CJ
You may need to change the build action to Content in the file's properties.
It's probably set to None at the moment, which will mean it isn't copied up in the publish process.