Activities of "bilalhaidar"

Thanks Ismail.

Im fact, I am not yet getting why the need for this function in a time canActivate is doing the job? Can you illustrate more please?

Isn't better to keep the default Angular 2 routing?

OK, I removed all reference to the Abp.Dapper nuget and then installed the correct version that works with my project. All references are okay now.

When I run the application, swagger takes over all is good.

Now, when I try to access the new application services, I get this exception in the logging file:

ERROR 2017-08-13 20:35:39,327 [35   ] Mvc.ExceptionHandling.AbpExceptionFilter - Can't create component 'Tekvention.DrcApp.Shared.CountryRegionsAppService' as it has dependencies to be satisfied.

'Tekvention.DrcApp.Shared.CountryRegionsAppService' is waiting for the following dependencies:
- Service 'Abp.Dapper.Repositories.IDapperRepository`1[[Tekvention.DrcApp.Shared.Region, Tekvention.DrcApp.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=null]]' which was not registered.

Castle.MicroKernel.Handlers.HandlerException: Can't create component 'Tekvention.DrcApp.Shared.CountryRegionsAppService' as it has dependencies to be satisfied.

'Tekvention.DrcApp.Shared.CountryRegionsAppService' is waiting for the following dependencies:
- Service 'Abp.Dapper.Repositories.IDapperRepository`1[[Tekvention.DrcApp.Shared.Region, Tekvention.DrcApp.Core, Version=4.1.0.0, Culture=neutral, PublicKeyToken=null]]' which was not registered.

   at Castle.MicroKernel.Handlers.DefaultHandler.AssertNotWaitingForDependency()
   at Castle.MicroKernel.Handlers.DefaultHandler.ResolveCore(CreationContext context, Boolean requiresDecommission, Boolean instanceRequired, Burden& burden)
   at Castle.MicroKernel.Handlers.DefaultHandler.Resolve(CreationContext context, Boolean instanceRequired)
   at Castle.MicroKernel.Handlers.AbstractHandler.Resolve(CreationContext context)
   at Castle.MicroKernel.DefaultKernel.ResolveComponent(IHandler handler, Type service, IDictionary additionalArguments, IReleasePolicy policy)
   at Castle.MicroKernel.DefaultKernel.Castle.MicroKernel.IKernelInternal.Resolve(Type service, IDictionary arguments, IReleasePolicy policy)
   at Castle.MicroKernel.DefaultKernel.Resolve(Type service, IDictionary arguments)
   at Castle.Windsor.WindsorContainer.Resolve(Type service)
   at Castle.Windsor.MsDependencyInjection.ScopedWindsorServiceProvider.ResolveInstanceOrNull(Type serviceType, Boolean isOptional)
   at Castle.Windsor.MsDependencyInjection.ScopedWindsorServiceProvider.GetServiceInternal(Type serviceType, Boolean isOptional)
   at Castle.Windsor.MsDependencyInjection.ScopedWindsorServiceProvider.GetRequiredService(Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.AspNetCore.Mvc.Controllers.ServiceBasedControllerActivator.Create(ControllerContext actionContext)
   at Microsoft.AspNetCore.Mvc.Controllers.DefaultControllerFactory.CreateController(ControllerContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextExceptionFilterAsync>d__24.MoveNext()

OK I have it now. Still facing sane issue.

My 2 cents.

I had to read about that long time ago and caused me some confusion.

First of all, you can configure the ClockProvider to be UTC (server side). This way, any date you send to the server, will be stored in the database as UTC. For me, I had to do some cleaning for the dates so that I always send the date without a time or at least (00:00:00).

On the client side, depending on the timezone the user have selected, the date will be shown accordingly.

Moment is configured by default to local date (because ClockProvider is configured so on the server). However, I prefer always to use ClockProvider.Utc to make things easy.

HTH

In that location I don't have the file horizontal-timeline.js!

Thanks. I was able to check them out.

A question to the dev team, why not implement the Date control as an angular component rather than making use of jQuery?

In fact, this might cause problems having multiple instances of the same service, in different levels of the injector (when using lazy loading).

if possible to ask someone from dev team to comment on this here.

Thanks

I already know that and that's why I am asking to gain some knowledge.

Maybe someone from the development team should answer this thread.

Thanks

I don't have this file in the angular-cli.json.

Can you guide me on how to remove this feature?

Thanks

Thanks. I believe that's only for the jQuery version. Those are not supported in Angular 2 unless we do something, which I don't know :)

Maybe someone from the core team can assist here?