Table of Contents |
---|
Adding the custom package source
Note |
---|
Starting |
...
with Catel v5, the alpha prereleases are only available on the MyGet feed for Catel. Therefore you must first add the custom url to the NuGet Package Manager. The easiest way to do this is via Visual Studio. |
- Go to Tools => NuGet Package Manager => Package Manager Settings
- Select Package Sources
- Click the + button at the right top and use the following values at the bottom:
Name: MyGet - Catel
Source: https://www.myget.org/F/catel/api/v3/index.json
Installing via package manager
Note |
---|
This section must be written with screenshots |
Please make sure to select the same settings as in the screenshow below:
Installing via package manager console
...
Code Block |
---|
Install-Package Catel.Extensions.Controls –IncludePrerelease -version 24.40.11122110410-betaunstable0532 |
Updating to the latest beta
...
Code Block |
---|
Update-Package Catel.Extensions.Controls –IncludePrerelease -version 24.40.11122110410-betaunstable0532 |
Updating to the latest stable version
Code Block |
---|
Update-Package Catel.Extensions.Controls |
Strange versioning
The versioning of the beta versions is a bit strange. This is due to a bug in NuGet which does not support the full SemVer standard to include build numbers. Therefore, the beta versions are always 1 less than the next official version.
For example, say that version 2.4 is currently the official version, and the team is working towards version 2.5. Then all beta versions for 2.5 will have this version number:
2.4.[yyMMddHHmm]-beta (thus on December 21st 2011, 10:41, the version would be 2.4.1112211041-beta).
Note |
---|
First idea was to include the full year, but then the number became too large. Therefore, 20 of 2011 is stripped (we will think of a solution for this in the year 2099) |