-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect the dll versions based on the referenced .NET Framework version in a ProjectFile #19
Comments
We could use conditions like in https://github.com/fsprojects/fsharpx/blob/master/src/FSharpx.Core/FSharpx.Core.fsproj
|
Looks good. This would allow us to keep the projs untouched regardless of the developer switching the target framework version in VS. |
Yes. We just need a mapping from foldername in nuget package net40 to Condition="'$(TargetFrameworkVersion)' == 'v4.0'"> and a strategy for defaults. |
"Just" might get complicated with the |
I close this. Let's open concrete issues with bugs. |
Castle.Core misses the
Reference: https://nuget.codeplex.com/wikipage?title=Framework%20Profile%20Support |
If the project is built against the client profile we can check that with If there is only
If there is both
|
The existence of
|
Wow, it gets even more complicated. log4net 1.2.10.0 follows a different convention: it uses log4net 2.0.3 on the other hand uses |
Some bugs with specific packages I use in my sample solution:
|
The (oldish)
(This is a .NET 4.0 project.) |
|
Silverlight has |
TargetFrameworkIdentifier OMG |
could you please add the "correct" XML tags for RestSharp? |
This is nothing more than a best guess. MSBuild is broken on so many levels, who would have thought that? 👿
|
Based on
.NET Framework
Silverlight
Windows Phone
Windows Store
Portable Class Libraries
Either:
|
Looks like a good reference, even if it's not my MS: http://blog.stephencleary.com/2012/05/framework-profiles-in-net.html |
anything open? |
At the moment we install the last framework version of a package in alphabetical order.
This is of course non-sense
The text was updated successfully, but these errors were encountered: