- Using most recent Autofac for .NET 3.5 instead of old outdated one
- Our Autofac-flavor registration container now exposes its inner IContainer instance, so that we can access it if we want to
- Bumped up version to v0.5 to mark the change
Caching utilities, Variation helpers, Web Part setup-related interfaces, publishing Pages library setup helper, and more!
- CacheHelper and its related ICacheKey classes help you store your frequently-requested objects in HttpCache (warning: ClearCache will not work accross a distributed farm - it must be called from every WFE)
- VariationsDirector coordinates the creation of variation labels (with a default implementation that creates a bilingual English-French hierarchy, with en-CA as the source label's culture and fr-CA at the destination - typical for Canadian setups)
- IQueryHelper helps with creator CAML queries to filter against Taxonomy terms
- FolderMaker takes a hierarchy of IFolderInfos, IPageInfos, ITaxonomyInfos and the like as input and initializes a Pages (publishing site) library folder and pages hierarchy with folder metadata defaults pre-configured and items values assigned
- ContentTypeInfo and the like (think FieldInfo, already in Utils) help you store your content types' metadata as static "constants" objects in your app code (e.g. to avoid string-typing everywhere and copy-pasting column internal names)
Pretty brutal re-organization of namespaces to clean up the used-too-often GSoft.Dynamite.Utils namespace.
- Most definitely breaks backward compatibility with v0.4
New utils PageCreator and CollectionExtensions.
- Also re-ordered registrations in Unity and Autofac registration modules to follow the alphabetical order of the namespaces (for less confusion)
Totally explains why none of my app's modules were getting registered. Whoops! :D
Prevent NullRefs in TaxonomyMultiInfo because inner Collection wasn't always initialized (still keep it settable, though, even if it smells)
Remove smelly ScanAssembliesForInterfaceImplementationAndRegisterFirstMatch.
- Instead of this hack to register one type at a time, just put a Module in you WSP project with that project's specificy provided registrations
Merge branch 'feature/publishing-helpers' into develop
Remove now defunct ServiceLocator project
- GacAssemblyLocator is now in GSoft.Dynamite.Utils
Allow targeting of specific Assembly version when scanning the GAC.
- Also, DI.Autofac project now depends on /bin/Release/GSoft.Dynamite.DLL instead of on the other project to make sure we depend on Specific Version of Dynamite (just like the App does)
[AutofacRegistrationModuleContainer] Changed the way we load assembly. Instead of doing it manually, with the new version of autofac, you can RegisterAssemblyModules. I think this method will make sure to load all modules in the correct order.
[AutofacRegistrationModuleContainer] Reinserted the check to not load GSoft.Dynamite.DI.Autofac twice
Created new SP project, wsp that will bootstrap most projects.
-Javascript Import features with additional page head sequence id to 0
-Javascript librairies for dynamite
Renamed Dynamite SP project to GSoft.Dynamite.SP, wsp is GSoft.Dynamite.wsp and JS namespace is GSoft.Dynamite
Renamed project GSoft.Dynamite.Client to GSoft.Dynamite.SP, namespace to GSoft.Dynamite in js and res file
Added BrowserCacheSafe to all js scripts in javascript import
Fixed js script links
Merge branch 'release/v0.5_SP2010'