Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/onlyutkarsh/AppVeyorExtension

AppVeyor extension for Visual Studio
https://github.com/onlyutkarsh/AppVeyorExtension

appveyor extension visual-studio

Last synced: 2 months ago
JSON representation

AppVeyor extension for Visual Studio

Host: GitHub
URL: https://github.com/onlyutkarsh/AppVeyorExtension
Owner: onlyutkarsh
Created: 2015-10-17T21:29:25.000Z (over 9 years ago)
Default Branch: master
Last Pushed: 2023-04-16T19:44:01.000Z (almost 2 years ago)
Last Synced: 2024-08-04T09:02:56.954Z (6 months ago)
Topics: appveyor, extension, visual-studio
Language: C#
Homepage: https://marketplace.visualstudio.com/items?itemName=UtkarshShigihalliandTarunArora.AppVeyorExtensionforVisualStudio
Size: 199 KB
Stars: 15
Watchers: 6
Forks: 4
Open Issues: 6
Metadata Files:
- Readme: README.md

Awesome Lists containing this project

README

        # Introduction #

[AppVeyor](http://www.appveyor.com/) is a well known cloud build server, which integrates with many source controls like VSO (Visual Studio Online), GitHub, BitBucket etc. Like many others do, we love Appveyor. However, most of the time we spend our time in Visual Studio and interacting with Appveyor was not possible from within Visual Studio. So we decided to build an extension!

> [**Download**](https://marketplace.visualstudio.com/items?itemName=UtkarshShigihalliandTarunArora.AppVeyorExtensionforVisualStudio) from VS Marketplace.

> 

![](_Screenshots/appveyor_toolwindow_full_annotate.jpg)

## Note ##

- The extension is developed in Visual Studio 2013 using [VS2013 SDK](https://www.microsoft.com/en-gb/download/details.aspx?id=40758).

- We use [PostSharp](https://www.postsharp.net) to handle exceptions in our extension. If you do not have license, please remove `[HandleException]` attribute from the methods.

## Defects/ Issues? ##

Please [raise a issue](https://github.com/onlyutkarsh/AppVeyorExtension/issues/new) and we will try our best to address and fix the issue.

Alternatively you can **contribute** the fix send the pull request :-)