Difference between revisions of "Nuget Package Repository"
(Added information regarding out package repository.) |
m (corrected spelling.) |
||
Line 1: | Line 1: | ||
− | eVision hosts an assortment of code libraries on our locally-hosted nuget repository. While the packages within our repository were not specifically designed to be consumed by third-parties, we have purposely left them publicly-accessible so that our clients can leverage some of our internal tools in order to | + | eVision hosts an assortment of code libraries on our locally-hosted nuget repository. While the packages within our repository were not specifically designed to be consumed by third-parties, we have purposely left them publicly-accessible so that our clients can leverage some of our internal tools in order to interact with the various systems that store and process their data. |
It is worth noting that these resources are the exact packages that we use within our internal projects, so these packages get tested fairly thoroughly and are well supported by our internal applications. While most of the packages don't have any documentation, there are some that include some degree of documentation in the format of VS-compatible "xmlcomments", which provide some level of documentation by way of Intellisense within Visual Studio. | It is worth noting that these resources are the exact packages that we use within our internal projects, so these packages get tested fairly thoroughly and are well supported by our internal applications. While most of the packages don't have any documentation, there are some that include some degree of documentation in the format of VS-compatible "xmlcomments", which provide some level of documentation by way of Intellisense within Visual Studio. |
Revision as of 14:59, 29 September 2014
eVision hosts an assortment of code libraries on our locally-hosted nuget repository. While the packages within our repository were not specifically designed to be consumed by third-parties, we have purposely left them publicly-accessible so that our clients can leverage some of our internal tools in order to interact with the various systems that store and process their data.
It is worth noting that these resources are the exact packages that we use within our internal projects, so these packages get tested fairly thoroughly and are well supported by our internal applications. While most of the packages don't have any documentation, there are some that include some degree of documentation in the format of VS-compatible "xmlcomments", which provide some level of documentation by way of Intellisense within Visual Studio.
Getting Started With Nuget
In order to consume our nuget packages within Visual Studio, you'll need to ensure that you have nuget installed. The nuget website is a great resource for getting started; we've provided some links below:
- http://docs.nuget.org/docs/start-here/installing-nuget
- http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog
Adding the eVision Repository
After installing nuget, it will need to be configured to use the eVision package repository in addition to the default. This will allow the eVision packages to show up in search results so that they can be added to your projects. The source for the package repository is http://nuget.evisionservices.com/nuget/Ensemble
. The repository is also accessible via the web, at http://nuget.evisionservices.com/feeds/Ensemble