You don't need to do anything. NuGet already takes care of that for you. When you use nuget.exe pack command or NPE to create your package, we stamp it with the new xml schema version (in the .nuspec file), which prevents older nuget client from installing
it.

You don't need to do anything. NuGet already takes care of that for you. When you use nuget.exe pack command or NPE to create your package, we stamp it with the new xml schema version (in the .nuspec file), which prevents older nuget client from installing
it.

The nuget.exe doesn't always auto-update the schema version. It is smart enough to detect if your package makes use of the new target-framework features in 2.0 before stamping the new schema version. If your package doesn't, then it will try to
be as backwards-compatible as possible.

The nuget.exe doesn't always auto-update the schema version. It is smart enough to detect if your package makes use of the new target-framework features in 2.0 before stamping the new schema version. If your package doesn't, then it will try to be as backwards-compatible
as possible.