-
Notifications
You must be signed in to change notification settings - Fork 2
installation
ESDC Developers can use the internal NuGet Source External developers can download the NuGet packages and create a NuGet Source that points to a local folder or include it in their departmental NuGet source.
For details on NuGet, the URL and User Guide for the Internal NuGet Source.
See the latest release details for WebForms (ASPX), MVC and CoreMVC.
WebForms (ASPX): GoC.WebTemplate-WebForms.1.31.2.zip
MVC: GoC.WebTemplate-MVC.1.31.2.zip
WebForms (ASPX): GoC.WebTemplate-WebForms.1.30.2.zip
MVC: GoC.WebTemplate-MVC.1.30.2.zip
Instructions on how to setup a local feed as a NuGet Source
It's always best to update to the latest version. If you want to know the specific version of CDTS or WET-BOEW that you are implementing, see the Supported Dependencies graph in the CDTS documentation.
- Open your web project in Visual Studio;
- Right click on your project;
- Select "Manage NuGet Packages...";
- In the NuGet Window:
- Select the Web Template Package Source
-
For WebForms (ASPX): Select the package named
GoC.WebTemplate-WebForms
for the template only (This will require the package namedGoC.WebTemplate-Components.Framework
andGoC.WebTemplate-Components
as well); -
For MVC: Select the package named
GoC.WebTemplate-MVC
for the template only (This will require the package namedGoC.WebTemplate-Components.Framework
andGoC.WebTemplate-Components
as well); -
For CoreMVC: Select the package named
GoC.WebTemplate-CoreMVC
for the template only (This will require the package namedGoC.WebTemplate-Components.Core
andGoC.WebTemplate-Components
as well);- Complete with some manual edits to your code, noted bellow CoreMVC Todo
- Click "Install".
- After the installation is complete, close the NuGet Window.
Sample code can be within the solution:
- Added a reference to the
GoC.WebTemplate.Components.dll
,GoC.WebTemplate.Components.Framework.dll
andGoC.WebTemplate.WebForms.dll
- Added a folder
GoC.WebTemplate
with:- 9 master pages
- A folder
StaticFallbackFiles
containing the Static backup files for the version of the template release;
- Added entries to your
web.config
.
- Added a reference to the
GoC.WebTemplate.Components.dll
,GoC.WebTemplate.Components.Framework.dll
andGoC.WebTemplate.MVC.dll
- Added a folder
Views\GoC.WebTemplate
with:- 9 layout pages
- A folder
StaticFallbackFiles
containing the Static backup files for the version of the template release;
- Added entries to your
web.config
.
- Added a reference to the
GoC.WebTemplate.Components.dll
,GoC.WebTemplate.Components.Core.dll
, andGoC.WebTemplate.CoreMvc.dll
- Added references to
Views\GoC.WebTemplate
with:- 9 layout pages
- A folder
StaticFallbackFiles
containing the Static backup files for the version of the template release
These files are visible from within Visual Studio and will be deployed (as compiled assets) with your solution but will not be added to your source.
- Edit the
Startup.cs
- Add using statements
using GoC.WebTemplate.Components.Core.Services;
- Add the following to
ConfigureServices
functionservices.AddModelAccessor(); services.ConfigureGoCTemplateRequestLocalization(); // >= v2.3.0
- Add the following to
Configure
functionapp.UseRequestLocalization(); // >= v2.3.0 app.UseRequestLocalization(CultureConfiguration.GetLocalizationOptions()); // <= v2.3.0
- Add using statements
- Add default Application Settings for the CDTS Template
- Add the following at the root level of your
appsettings.json
file
"GoCWebTemplate": { "version": "v4_0_39", //change to current CDTS version "environment": "AKAMAI" //change to the appropriate environment for your application }
- See all the available Environments
- See Configurations for all the other configurations you can add to this section.
- Add the following at the root level of your
Now that the template packages have been successfully installed, please see Implementation for the remaining implementation steps.