search
Found 123 packages
HelixToolkit
Helix Toolkit is a collection of 3D components for .NET.
v3.1.2
↙ 2.9M / total
3D
HelixToolkit.Wpf
Helix Toolkit is a collection of 3D components for .NET. This package is based on WPF.
v3.1.2
↙ 1.9M / total
3DWPFWPF3DVisualization
HelixToolkit.Wpf.SharpDX
Helix Toolkit is a collection of 3D components for .NET. This package is based on WPF and SharpDX.
v3.1.2
↙ 889.1K / total
3DWPFWPF3DDirectXSharpDX
TwitchLib.Api.Helix
Project containing the Helix section of TwitchLib.Api
v3.10.2
↙ 692.7K / total
twitchlibrarychatc#csharp
pkg
RichardSzalay.Helix.Publishing.WebRoot
Includes dependent web projects in the ASP.NET Publishing Pipeline
v1.5.6
↙ 1.2M / total
TwitchLib.Api.Helix.Models
Project containing the Helix models used in TwitchLib.Api
v3.10.2
↙ 709.0K / total
twitchlibrarychatc#csharp
p4api.net
Perforce Helix VCS Library for .NET Core Cross Platform Library supporting Windows, Linux and OSX
v2025.2.287.2434
↙ 3.0M / total
perforcehelixvcsscmp4
p4api.net.core
Perforce Helix VCS Library for .NET Core Cross Platform Library supporting Windows, Linux and OSX
v2023.2.255.3501
↙ 1.9M / total
perforcehelixvcsscmp4
HelixToolkit.Core.Wpf
Provides custom controls and extensions for .net core WPF 3D.
v2.27.3
↙ 311.7K / total
wpfwpf3d3Dnetcore
HelixToolkit.SharpDX.Core
Provides custom 3D controls for netstandard and netcore based on SharpDX.
v2.27.3
↙ 305.3K / total
netstandardnetcoreSharpDX3DDirectX
HelixToolkit.SharpDX.Assimp
Helix Toolkit is a collection of 3D components for .NET. This package is based on SharpDX and AssimpNet. Provides Assimp Import/Export for HelixToolkit.SharpDX.
v3.1.2
↙ 150.6K / total
3DDirectXSharpDXAssimp
HelixToolkit.SharpDX.Core.Wpf
Provides custom 3D controls for netcore WPF based on SharpDX.
v2.27.3
↙ 249.2K / total
netcoreWpfSharpDX3DDirectX
Constellation.Foundation.ModelMapping
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.
Constellation.Foundation.Data
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.
v10.3.0.23123
↙ 365.0K / total
SitecoreSitecoreHelixFoundation
pkg
HedgehogDevelopment.FxCop.Helix
Adds rules to Code Analysis to verify Helix specific namespaces are being implemented correctly.
v1.0.0.7
↙ 45.9K / total
SitecoreHelix
HelixToolkit.UWP
Provides custom 3D controls for UWP and a scene graph based on SharpDX.
v2.27.3
↙ 45.8K / total
UWPSharpDX3DDirectX
Constellation.Foundation.PackageVerification
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.
v10.3.0.23221
↙ 141.1K / total
SitecoreSitecoreHelixFoundation
pkg
RichardSzalay.Helix.Publishing.Module
Includes dependent web projects in the ASP.NET Publishing Pipeline
v1.5.6
↙ 42.5K / total
Constellation.Feature.Navigation
Requires Sitecore 10.3 Requires .NET Framework 4.8 Constellation is a collection of utilities for .NET CMS implementers. The Feature.Navigation library addresses the three most common forms of Navigation on Sitecore sites: Declared (static) Navigation: (explicitly defined, may differ from the shape of the content tree) - DeclaredNavigationRepository.GetNavigation - Accepts a Navigation Menu item and assembles a full tree-like ViewModel for immediate processing in your View. If you need context highlighting in your navigation, be sure to pass in the Context Item as well. When using NavigationLink objects, there are usually several opportunities to supply the text of a given link. NavigationLink.GetBestLinkText() evaluates all of them and attempts to supply the best fit. The strategy is based on overriding the concept of "name". Here are the rules: - If Use This Display Name is checked on the NavigationLink item, it wins. - If the Link.Text is supplied by the user, it wins. - If the Link.TargetItem exists and inherits from Page Navigation Title, and the field value is not null, it wins. - If the Link.TargetItem exists its DisplayName is used. - Assuming all other things are not true, use the NavigationLink's DisplayName. Note that in this condition if you intended to point to a Sitecore Item, you have a bad link. Branch (Context) Navigation: (implicitly defined. It follows the shape of the Content Tree) - BranchNavigationRepository.GetNavigation - Accepts the request Context Item (should be a Page) and generates a tree of BranchNodes representing the nearest LandingPage, its children, as well as the descendants of any children that are Ancestors of the Context Item. (will also create Children for the Context Item node in the tree). Use this to produce the expanded navigation seen on many sites with deep content. Breadcrumbs: (implicitly defined. It walks up the Content Tree to get the path) - BreadcrumbNavigationRepository.GetNavigation - Accepts the request Context Item and Context SiteInfo. Generates an array of Breadcrumb models you can enumerate on your View. The breadcrumbs will start on your Site's StartItem and end with the supplied Context Item, which will be marked IsContextItem so you can change your rendering behavior. Uses the Item.Axes.GetAncestors() method to generate the list of breadcrumbs. The included package must be installed to use this library. This should happen automatically after you build and deploy your project.
Constellation.Foundation.Caching
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
v10.3.0.22919
↙ 92.8K / total
SitecoreSitecoreHelixFoundation
page 1next →