- As the Mac restarts, hold down the Command and R keys until the Mac OS X Utilities window appears. Select Disk Utility, and then click Continue. Select your startup disk on the left side of the screen, and then click Erase. Click the Format pop-up menu, choose Mac OS Extended, provide a name, and then click Erase.
- Sep 01, 2020 Step 2: Select Restore from Time Machine Backup on the list. Remember that if you save backups on an external drive or server, your Mac must be connected to.
Install or Reinstall Mavericks, Lion/Mountain Lion from Scratch
If you have an older Mac that chimes at boot, hold down the keys until you hear a second startup chime. Then check the Startup Disk, Display, and Date & Time panes of System Preferences to make. Aug 08, 2018 Click the Apple menu icon and then select Restart.As the Mac restarts, hold down the Command and R keys until the Mac OS X Utilities window appears.; Select Disk Utility, and then click Continue.; Select your startup disk on the left side of the screen, and then click Erase.; Click the Format pop-up menu, choose Mac OS Extended, provide a name, and then click Erase.
Sep 03, 2020 Click the Restore from Time Machine Backup option listed on the MacOS Utilities pop-up. Click Continue to enter this mode. Next is another Continue button where you’ll acknowledge the info.
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Erase the hard drive:
1. Select Disk Utility from the main menu and click on the Continue button.
2. After DU loads select your startup volume (usually Macintosh HD) from the
left side list. Click on the Erase tab in the DU main window.
3. Set the format type to Mac OS Extended (Journaled.) Optionally, click on
the Security button and set the ZeroData option to one-pass. Click on
the Erase button and wait until the process has completed.
4. Quit DU and return to the main menu.
Reinstall Lion/Mountain Lion, Mavericks: Select Reinstall Lion/Mountain Lion, Mavericks and click on the Install button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible
because it is three times faster than wireless.
-->To promote a cleaner development environment and to reduce repository size, NuGet Package Restore installs all of a project's dependencies listed in either the project file or
packages.config
. The .NET Core 2.0+ dotnet build
and dotnet run
commands do an automatic package restore. Visual Studio can restore packages automatically when it builds a project, and you can restore packages at any time through Visual Studio, nuget restore
, dotnet restore
, and xbuild on Mono.Package Restore makes sure that all a project's dependencies are available, without having to store them in source control. To configure your source control repository to exclude the package binaries, see Packages and source control.
Package Restore overview
Package Restore first installs the direct dependencies of a project as needed, then installs any dependencies of those packages throughout the entire dependency graph.
If a package isn't already installed, NuGet first attempts to retrieve it from the cache. If the package isn't in the cache, NuGet tries to download the package from all enabled sources in the list at Tools > Options > NuGet Package Manager > Package Sources in Visual Studio. During restore, NuGet ignores the order of package sources, and uses the package from whichever source is first to respond to requests. For more information about how NuGet behaves, see Common NuGet configurations.
NuGet doesn't indicate a failure to restore a package until all the sources have been checked. At that time, NuGet reports a failure for only the last source in the list. The error implies that the package wasn't present on any of the other sources, even though errors aren't shown for each of those sources individually.
Restore packages
Package Restore tries to install all package dependencies to the correct state matching the package references in your project file (.csproj) or your packages.config file. (In Visual Studio, the references appear in Solution Explorer under the Dependencies NuGet or the References node.)
- If the package references in your project file are correct, use your preferred tool to restore packages.
- Visual Studio (automatic restore or manual restore)
If the package references in your project file (.csproj) or your packages.config file are incorrect (they do not match your desired state following Package Restore), then you need to either install or update packages instead.For projects using PackageReference, after a successful restore, the package should be present in the global-packages folder and theobj/project.assets.json
file is recreated. For projects usingpackages.config
, the package should appear in the project'spackages
folder. The project should now build successfully. - After running Package Restore, if you still experience missing packages or package-related errors (such as error icons in Solution Explorer in Visual Studio), you may need to follow instructions described in Troubleshooting Package Restore errors or, alternatively, reinstall and update packages.In Visual Studio, the Package Manager Console provides several flexible options for reinstalling packages. See Using Package-Update.
Restore using Visual Studio
In Visual Studio on Windows, either:
- Restore packages automatically, or
- Restore packages manually
Restore packages automatically using Visual Studio
Package Restore happens automatically when you create a project from a template or build a project, subject to the options in Enable and disable package restore. In NuGet 4.0+, restore also happens automatically when you make changes to a SDK-style project (typically a .NET Core or .NET Standard project).
- Enable automatic package restore by choosing Tools > Options > NuGet Package Manager, and then selecting Automatically check for missing packages during build in Visual Studio under Package Restore.For non-SDK-style projects, you first need to select Allow NuGet to download missing packages to enable the automatic restore option.
- Build the project.If one or more individual packages still aren't installed properly, Solution Explorer shows an error icon. Right-click and select Manage NuGet Packages, and use Package Manager to uninstall and reinstall the affected packages. For more information, see Reinstall and update packagesIf you see the error 'This project references NuGet package(s) that are missing on this computer,' or 'One or more NuGet packages need to be restored but couldn't be because consent has not been granted,' enable automatic restore. For older projects, also see Migrate to automatic package restore. Also see Package Restore troubleshooting.
Restore packages manually using Visual Studio
- Enable package restore by choosing Tools > Options > NuGet Package Manager. Under Package Restore options, select Allow NuGet to download missing packages.
- In Solution Explorer, right click the solution and select Restore NuGet Packages.If one or more individual packages still aren't installed properly, Solution Explorer shows an error icon. Right-click and select Manage NuGet Packages, and then use Package Manager to uninstall and reinstall the affected packages. For more information, see Reinstall and update packagesIf you see the error 'This project references NuGet package(s) that are missing on this computer,' or 'One or more NuGet packages need to be restored but couldn't be because consent has not been granted,' enable automatic restore. For older projects, also see Migrate to automatic package restore. Also see Package Restore troubleshooting.
Enable and disable package restore in Visual Studio
In Visual Studio, you control Package Restore primarily through Tools > Options > NuGet Package Manager:
- Allow NuGet to download missing packages controls all forms of package restore by changing the
packageRestore/enabled
setting in the packageRestore section of theNuGet.Config
file, at%AppData%NuGet
on Windows, or~/.nuget/NuGet/
on Mac/Linux. This setting also enables the Restore NuGet Packages command on the solution's context menu in Visual Studio, .NoteTo globally override thepackageRestore/enabled
setting, set the environment variable EnableNuGetPackageRestore with a value of True or False before launching Visual Studio or starting a build. - Automatically check for missing packages during build in Visual Studio controls automatic restore by changing the
packageRestore/automatic
setting in the packageRestore section of theNuGet.Config
file. When this option is set to True, running a build from Visual Studio automatically restores any missing packages. This setting doesn't affect builds run from the MSBuild command line.
To enable or disable Package Restore for all users on a computer, a developer or company can add the configuration settings to the global
nuget.config
file. The global nuget.config
is in Windows at %ProgramData%NuGetConfig
, sometimes under a specific {IDE}{Version}{SKU}
Visual Studio folder, or in Mac/Linux at ~/.local/share
. Individual users can then selectively enable restore as needed on a project level. For more details on how NuGet prioritizes multiple config files, see Common NuGet configurations.Important
If you edit the
packageRestore
settings directly in nuget.config
, restart Visual Studio, so that the Options dialog box shows the current values.Choose default package management format
NuGet has two formats in which a project may use packages:
PackageReference
and packages.config
. The default format can be selected from the drop-down under the Package Management heading. An option to be prompted when the first package is installed in a project is also available.Note
If a project does not support both package management formats, the package management format used will be the one that's compatible with the project, and therefore may not be the default set in the options. Additionally, NuGet will not prompt for selection on first package installation, even if the option is selected in the options window.
If Package Manager Console is used to install the first package in a project, NuGet will not prompt for format selection, even if the option is selected in the options window.
Restore using the dotnet CLI
Use the dotnet restore command, which restores packages listed in the project file (see PackageReference). With .NET Core 2.0 and later, restore is done automatically with
dotnet build
and dotnet run
. As of NuGet 4.0, this runs the same code as nuget restore
.As with the other
dotnet
CLI commands, first open a command line and switch to the directory that contains your project file.How To Purple Restore For Mac 2017 Free
To restore a package using
dotnet restore
:Important
![Purple Purple](https://i.ytimg.com/vi/DL-IdSL9o-8/maxresdefault.jpg)
To add a missing package reference to the project file, use dotnet add package, which also runs the
restore
command.Restore using the nuget.exe CLI
Use the restore command, which downloads and installs any packages missing from the packages folder.
For projects migrated to PackageReference, use msbuild -t:restore to restore packages instead.
restore
only adds packages to disk but does not change a project's dependencies. To restore project dependencies, modify packages.config
, then use the restore
command.As with the other
nuget.exe
CLI commands, first open a command line and switch to the directory that contains your project file.To restore a package using
restore
:Important
The
restore
command does not modify a project file or packages.config. To add a dependency, either add a package through the Package Manager UI or Console in Visual Studio, or modify packages.config and then run either install
or restore
.Restore using MSBuild
To restore packages listed in the project file with PackageReference, use the the msbuild -t:restore command. This command is available only in NuGet 4.x+ and MSBuild 15.1+, which are included with Visual Studio 2017 and higher versions. Both
nuget restore
and dotnet restore
use this command for applicable projects.- Open a Developer command prompt (In the Search box, type Developer command prompt).You typically want to start the Developer Command Prompt for Visual Studio from the Start menu, as it will be configured with all the necessary paths for MSBuild.
- Switch to the folder containing the project file and type the following command.
- Type the following command to rebuild the project.Make sure that the MSBuild output indicates that the build completed successfully.
Restore using Azure Pipelines
When you create a build definition in Azure Pipelines, include the NuGet restore or .NET Core restore task in the definition before any build tasks. Some build templates include the restore task by default.
Restore using Azure DevOps Server
Azure DevOps Server and TFS 2013 and later automatically restore packages during build, if you're using a TFS 2013 or later Team Build template. For earlier TFS versions, you can include a build step to run a command-line restore option, or optionally migrate the build template to a later version. For more information, see Set up package restore with Team Foundation Build.
Constrain package versions with restore
When NuGet restores packages through any method, it honors any constraints you specified in
packages.config
or the project file:- In
packages.config
, you can specify a version range in theallowedVersion
property of the dependency. See Constrain upgrade versions for more information. For example: - In a project file, you can use PackageReference to specify a dependency's range directly. For example:
In all cases, use the notation described in Package versioning.
Force restore from package sources
By default, NuGet restore operations use packages from the global-packages and http-cache folders, which are described in Manage the global packages and cache folders.
To avoid using the global-packages folder, do one of the following:
- Clear the folder using
nuget locals global-packages -clear
ordotnet nuget locals global-packages --clear
. - Temporarily change the location of the global-packages folder before the restore operation, using one of the following methods:
- Set the NUGET_PACKAGES environment variable to a different folder.
- Create a
NuGet.Config
file that setsglobalPackagesFolder
(if using PackageReference) orrepositoryPath
(if usingpackages.config
) to a different folder. For more information, see configuration settings. - MSBuild only: Specify a different folder with the
RestorePackagesPath
property.
To avoid using the cache for HTTP sources, do one of the following:
- Use the
-NoCache
option withnuget restore
, or the--no-cache
option withdotnet restore
. These options don't affect restore operations through the Visual Studio Package Manager or console. - Clear the cache using
nuget locals http-cache -clear
ordotnet nuget locals http-cache --clear
. - Temporarily set the NUGET_HTTP_CACHE_PATH environment variable to a different folder.
How To Purple Restore For Mac 2017 Mac
Migrate to automatic package restore (Visual Studio)
For NuGet 2.6 and earlier, an MSBuild-integrated package restore was previously supported but that is no longer true. (It was typically enabled by right-clicking a solution in Visual Studio and selecting Enable NuGet Package Restore). If your project uses the deprecated MSBuild-integrated package restore, please migrate to automatic package restore.
Projects that use MSBuild-Integrated package restore typically contain a .nuget folder with three files: NuGet.config, nuget.exe, and NuGet.targets. The presence of a NuGet.targets file determines whether NuGet will continue to use the MSBuild-untegrated approach, so this file must be removed during the migration.
To migrate to automatic package restore:
2017 Mac Computer
![Mac Mac](https://9to5mac.com/wp-content/uploads/sites/6/2017/04/how-to-restore-iphone-from-itunes-backup-lead.jpg?resize=1024,512)
- Close Visual Studio.
- Delete .nuget/nuget.exe and .nuget/NuGet.targets.
- For each project file, remove the
<RestorePackages>
element and remove any reference to NuGet.targets.
To test the automatic package restore:
2017 Mac Desktop
- Remove the packages folder from the solution.
- Open the solution in Visual Studio and start a build.Automatic package restore should download and install each dependency package, without adding them to source control.
How To Purple Restore For Mac 2017 Torrent
Troubleshooting
2017 Mac Pro
See Troubleshoot package restore.