This website requires JavaScript.
Explore
Help
Sign In
mirrors
/
dotnet-installer
Watch
2
Star
0
Fork
You've already forked dotnet-installer
0
Code
Issues
Pull requests
Projects
Releases
Packages
Wiki
Activity
Actions
a616c04a38
dotnet-installer
/
TestAssets
History
Livar Cunha
10e743e8e5
Switched to using a FallbackPackagePathResolver to find the tool dll, because now with Fallback folders, we can have the tool dll in the fallback folder but its assets file in the user nuget cache. This happens because Nuget never writes to the fallback folder, including the tool's assets file that it generates during restore.
2017-03-24 12:17:27 -07:00
..
DesktopTestProjects
Disabling intermittent test and fixing assets for windows only tests.
2017-03-17 20:32:52 -07:00
LockFiles
/ExportFiles
Fix package code for new NuGet.
2016-07-26 20:53:20 -05:00
NonRestoredTestProjects
Updated tests to the new appropriate TFM 1.1, since we need a shared runtime besides 2.0 in the new distros. Once we have vstest for 2.0 then we won't need it anymore.
2017-03-17 20:32:51 -07:00
TestPackages
Switched to using a FallbackPackagePathResolver to find the tool dll, because now with Fallback folders, we can have the tool dll in the fallback folder but its assets file in the user nuget cache. This happens because Nuget never writes to the fallback folder, including the tool's assets file that it generates during restore.
2017-03-24 12:17:27 -07:00
TestProjects
Switched to using a FallbackPackagePathResolver to find the tool dll, because now with Fallback folders, we can have the tool dll in the fallback folder but its assets file in the user nuget cache. This happens because Nuget never writes to the fallback folder, including the tool's assets file that it generates during restore.
2017-03-24 12:17:27 -07:00