Giter Club home page Giter Club logo

dynamite's People

Contributors

decapent avatar denaes avatar drdeteck avatar franckyc avatar frederik-pion avatar joseph-passineau avatar luji avatar mattxtrem avatar samgrem avatar taoneill avatar yohanb avatar zargath avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

dynamite's Issues

Merge logic from VariationHelper to VariationExpert and Builder

A 2010 project introduced VariationExpert VariationBuilder logics while, in the same time, a 2013 project introduced a VariationHelper. The Helper has been moved to the Globalization.Variation namespace, but the merge of the methods must be done. The only 2 methods that seems to be used are SyncList and SyncWeb in the PowerShell dll.

Use same signing key between 2013 and 2010

The 2010 one (v0.4_SP2010 is already in prod) is under GSoft.Dynamite/Properties/GSoft.Dynamite.snk

The 2013 one (ideally, the one we get rid of) is under ~\Shared\GSoft.Dynamite.snk. This may cause problems during ugrapes in environments where Dynamite 2013 is already deployed.

Maybe both are one and the same and we screwed up while linking them to our projects somehow, we'll see...

Dependency Injection: take the new 2013-specific registrations from the defunct GResgistrationModule and put them in the Autofac and Unity registration modules in their specific projects

Deleted GRegModule:

using GSoft.Dynamite.Binding;
using GSoft.Dynamite.Caching;
using GSoft.Dynamite.Logging;
using GSoft.Dynamite.Navigation;
using GSoft.Dynamite.Repositories;
using GSoft.Dynamite.Taxonomy;
using GSoft.Dynamite.Utils;
using Microsoft.Practices.Unity;

namespace GSoft.Dynamite.Unity
{
    /// <summary>
    /// Container registrations for GSoft.G.SharePoint components
    /// </summary>
    public class GRegistrationModule : IRegistrationModule
    {
        private readonly string _logCategoryName;
        private readonly string _defaultResourceFileName;

        /// <summary>
        /// Creates a new registration module to prepare dependency injection
        /// for GSoft.G.SharePoint components
        /// </summary>
        /// <param name="logCategoryName">The ULS category in use when interacting with ILogger</param>
        /// <param name="defaultResourceFileName">The default resource file name when interacting with IResourceLocator</param>
        public GRegistrationModule(string logCategoryName, string defaultResourceFileName)
        {
            this._logCategoryName = logCategoryName;
            this._defaultResourceFileName = defaultResourceFileName;
        }

        /// <summary>
        /// Registers the modules type bindings
        /// </summary>
        /// <param name="container">The container on which to register type bindings</param>
        public void Register(IUnityContainer container)
        {
#if DEBUG
            // Logger with debug output
            var logger = new TraceLogger(this._logCategoryName, this._logCategoryName, true);
            container.RegisterInstance<ILogger>(logger);
#else
            // Logger without debug output
            var logger = new TraceLogger(this._logCategoryName, this._logCategoryName, false);
            container.RegisterInstance<ILogger>(logger);
#endif

            // Binding
            var builder = new EntitySchemaBuilder<SharePointEntitySchema>();
            var binder = new SharePointEntityBinder(new CachedSchemaBuilder(builder, logger));
            container.RegisterInstance<ISharePointEntityBinder>(binder);

            // Taxonomy
            container.RegisterType<ITaxonomyService, TaxonomyService>();
            container.RegisterType<TaxonomyService>();
            container.RegisterType<TaxonomyHelper>();

            // Navigation
            container.RegisterType<ICatalogNavigation, CatalogNavigation>();

            // Caching
            container.RegisterType<IAppCacheHelper, AppCacheHelper>();
            container.RegisterType<ISessionCacheHelper, SessionCacheHelper>();

            // Repositories
            container.RegisterType<FolderRepository>();
            container.RegisterType<ListLocator>();

            // Utilities
            container.RegisterInstance<IResourceLocator>(new ResourceLocator(this._defaultResourceFileName));

            container.RegisterType<ContentTypeHelper>();
            container.RegisterType<EventReceiverHelper>();
            container.RegisterType<FieldHelper>();
            container.RegisterType<ListHelper>();
            container.RegisterType<ListSecurityHelper>();
            container.RegisterType<MuiHelper>();
            container.RegisterType<SecurityHelper>();
            container.RegisterType<SearchHelper>();
            container.RegisterType<WebPartHelper>();
            container.RegisterType<MasterPageHelper>();
            container.RegisterType<RegionalSettingsHelper>();
            container.RegisterType<CustomActionHelper>();
            container.RegisterType<WebConfigModificationHelper>();
            container.RegisterType<VariationsHelper>();
            container.RegisterType<NavigationHelper>();
        }
    }
}

Multiple github accounts not working on SourceTree

I recently added 2 github accounts to my Windows SourceTree and cloned 2 repositories. Pushing and pulling from the first repo suddenly stopped working. The error given was:

remote: Repository not found.
fatal: repository 'https://github.com/xyz/' not found

I managed to get around the problem by uninstalling and reinstalling the credentials manager using:
$ git credential-manager uninstall
$ git credential-manager install

[EntityBinder] Supporter les DataRow qui viennent de la recherche.

Lorsqu'on utilise un KeywordQuery dans un SearchExecutor, on nous retourne des DataTable qui contiennent des DataRow dont les clés sont des ManagedProperties. On doit supporter le mapping vers des entités sachant que nous n'avons pas le SPWeb d'origine, donc pas de SPFieldCollection.

Clean up the Utils namespace in 2013 because most everything was re-distributed into other namespaces during 2010 refactor

Make sure no 2013-specifc changes get manually merge into their new-namespace'd counterparts (e.g. if anything changed in Utils/FieldHelper since October 2013, it need st obe incorporated maybe into the new Definitions/FieldHelper)

Check out the 2013 history of these in particular:


    <Compile Include="Utils\FieldHelper.cs" />
    <Compile Include="Utils\FieldInfo.cs" />
    <Compile Include="Utils\IResourceLocator.cs" />
    <Compile Include="Utils\ListHelper.cs" />
    <Compile Include="Utils\ListSecurityHelper.cs" />
    <Compile Include="Utils\MasterPageHelper.cs" />
    <Compile Include="Utils\MuiHelper.cs" />
    <Compile Include="Utils\NavigationHelper.cs" />
    <Compile Include="Utils\RegionalSettingsHelper.cs" />
    <Compile Include="Utils\ResourceLocator.cs" />
    <Compile Include="Utils\SearchHelper.cs" />
    <Compile Include="Utils\SecurityHelper.cs" />
    <Compile Include="Utils\Unsafe.cs" />
    <Compile Include="Utils\VariationsHelper.cs" />
    <Compile Include="Utils\WebConfigModificationHelper.cs" />
    <Compile Include="Utils\WebPartHelper.cs" />

Figure out a way to merge all the new 2013 stuff in the Schemas namespace with the new FieldInfos objects from the new 2010 Setup namespace

Ideally, we should enhance FieldInfos to be more complete (e.g. TaxonomyFieldInfo, etc.) and collaborate with/reuse the new Schemas utils so that we don't have to depend on any Element.xml.

Basically, we want:

  1. Create FieldInfo object that hold all field schema metadata as a static "constant" object in your Contracts project
  2. Use a FieldHelper with capabilities similar to ContentTypeHelper to EnsureField(FieldCollection, FieldInfo)

This way we can provision fields easily on a site collection or on a list. This is related to #1, where some things that @FranckyC or @yohanb added to ListHelper don't follow the "Ensure"/"Add if not exists" philosophy of ContentTypeHelper.

Installation steps problem

While installation it is not asking for steps given below:

Enter your full name and email address (your @gsoft.com email, if you work for GSoft)
Choose the option to install the self-contained Git version to be used by when prompted
Skip the Mercurial option
Choose Putty as SSH option
Enter your github.com username and password

Will this create any problem while working on it.

I am facing issue of checking resource stuck while making clone.

Please help me.

New-DSPQueryRules error: There is no web named "http://.."

Running the New-DSPQueryRules script in a new PowerShell window gives an error.

The error occured in AgroPur deployment using :

$script = './New-SPQueryRules.ps1'
Start-Process powershell.exe -ArgumentList $script -Wait

The exception is thrown in the method GSoft.Dynamite.ServiceLocator.SPWebLifetimeScopeProvider:EnsureWebScopeInternal(SPWEB web) while accessing the web.ID property.

See attachment image
image

Git step by step guide - Missing pages

Hello,

I'm not sure if this is the best place to put this but I noticed when looking through your "Git step by step" guide that steps 4 & 5 are yet to be done.

I realise this isn't likely to be high up on your list of priorities but I thought I'd point it out. Also what was meant to be in those parts? If there was an outline of what should be there someone else could write it?

How to provision taxonomy through code?

Hi, guys. I've read some topics and some classes
https://github.com/GSoft-SharePoint/Dynamite/wiki/How-to-break-up-your-solution-in-many-Visual-Studio-projects-with-their-own-responsibilities
https://github.com/GSoft-SharePoint/Dynamite#c2-initialize-your-term-store
https://github.com/GSoft-SharePoint/Dynamite/tree/91cdefb6a6434afec3130aa8acc759a81550d582/Source/GSoft.Dynamite/Taxonomy
but didn't found how to provision my taxonomy tree to my ManagedMetadata Service through code? I wonna do timer job that would be update and populate my taxonomy from SQL, but dunno how Dynamite can help with this. So, is it possible to do with dynamite?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.