Free downloads for building and running.NET apps on Linux, macOS, and Windows. Runtimes, SDKs, and developer packs for.NET Framework,.NET Core, and ASP.NET. What to try if you can't install or activate Office for Mac. Restart your Mac and open any Microsoft Office app to reactivate. Can't download the Office for Mac installer. Check to make sure your internet is working on the Mac you're trying to install on. Pause any other downloads you may have active. Follow these steps to install the UI flows app: Download the UI flows installer. Open the Setup.Microsoft.PowerAutomate.UIflow.exe file. This file is likely in your Downloads folder after you downloaded it in the previous step. The runtime includes everything you need to run existing apps/programs built with.NET Framework. Download.NET Framework 4.7.2 Runtime. Developer Pack. The developer pack is used by software developers to create applications that run on.NET Framework, typically using Visual Studio. Download.NET Framework 4.7.2 Developer Pack.
-->
You can use Visual Studio or your own custom development environment to build SharePoint Framework solutions. You can use a Mac, PC, or Linux.
Note
Before following the steps in this article, be sure to Set up your Office 365 tenant.
You can also follow these steps by watching this video on the SharePoint PnP YouTube Channel:
Install developer tools
Install NodeJS
Install NodeJS LTS version 10.
- If you are in Windows, you can use the msi installers (x86 or x64) in this link for the easiest way to set up NodeJS (notice that these direct links evolve over time, so check the latest v10 from the above directory).
- If you have NodeJS already installed, check that you have the correct version by using
node -v
. It should return version 10.19.0.
Important
The current supported LTS version of NodeJS for the SharePoint Framework is Node.js v8.x and Node.js v10.x. Notice that 9.x, 11.x or 12.x versions are currently not supported with SharePoint Framework development.
Note
If you are building SharePoint Framework components for SharePoint Server 2016, refer to additional details in the SPFx & SharePoint Server 2016 section for additional details on which version of NodeJS you should install.
Install a code editor
You can use any code editor or IDE that supports client-side development to build your web part, such as:
The steps and examples in this documentation use Visual Studio Code, but you can use any editor of your choice.
Install Yeoman and gulp
Yeoman helps you kick-start new projects, and prescribes best practices and tools to help you stay productive. SharePoint client-side development tools include a Yeoman generator for creating new web parts. The generator provides common build tools, common boilerplate code, and a common playground website to host web parts for testing.
Enter the following command to install Yeoman and gulp:
Install Yeoman SharePoint generator
The Yeoman SharePoint web part generator helps you quickly create a SharePoint client-side solution project with the right toolchain and project structure. Microsoft net framework 4.8 sdk mac.
To install the SharePoint Framework Yeoman generator globally, enter the following command:
For more information about the Yeoman SharePoint generator, see Scaffold projects by using Yeoman SharePoint generator. https://latinever334.weebly.com/microsoft-excel-data-entry-apple-mac-ver-16.html.
Install a modern web browser
You should be using a modern web browser like Edge, Chrome or Firefox as the development browser. Local workbench does not support usage of Internet Explorer 11.
Trusting the self-signed developer certificate
The SharePoint Framework's local webserver, used when testing your custom solutions from your development environment, uses HTTPS by default. This is implemented using a development self-signed SSL certificate. Self-signed SSL certificates are not trusted by your developer environment. You must first configure your development environment to trust the certificate.
A utility task is included in every SharePoint Framework project in the form of a gulp task. You can elect to do this now, or wait until you create your first project as covered in the Build your first SharePoint client-side web part (Hello World part 1): Preview the web part tutorial.
Once a project has been created with the Yeoman generator for the SharePoint Framework, execute the following command from within the root folder of the project.
Note
This assumes you have installed all dependencies with
npm install
after creating the project. This step will install all gulp tasks as part of a project.
Optional tools
Following are some tools that might come in handy as well:
SPFx & SharePoint Server 2016
SharePoint Server 2016 uses the SharePoint Framework (SPFx) v1.1. Around this the time of the v1.1 release, NodeJS was transitioning from NodeJS v6.x to v8.x. In this update, NodeJS introduced a change where the default HTTP protocol switched from HTTP1 to HTTP2. SPFx v1.1 was written for HTTP1, not HTTP2, so this change impacted the local web server for SPFx v1.1 projects.
In NodeJS v8.x, you can force HTTP1 by setting the following environment variable to instruct NodeJS to use HTTP1 instead of the default HTTP2:
NODE_NO_HTTP2=1
. This environment variable only exists in NodeJS v8.x. Therefore, if you are building SPFx solutions for SharePoint Server 2016, you should use NodeJS v8.x.
This issue does not impact later versions of SPFx because they have been updated to support HTTPs.
For more information, refer to issue #1002.
Next steps
You are now ready to build your first client-side web part!
Troubleshooting
Unable to Trust the Self-signed Development Certificate
If you are working with SharePoint Server 2016 / SPFx v1.1, first check the SPFx & SharePoint Server 2016 section above to ensure you are running a supported version of NodeJS.
In some cases, executing the command
gulp trust-dev-cert
, does not have the desired effect of trusting the self-signed development certificate on your machine. In rare cases such as these, you may need to delete a hidden folder that's generated in your profile folder. Locate & delete the folder <homedir>/.gcb-serve-data
and then try to trust the self-signed development certificate again.
Unable to Install Packages with NPM - Corporate Proxies
If your development environment is behind a corporate proxy, you need to configure NPM to use that proxy. Refer to the npm-config documents on how to configure your development environment behind a corporate proxy.. specifically the proxy & http-proxy settings. More information: How to setup Node.js and Npm behind a corporate web proxy
Note
If you find an issue in the documentation or in the SharePoint Framework, report that to SharePoint engineering by using the issue list at sp-dev-docs repository. Thanks for your input in advance.
-->
Looking to install a package? See Ways to install NuGet packages.
To work with NuGet, as a package consumer or creator, you can use command-line interface (CLI) tools as well as NuGet features in Visual Studio. This article briefly outlines the capabilities of the different tools, how to install them, and their comparative feature availability. To get started using NuGet to consume packages, see Install and use a package (dotnet CLI) and Install and use a package (Visual Studio). To get started creating NuGet packages, see Create and publish a NET Standard package (dotnet CLI) and Create and publish a NET Standard package (Visual Studio).
Tool | Description | Download |
---|---|---|
dotnet.exe | CLI tool for .NET Core and .NET Standard libraries, and for any SDK-style project such as one that targets .NET Framework. Included with the .NET Core SDK and provides core NuGet features on all platforms. (Starting in Visual Studio 2017, the dotnet CLI is automatically installed with any .NET Core related workloads.) | .NET Core SDK |
nuget.exe | CLI tool for .NET Framework libraries and for any non-SDK-style project such as one that targets .NET Standard libraries. Provides all NuGet capabilities on Windows, provides most features on Mac and Linux when running under Mono. | nuget.exe |
Visual Studio | On Windows, the NuGet Package Manager is included with Visual Studio 2012 and later. Visual Studio provides the Package Manager UI and the Package Manager Console, through which you can run most NuGet operations. | Visual Studio |
Visual Studio for Mac | On Mac, certain NuGet capabilities are built-in directly. Package Manager Console is not presently available. For other capabilities, use the dotnet.exe or nuget.exe CLI tools. |
Visual Studio for Mac |
Visual Studio Code | On Windows, Mac, or Linux, NuGet capabilities are available through marketplace extensions, or use the dotnet.exe or nuget.exe CLI tools. |
Visual Studio Code |
The MSBuild CLI also provides the ability to restore and create packages, which is primarily useful on build servers. MSBuild is not a general-purpose tool for working with NuGet.
Package Manager Console commands work only within Visual Studio on Windows and do not work within other PowerShell environments.
Visual Studio
Install on Visual Studio 2017 and newer
Starting in Visual Studio 2017, the installer includes the NuGet Package Manager with any workload that employs .NET. To install separately, or to verify that the Package Manager is installed, run the Visual Studio installer and check the option under Individual Components > Code tools > NuGet package manager.
Install on Visual Studio 2015 and older
NuGet Extensions for Visual Studio 2013 and 2015 can be downloaded from https://dist.nuget.org/index.html.
For Visual Studio 2010 and earlier, install the 'NuGet Package Manager for Visual Studio' extension. Note, if you can't see the extension in the first page of search results, try changing the Sort By dropdown to 'Most Downloads', or an alphabetical sort.
CLI tools
You can use either the
dotnet
CLI or the nuget.exe
CLI to support NuGet features in the IDE. The dotnet
CLI is installed with some Visual Studio workloads, such as .NET Core. The nuget.exe
CLI must be installed separately as described earlier.
The two NuGet CLI tools are
dotnet.exe
and nuget.exe
. See feature availability for a comparison.
- To target .NET Core or .NET Standard, use the dotnet CLI. The
dotnet
CLI is required for the SDK-style project format, which uses the SDK attribute. - To target .NET Framework (non-SDK-style project only), use the
nuget.exe
CLI. If the project is migrated frompackages.config
to PackageReference, use the dotnet CLI.
dotnet.exe CLI
The .NET Core 2.0 CLI,
dotnet.exe
, works on all platforms (Windows, Mac, and Linux) and provides core NuGet features such as installing, restoring, and publishing packages. dotnet
provides direct integration with .NET Core project files (such as .csproj
), which is helpful in most scenarios. dotnet
is also built directly for each platform and does not require you to install Mono.
Installation:
- On developer computers, install the .NET Core SDK. Starting in Visual Studio 2017, the dotnet CLI is automatically installed with any .NET Core related workloads.
- For build servers, follow the instructions on Using .NET Core SDK and tools in Continuous Integration.
To learn how to use basic commands with the dotnet CLI, see Install and use packages using the dotnet CLI. Microsoft home and office student 2016 for mac.
nuget.exe CLI
The
nuget.exe
CLI, nuget.exe
, is the command-line utility for Windows that provides all NuGet capabilities; it can also be run on Mac OSX and Linux using Mono with some limitations.
To learn how to use basic commands with the
nuget.exe
CLI, see Install and use packages using the nuget.exe CLI.
Microsoft Setup Ui Framework Mac Download Mac
Installation:
Windows
Note
NuGet.exe 5.0 and later require .NET Framework 4.7.2 or later to execute.
- Visit nuget.org/downloads and select NuGet 3.3 or higher (2.8.6 is not compatible with Mono). The latest version is always recommended, and 4.1.0+ is required to publish packages to nuget.org.
- Each download is the
nuget.exe
file directly. Instruct your browser to save the file to a folder of your choice. The file is not an installer; you won't see anything if you run it directly from the browser. - Add the folder where you placed
nuget.exe
to your PATH environment variable to use the CLI tool from anywhere.
macOS/Linux
Behaviors may vary slightly by OS distribution.
-
Install Mono 4.4.2 or later.
-
Mac microsoft header cant click on the body. Execute the following command at a shell prompt:
-
Create an alias by adding the following script to the appropriate file for your OS (typically
~/.bash_aliases
or~/.bash_profile
): -
Reload the shell. Test the installation by entering
nuget
with no parameters. NuGet CLI help should display.
Tip
Use
nuget update -self
on Windows to update an existing nuget.exe to the latest version.
Note
The latest recommended NuGet CLI is always available at
https://dist.nuget.org/win-x86-commandline/latest/nuget.exe
. For compatibility purposes with older continuous integration systems, a previous URL, https://nuget.org/nuget.exe
currently provides the deprecated 2.8.6 CLI tool.
Feature availability
Feature | dotnet CLI | nuget CLI (Windows) | nuget CLI (Mono) | Visual Studio (Windows) | Visual Studio for Mac |
---|---|---|---|---|---|
Search packages | ✔ | ✔ | ✔ | ✔ | |
Install/uninstall packages | ✔ | ✔(1) | ✔ | ✔ | ✔ |
Update packages | ✔ | ✔ | ✔ | ✔ | |
Restore packages | ✔ | ✔ | ✔(2) | ✔ | ✔ |
Manage package feeds (sources) | ✔ | ✔ | ✔ | ✔ | |
Manage packages on a feed | ✔ | ✔ | ✔ | ||
Set API keys for feeds | ✔ | ✔ | |||
Create packages(3) | ✔ | ✔ | ✔(4) | ✔ | |
Publish packages | ✔ | ✔ | ✔ | ✔ | |
Replicate packages | ✔ | ✔ | |||
Manage global-package and cache folders | ✔ | ✔ | ✔ | ||
Manage NuGet configuration | ✔ | ✔ |
(1) Does not affect project files; use
dotnet.exe
instead.
(2) Works only with
packages.config
file and not with solution (.sln
) files.
(3) Various advanced package features are available through the CLI only as they aren't represented in the Visual Studio UI tools.
(4) Works with
.nuspec
files but not with project files.
Upcoming Features
If you'd like to preview upcoming NuGet features, install a Visual Studio Preview, which works side-by-side with stable releases of Visual Studio. To report problems or share ideas for previews, open an issue on the NuGet GitHub repository.
Related topics
Best Web Ui Framework
Developers working on Windows can also explore the NuGet Package Explorer, an open-source, stand-alone tool to visually explore, create, and edit NuGet packages. It's very helpful, for example, to make experimental changes to a package structure without rebuilding the package.