Updated from Catel 3.6 to 3.8 / Performance problem

Topics: Questions
Dec 10, 2013 at 12:27 PM
Hello

I have updated to catel 3.8. Now some actions needs more time than before. The only thing I changed in my code is Resolving the services.

From : ServiceLocator.ResolveType<>
To: DependencyResolver.Resolve<>

Are there some known reasons?
Coordinator
Dec 10, 2013 at 8:21 PM
The DependencyResolver is just a very light-weight wrapper around the ServiceLocator. Can you run the code with a profiler attached?
Dec 11, 2013 at 6:25 AM
I think its not the the DependencyResolver. The actions which needs a little bit more time, are all with sending end recieving messages via the message mediator.
Coordinator
Dec 11, 2013 at 7:31 AM
I can't remember changing anything. But moving from 3.6 => 3.8 is a big change, can be a lot of things.
Dec 17, 2013 at 8:32 AM
Hello

Found an other problem accroding to the upgarde from catel 3.6 to 3.8

I create a command with CommandHelper
public viewmodel()
{
   ActivateRecipeCommand = CommandHelper.CreateCommand(() => { ... }, () => PlacementErrorValidationSummary, "ActivateRecipeCommand");
}

[ValidationToViewModel(Tag = "PlacementErrorValidation", IncludeChildViewModels = true)]
public IValidationSummary PlacementErrorValidationSummary
{
      get { return GetValue<IValidationSummary>(PlacementErrorValidationSummaryProperty); }
      set { SetValue(PlacementErrorValidationSummaryProperty, value); }
}
In catel 3.8 the button is disabled at startup also if there are no errors. After I change something on the view the button is enabled.
In catel 3.6 the button ist enabled at startup if there is no error.
Coordinator
Dec 17, 2013 at 8:42 AM
Please create a separate ticket (with repro), then I can take a look.
Mar 19, 2014 at 12:04 PM
Hello again. No repro yet.

But one more information:

PlacementErrorValidationSummary.HasErrors
PlacementErrorValidationSummary.HasWarnings

Bot properties are undefined at startup. Not true not false.
Coordinator
Mar 19, 2014 at 12:06 PM
Not true and not false? That is weird because they are booleans and not nullable (meaning they must default to false).
Mar 19, 2014 at 1:09 PM
Yes you are right.

But if I bind this two Properties to a textbox no value is displayed at startup. I think ToString() should display true ore false.
Mar 19, 2014 at 2:05 PM
Ok PlacementErrorValidationSummary is null at starup. But how to initialize?
Mar 21, 2014 at 7:17 AM
Hello otherwise can you tell me when the ValidationSummary will be initialized?

Who does that?
Mar 21, 2014 at 10:26 AM