You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
I have a scenario in which a NuGet package contains a set of files targeting two frameworks, lib/net35 (for a Unity game project) and lib/netstandard16 (for reusing the DLLs server-side in a .NET Core REST API). No problems loading up my package on the Core side through VS2015 as normal.
The trouble is getting the net35 files into the Unity game project. Unity routinely overwrites the solution/project files so NuGet doesn't really work well with Unity projects, and DLLs should be dropped somewhere under an "Assets" folder in a Unity project folder.
I tried to create a simple batch file in the folder where I store my packages with a command like this:
However, that dumps both framework libs into the folder, which is a problem. Would it be a big deal to add a switch along the lines of "-Framework net35" to the install command for times when a VS project file isn't around to consult?
The text was updated successfully, but these errors were encountered:
NuGet install was not designed to work with multiple TFMs. In the short term, we won't be able to address this feature request. Putting into future.
rrelyea
changed the title
Command-line switch to choose framework target to install?
New commandline switch? -- NuGet Install -tfm netfx35
Jul 19, 2016
We haven’t been able to fully investigate your problem as our focus has been on other problem reports. If there are more community feedback on this, then we'll re-evaluate this.
I have a scenario in which a NuGet package contains a set of files targeting two frameworks, lib/net35 (for a Unity game project) and lib/netstandard16 (for reusing the DLLs server-side in a .NET Core REST API). No problems loading up my package on the Core side through VS2015 as normal.
The trouble is getting the net35 files into the Unity game project. Unity routinely overwrites the solution/project files so NuGet doesn't really work well with Unity projects, and DLLs should be dropped somewhere under an "Assets" folder in a Unity project folder.
I tried to create a simple batch file in the folder where I store my packages with a command like this:
nuget install ClientLibraries -OutputDirectory "C:\Users\Public\Documents\Unity Projects\Client\Assets\GameDLL"However, that dumps both framework libs into the folder, which is a problem. Would it be a big deal to add a switch along the lines of "-Framework net35" to the install command for times when a VS project file isn't around to consult?
The text was updated successfully, but these errors were encountered: