Version and Depedency Options
We now have all the depedencies for our program. Now, we learn how to use the libraries in our code. But, now we will create another project to use it.
- Create new asp.net mvc application project
- Choose MVC template.
- It takes longer time to download all libraries needed from NuGet.
- Let's take another packages to make it easier while troubleshooting bugs.
- Install Elmah.mvc from NuGet package manager.
NuGet assumes that all packages are versioned using the Semantic Versioning scheme.
Semantic Versioning scheme refers to three numbers separated by dots, example: v1.0.1-beta (Major.Minor.Patch)1 refers to Major version when you make incompatible API changes.
0 refers to Minor version when you add functionality in a a backwards-compatible manner.
1 refers to Patch version when you make backward-compatible bug fixes.
-alpha refers to prereleases.
Tick on options menu in Elmah.MVC, pay attention to "Depedency Behaviour".
Lowest refers to the lowest version that can be used.
Highest Patch refers to the lowest minor version, but highest patch version.
Highest Minor refers to the highest minor version, of the major version (1). .
Highest refers to highest and greates patch
Check the Updates panel.
Updating a major version of the packages is risky.
The safest way is updating for the highest minor version.
Untick at newtonsoftjson and jquery.
Let's take a look at jQuery.
We need to figure out why Microsoft decided to have ASP.NET MVC use version one of the library instead of the latest and greatest.
If we take a look at jQuery 2, it doesn't support version eight or earlier of Internet Explorer.
So, its okay actually to update it.
We take a risk to update the newtonsoft too.
Updating a package with wrong version could make our project build failed.
To downgrade the installed package, we can open Tools > NuGet Package Manager > Package Manager Console.