169 packages tagged with “foundation”
Integrate with Azure DevOps Server 2022 and Azure DevOps Services from desktop-based, ASP.NET, and other Windows applications. Provides access to shared platform services such as account, profile, identity, security, and more via public REST APIs.
Integrate with Azure DevOps Server 2022 and Azure DevOps Services from desktop-based, ASP.NET, and other Windows applications. Provides the models used to access the Distributed Task Service via public REST APIs.
Integrate with Azure DevOps Server and Azure DevOps Services from desktop-based, ASP.NET, and other Windows applications. Provides access to version control, work item tracking, build, and more via public REST APIs.
This package provides an assembly containing classes which extend the .NET Framework 4.5 with the necessary logic that extends token validation to check that the signer of a token and the issuer of the token are a valid pair. This capability can be applied both within the Windows Identity Foundation token processing pipeline and standalone, without any dependency on WIF’s configuration.
Simple, flexible, interactive and powerful data visualization for Wpf
Integrate with Azure DevOps Server 2022 and Azure DevOps Services from desktop-based Windows applications. Work with and manage version control, work items, and build, and other resources from your client application.
Stimulsoft Reports.WPF is a reporting tool that is developed for WPF (Windows Presentation Foundation). Rich capabilities of rendering, viewing, printing and exporting reports – it's all about Stimulsoft Reports.WPF. The product uses the reports engine for creating reports which is based on the many years experience of developing and using reporting tools. Great many components, properties and parameters, thought over the structure of reports.
ThinkGeo.UI.Wpf targets .NET Framework 4.6.2+ and .NET 8 for Windows. This package allows you to add maps and perform GIS spatial operations within your WPF/WinForms application. It provides classes to work with most GIS data formats, display popups, allow spatial drawing, manage projections, perform spatial operation and much more. Supported Platforms: Windows This is a commercial product with a free 30-day evaluation. Start your evaluation by signing up at https://helpdesk.thinkgeo.com/register and downloading the ProductCenter application. Docs and Product Guides: https://docs.thinkgeo.com/ API Documentation: https://docs.thinkgeo.com/products/desktop-maps/ThinkGeo.UI.WinForms%26Wpf/ThinkGeo.UI.Wpf.AdornmentOverlay/ Other ThinkGeo Products based on .NET: ThinkGeo.UI.Maui ThinkGeo.UI.Android ThinkGeo.UI.iOS ThinkGeo.UI.Blazor ThinkGeo.UI.WinForms ThinkGeo.GisServer
Requires Sitecore 10.3 Requires .NET 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Foundation.ModelMapping library is inspired by AutoMapper and is designed to provide a quick, non-ORM method of mapping Sitecore Items to ViewModels. String properties on your ViewModel will be mapped to FieldRendered values from fields with the same names. Integer and DateTime property types can also be handled automatically, although you will not get page editor support for these types. There are a number of Attributes that you can assign to your ViewModel's properties to change the behavior of the Mapper. Usage: var modelMapper = (IModelMapper)ServiceLocator.ServiceProvider.GetService(typeof(IModelMapper)); // Dependency Injection of an IModelMapper is supported TModel viewModel = modelMapper.MapItemToNew<TModel>(sourceItem); Or: TModel viewmodel = item.MapToNew<TModel>(); Or: modelMapper.MapTo(item, model); When using Item or ItemList extensions for mapping, the context IModelMapper is requested from the ServiceLocator, so any moc objects you use for testing are supported with these extension methods. Constraints: - Your ViewModel must have a public, parameterless constructor. - Only Writable, Public Instance properties will be mapped. - Within Sitecore, your field names can be human-legible. ModelMapper will attempt to convert the field name to a valid Property name. Simpler names work best. You can use the Field's Display Name for better human legibility and keep the Field's actual name closer to a legit C# entity name. - ViewModel properties can be: - - Strings - - HtmlStrings (recommended for RichText and FieldRenderer) - - Integers - - Decimals - - DateTimes - - Other ViewModels (recommended for DropLink, DropTree) - - ICollection Generics of other ViewModels (recommended for Multilist, Treelist) - - ModelMapping.Model.ImageModel (for Image Fields, gives access to all field properties and permits generating different kinds of image URLs on the View.) - - ModelMapping.Model.GeneralLinkModel (for General Link fields, gives access to all field properties through a single object.) - - Random Plain Old Classes as long as they are Where T: class, new() The following Model properties are mapped to Item properties rather than Item fields: - ID - Maps to the Item.ID - Make sure you use Sitecore.Data.ID as the property type. - Name - Maps to the Item.Name - DisplayName - Maps to Item.DisplayName - Url - Should be a string, not a Uri. Causes the current context LinkManager to generate a Url for the Item. - Parent - Maps to the ViewModel you provide based on the Item.Parent. Support for XML Field Attributes - ImageField.Alt - use Model.FieldNameAlt - ImageField.Height - use Model.FieldNameHeight - GeneralLink.Target - use Model.FieldNameTarget - etc. Support for LinkField.TargetItem - use Model.FieldNameTargetItem and supply a class with public properties and a parameterless constructor. Support for MultilistField.GetItems - use Model.FieldName and supply a generic ICollection<T> where "T" is new() and has properties you can map. Extensible! See the Constellation.Foundation.ModelMapping.config file to change the way Fields are processed.
Requires Sitecore 10.3 Requires .NET 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Foundation.Data namespace contains an Item extension class that allows the developer to: - Get an Item's ancestor based on Template - Test an Item's Template inheritance - Retrieve an Item's children based on a specific Template - Retrieve the URL for the Item using the currently active LinkManager configuration. - Determine if the Item is in the Context Site. - Find or create an Item's child given a name and a Template ID.
Integrate with Azure DevOps Server 2022 and Azure DevOps Services from desktop-based, ASP.NET, and other Windows applications. Provides access to the Release Service via public REST APIs.
Integrate with Azure DevOps Server 2022 and Azure DevOps Services from desktop-based, ASP.NET, and other Windows applications. Provides access to the Distributed Task Service via public REST APIs.
Core CSS and JavaScript files for Foundation framework. For the complete package install Foundation5.MVC
Requires Sitecore 10.3 Requires .NET 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Foundation.PackageVerification library can be used to create NuGet packages that "self install" Items in Sitecore during the Sitecore initialization process. This can be very handy if your library requires a few "traffic control" Items or some Core/Sheer/SPEAK Items in order to run. It can also be used to prevent users from breaking your install. To use, install this NuGet package and review the provided example configuration file. for each Package you want to "verify," supply the name of the package (must be in the /packages folder) and the ID and database of Items you can use to determine if the package was previously installed. If these Items are not located, the package provided will be installed. Results are logged. It is possible to create your own package processor if your verification needs are more substantial. See the provided configuration example for where to override package processing on a package-by-package basis.
Integrate with Integrate with Azure DevOps Server 2022 and Azure DevOps Services from desktop-based, ASP.NET, and other Windows applications. Provides access to the Service Endpoints via public REST APIs.
Integrate with Azure DevOps Server 2022 and Azure DevOps Services from desktop-based, ASP.NET, and other Windows applications. Provides access to the Gallery Service via public REST APIs.
Core SCSS (Sass) and JavaScript files for Foundation for Sites. For the complete package install Foundation5.MVC.Sass
Integrate with Azure DevOps Server 2022 and Azure DevOps Services from desktop-based, ASP.NET, and other Windows applications. Provides access to the Service Hooks Service via public REST APIs.
Requires Sitecore 10.3 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Foundation.SitemapXml namespace contains Http Handlers which intercept the request before it hits Sitecore. Robots.TXT Handler: Returns a basic document that automatically applies to all search engine agents. The stock configuration has disallows for /sitecore urls to prevent the login page from being indexed. Additional default or site specific rules can be added through the supplied configuration file. See instructions within the config file. Assuming a given Site's robots.txt does not deny the root of a site, the robots.txt file will include a link to the site's sitemap.xml file. Sitemap.XML Handler: Returns an on-the-fly document (there are cache options available) for each configured Site in your installation. The document is created by having one or more "crawlers" inspect the Content Tree generating the necessary Item facts and URLs required to produce the Sitemap. You can specify a set of default crawlers for your installation, as well as override the crawler list on a site-by-site basis. There are also provisions for excluding sites from returning a sitemap.xml document if it is not appropriate. Default Functionality: The system will function on a basic level "out of the box". There is a default Content Tree crawler that will start at the root of the current Site and include Items that have presentation details. The crawlers operate in the extranet\anonymous role and thus security can be used to "hide" Items or branches from the crawler. Crawler output has extensive support for "validating" whether an Item should be included in the sitemap or not. Facts available through the API include: - Does the Item have presentation? - Does the Item have explicit rules to prevent Search Indexing? - Does the Item represent a "Page"? It is up to the developer to supply meaningful decisions behind these facts, but answering "no" to any of them will result in the Item not being included. This library outputs substantial amounts of troubleshooting warnings to the Sitecore log file. If you're having trouble, search for Constellation.Foundation.SitemapXml in your log file. Multi-Language Support: For every "site" definition element in your Sitecore configs, add a "supportedLanguages" attribute that is a comma-delimited list of all languages available on your site (example: supportedLanguages="en-US,fr-FR,pt-PT") Doing this will force the sitemap.xml file to include "alternate" links for each language the site supports. Installation Warning: Your web.config must have a system.webServer/handlers section, and that section must have at least one handler in it (an "add" element) in order to install this package successfully. If you're using the default Sitecore web.config this won't be an issue. The handlers provided in this package must be inserted at the top of the stack of handlers.
VERSION 10.3 is compiled for Sitecore 10.2 use and will not work on earlier versions. Requires Sitecore 10.3 Requires .NET 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Foundation.Caching namespace contains a Cache facade class that allows a developer to cache an object to either the Sitecore Cache or the System Web Cache. In addition to providing quick access to these APIs, the facade also provides support for scoping cached objects at the following levels: * Global * Site * Database Request an ICacheManager from your service locator to use in your Controllers. Portions based on work by Christopher Giddings: https://cjgiddings.wordpress.com/2012/02/03/sitecore-caching-utility/ updated heavily for modularity and to support Sitecore 9.x
naked Agility Visual Studio Team Services Sync & Migration Engine allows you to bulk edit data in Microsoft Team Foundation Server (TFS) and Visual Studio Team Services (VSTS). You can migrate work items, area & iterations, & test data from one Team Project to another. You can builk update work items and apply processing rules against your server or account. While the code is managed on Visual Studio Team Services all commits and releases are synched to https://github.com/nkdAgility/vsts-data-bulk-editor/
VERSION 10.3 is compiled for Sitecore 10.2 use and will not work on earlier versions. Requires Sitecore 10.3 Requires .NET 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Foundation.Context namespace contains a contract for context-sensitive objects along with a context evaluator that compares the sensitive instances' runtime settings against their configured scope. The purpose of this library is to provide scoped pipeline handlers and rules to Sitecore to prevent developers from unintentionally executing their customizations outside the scope of their current tenant|site|request.
Requires Sitecore 10.3 Requires .NET 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Foundation.Mvc assembly contains enhancements to Sitecore's MVC Rendering system: GenerateRenderingSpecificCacheKey Mvc.RenderRendering pipeline processor: Replaces the default GenerateCacheKey processor. Includes the ID of the Rendering in the cache key, this allows for multiple renderings with different presentation to use the same Datasource and be cached by Datasource without issues. MinifyAndAddRecordedHtmlToCache Mvc.RenderRendering pipeline processor: Replaces the default AddRecordedHtmlToCache processor. Uses the WebMarkupMin library to process the output HTML, Javascript, and CSS and minify it to improve page delivery time through file size reduction. The default settings are "safe" but effective, however WebMarkupMin offers far more aggressive minification settings for the bold. GetControllerRenderer Mvc.GetRenderer pipeline processor: Replaces the default GetControllerRenderer. Allows the developer to rely on the name of the Rendering to locate the appropriate controller to execute (convention over configuration). Very handy for Renderings that have a dedicated controller with one action that always produces the same output. ConventionController: Provides a good base-class controller for Sitecore implementations: * Forces the use of the Index() controller action (overrides possible) * Provides the programmer with immediate access to the Rendering's DataSource and ContextItem (PageContext) * Requires the programmer to assemble the model from the above Items. * Automatically finds the View based upon the Rendering's XPath location in Sitecore EditorCompatibleView: Replaces the stock MVC View, and provides methods for determining if the Page Mode "IsExperienceEditor" and "IsExperienceEditorEditing" which are of particular use if the View needs to change behavior to support editors. ViewPathResolver: Independent engine for locating a View based on the Rendering Item's path in Sitecore. It has configuration settings that allow the programmer to specify the location of Renderings in Sitecore and how they map to the location of the Views on disk. See the provided config file for details.
Simple, flexible, interactive and powerful data visualization for Wpf (forked from master branch to add Support to netcoreapp3.1)
Package Description
Integrate with Azure DevOps Server 2022 and Azure DevOps Services from desktop-based, ASP.NET, and other Windows applications. Provides access to the Search Service via public REST APIs.
Provides a default starting point for setting up a new WebApi service which includes Its.Configuration and Its.Log with a set of classes that preconfigure numerous defaults.
Integrate with Azure DevOps Server 2022 and Azure DevOps Services from desktop-based, ASP.NET, and other Windows applications. Provides access to the Extension Management Service via public REST APIs.
This is the elision foundation package to reference if you are building a module or other code that just needs to reference the elision foundation. If you need to install Elision's foundation layer, use the Elision.Foundation package instead.
Foundation is the most advanced responsive front-end framework in the world. With Foundation you can quickly prototype and build sites or apps that work on any kind of device, with tons of included layout constructs (like a full responsive grid), elements and best practices. Homepage: http://foundation.zurb.com Documentation: http://foundation.zurb.com/docs Download: http://foundation.zurb.com/download.php Foundation is MIT-licensed and absolutely free to use. Foundation wouldn't be possible without the support of the entire ZURB team, our friends and colleagues who gave feedback, and some luminaries who did some heavy lifting that we took advantage of (thanks guys).