GcExcel .NET reference is available through NuGet, a Visual Studio extension that automatically adds libraries and references to your project.
Installing the product involves the following tasks. You can either get the GcExcel .NET NuGet package or download it locally on your machine.
If you are installing the GcExcel .NET package through NuGet, refer to the following tasks:
If you are installing the GrapeCity.Documents.Excel package manually, refer to the following tasks:
- To manually create NuGet package source
- To install the GrapeCity.Documents.Excel package using command line interface
- To add GrapeCity.Documents.Excel package reference
Setting up an application
GcExcel .NET reference is available through NuGet, a Visual Studio extension that automatically adds libraries and references to your project.
Installing the product involves the following tasks. You can either get the GcExcel .NET NuGet package or download it locally on your machine.
If you are installing the GcExcel .NET package through NuGet, refer to the following tasks:
If you are installing the GrapeCity.Documents.Excel package manually, refer to the following tasks:
- To manually create NuGet package source
- To install the GrapeCity.Documents.Excel package using command line interface
- To add GrapeCity.Documents.Excel package reference
To find and install the GrapeCity.Documents.Excel NuGet package
Complete the following steps to add GrapeCity.Documents.Excel NuGet package in your .NET Core Console Application in Visual Studio.
- In Solution Explorer, right-click either Dependencies or a project and select Manage NuGet Packages.
- In the Browse tab, select nuget.org from the Package source dropdown.
- In the Browse tab, type "grapecity.documents" or "GrapeCity.Documents" in the search text box at the top and find the package "GrapeCity.Documents.Excel" as shown in the below image.
- Click Install to install the GrapeCity.Documents.Excel package and its dependencies into the project. When the installation is complete, make sure you check the NuGet folder in your solution explorer and confirm whether or not the GrapeCity.Documents.Excel package is added to your project dependencies.
To manually create NuGet package source
In order to manually create Nuget feed source, you need to complete the following steps to add the Nuget feed URL to your Nuget settings in Visual Studio. Before you proceed with this step, make sure you first download the GcExcel .NET Nupkg file and put it in a local folder, for example - "D:\Nupkg".
- From the Tools menu, select Nuget Package Manager | Package Manager Settings. The Options dialog box appears.
- In the left pane, select Package Sources.
- Click the
button in the top right corner. A new source is added under Available Package Sources. - Set a Name for the new package source.
- To add source in the Source field, click the ellipsis button next to the Source field to browse for the Nupkg folder.
- After you select the Nupkg folder, click the Update button and finally click OK.
To install the GrapeCity.Documents.Excel package using command line interface
- Open the CommandPrompt window on your Windows system.
- Use the cd command to navigate to your project folder. For example, cd C:\Users\Admin\Documents\Visual Studio 2017\Projects\GcExcel.NetCore-ConsoleApplication.
- Install GcExcel .NET NuGet package using the following command:
dotnet add package GrapeCity.Documents.Excel
To add GrapeCity.Documents.Excel package reference
GcExcel .NET is a cross-platform spreadsheet component that can be used on multiple platforms including Windows, Linux and Mac operating system.
In case you are creating an application using the Visual Studio, user can edit the **.csproj file and a package reference as shown in the image below:
To find and install the GrapeCity.Documents.Excel NuGet package
Complete the following steps to add GrapeCity.Documents.Excel NuGet package in your Visual Studio application.
- In Solution Explorer, right-click either Dependencies or a project and select Manage NuGet Packages.
- In the Browse tab, select nuget.org from the Package source dropdown.
- In the Browse tab, type "grapecity.documents" or "GrapeCity.Documents" in the search text box at the top and find the package "GrapeCity.Documents.Excel" as shown in the below image.
- Click Install to install the GrapeCity.Documents.Excel package and its dependencies into the project. When the installation is complete, make sure you check the NuGet folder in your solution explorer and confirm whether or not the GrapeCity.Documents.Excel package is added to your project dependencies.
To manually create NuGet package source
In order to manually create Nuget feed source, you need to complete the following steps to add the Nuget feed URL to your Nuget settings in Visual Studio. Before you proceed with this step, make sure you first download the GcExcel .NET Nupkg file and put it in a local folder, for example - "D:\Nupkg".
- From the Tools menu, select Nuget Package Manager | Package Manager Settings. The Options dialog box appears.
- In the left pane, select Package Sources.
- Click the button in the top right corner. A new source is added under Available Package Sources.
- Set a Name for the new package source.
- To add source in the Source field, click the ellipsis button next to the Source field to browse for the Nupkg folder.
- After you select the Nupkg folder, click the Update button and finally click OK.
To install the GrapeCity.Documents.Excel package using command line interface
- Open the CommandPrompt window on your Windows system.
- Use the cd command to navigate to your project folder. For example, cd C:\Users\Admin\Documents\Visual Studio 2017\Projects\NETCoreMVCApplication.
- Install GcExcel .NET NuGet package using the following command:
dotnet add package GrapeCity.Documents.Excel
To add GrapeCity.Documents.Excel package reference
GcExcel .NET is a cross-platform spreadsheet component that can be used on multiple platforms including Windows, Linux and Mac operating system.
In case you are creating an application using the Visual Studio, user can edit the **.csproj file and a package reference as shown in the image below: