Change NuGet package to a tools package about il-repack

[gluck]

I changed it "on purpose", as ILRepack.exe can be used as a library for some projects (like ILMerge does), not only as a standalone tool.
I wasn't sure whether the 'tool' deployment of nuget was really used (and how), and also thought most of the uses of the nuget package would be as a library dependency.

You're definitely proving me wrong on this, now I wonder if I should make two packages on nuget (library+tool)...

Any thoughts on this ?

[adamralph]

I wasn't aware that people were using ILRepack as a project reference. Out of interest, what is an example use case for that?

In any case, if that is a common requirement then I think your idea of two packages is the best solution. The name of the new package should indicate that it is a tools package and I guess it probably makes sense to put something into the descriptions of each package explaining what they can each be used for so that a user performing a NuGet search can easily tell which one they need.

[adamralph]

Thanks very much!