Nuget Package Repository - Revision history

Sowens at 19:07, 1 August 2016

2016-08-01T19:07:07Z

Jshearer: Updated feed instructions.

2016-03-01T05:32:49Z

Updated feed instructions.

Jshearer: Adding itemized instructions.

2014-12-10T16:16:44Z

Adding itemized instructions.

Jshearer: corrected spelling.

2014-09-29T18:59:12Z

corrected spelling.

Jshearer: Added information regarding out package repository.

2014-07-30T14:03:39Z

Added information regarding out package repository.

New page

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 interacting 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 <code><nowiki>http://nuget.evisionservices.com/nuget/Ensemble</nowiki></code>. The repository is also accessible via the web, at http://nuget.evisionservices.com/feeds/Ensemble

← Older revision		Revision as of 19:07, 1 August 2016
Line 18:		Line 18:
	* http://docs.nuget.org/docs/start-here/installing-nuget		* http://docs.nuget.org/docs/start-here/installing-nuget
	* http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog		* http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog
		+
		+
		+	Back to [[Developer Page]]

@@ Line 12: / Line 12: @@
 # Open Visual Studio and navigate to <code>Tools</code> &gt; <code>Options</code> &gt; <code>NuGet Package Manager</code> &gt; <code>Package Sources</code>.
 # Add a new package source by clicking the plus (<code>+</code>) button.
-# Enter a name for the package source.  For the location, enter <code><nowiki>http://nuget.evisionservices.com/nuget/Ensemble</nowiki></code>
+# Enter a name for the package source.  For the location, enter <code><nowiki>http://nuget.evisionservices.com/nuget</nowiki></code>
 # Click <code>OK</code> to save the changes.
 == Related Information ==
 * http://docs.nuget.org/docs/start-here/installing-nuget
 * http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog

← Older revision		Revision as of 18:59, 29 September 2014
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 ~~interacting~~ with the various systems that store and process their data.	+	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.

@@ 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 interact with the various systems that store and process their data.
+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 ==
+== Prerequisites ==
-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:
+== Adding the eVision NuGet Server ==
 * http://docs.nuget.org/docs/start-here/installing-nuget
 * http://docs.nuget.org/docs/start-here/managing-nuget-packages-using-the-dialog