VersionUtility doing way too much stuff

Topics: General
Nov 30, 2012 at 5:18 AM

I was just looking for a way to have in my msbuild targets a way to determine the output lib folder to copy assemblies to depending on the target framework version being built  and optional profile. This would be very handy when automating the multiple compilation passes on a project to build all the right assembly versions prior to nupkg packaging.

I found the place where this identifier/version/profile -> framework name -> simple string conversion is done is VersionUtility.

However, it's so huge that it's impossible to just take our of nuget and place it in an inline msbuild task for quick reuse. Looks like it's taking on quite a bit of responsibilities, way beyond just parsing and rendering the version/framework names... Maybe there's an oportunity to refactor it?

Dec 6, 2012 at 10:35 AM

Care to send a pull request?