CommonServiceLocator Discussions Rss Feed

New Post: Question about use of MefServiceLocator

jfraschilla — Sat, 04 May 2013 16:02:56 GMT

Why doesn't the compositionContainer get resolved in Class Foo shown below?

    class Program
    {
        static void Main(string[] args)
        {
            Test mytest = new Test();
        }
    }

    public class Test
    {
        public Test()
        {
            ComposeMefContainer();

            Foo foo = new Foo();
        }

        private void ComposeMefContainer()
        {
            CompositionContainer _container;
            var catalog = new AggregateCatalog(new DirectoryCatalog("."),
                          new AssemblyCatalog(Assembly.GetExecutingAssembly()));
            _container = new CompositionContainer(catalog);
            _container.ComposeParts(this);

            var mef = new MefServiceLocator(_container);
            ServiceLocator.SetLocatorProvider(() => mef);
        }
    }

    public class Foo
    {
        [Import]
        Bar abar;

        public Foo()
        {
            //I know I can do the following
            var bar = ServiceLocator.Current.GetInstance<Bar>();

            //Why doesn't this work?
            var compositionContainer = ServiceLocator.Current.GetInstance<CompositionContainer>();
            compositionContainer.SatisfyImportsOnce(this);
        }
    }

    [Export]
    public class Bar
    {
        public string Name {get; set;}

        public Bar()
        {
            Name = "Tom";
        }
    }

}

New Post: Is the strong naming key for Microsoft.Practices.ServiceLocation dll available?

freaksterrao — Fri, 15 Feb 2013 09:38:19 GMT

I have a .NET 4 application that uses Prism 4.0 and MEF.

We have a weird application crash (intermittent) where there is a NullReferenceException inside Prism code while accessing ServiceLocator.Current.

I wanted to do some changes in that code to introduce Interlocked.Exchange to see if it helps. However, the source code does not include the strong named key which means that I have to create a new key and rebuild everything that refers to Microsoft.Practices.ServiceLocation. (e.g. Prism dlls, my application dlls etc)

Hence the question, can the strong named key for Microsoft.Practices.ServiceLocation be shared here?

Also the exception call stack is:

A first chance exception has occured: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Practices.ServiceLocation.ServiceLocator.get_Current()

Which lead to:
System.ComponentModel.Composition.Primitives.ComposablePartException: An exception occurred while trying to create an instance of type 'GE.Energy.Framework.UI.Shell.Shell'. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Practices.Prism.Regions.RegionManager.CreateRegion(DependencyObject element)
at Microsoft.Practices.Prism.Regions.RegionManager.OnSetRegionNameCallback(DependencyObject element, DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e)
at System.Windows.DependencyObject.NotifyPropertyChange(DependencyPropertyChangedEventArgs args)
at System.Windows.DependencyObject.UpdateEffectiveValue(EntryIndex entryIndex, DependencyProperty dp, PropertyMetadata metadata, EffectiveValueEntry oldEntry, EffectiveValueEntry& newEntry, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType)
at System.Windows.DependencyObject.SetValueCommon(DependencyProperty dp, Object value, PropertyMetadata metadata, Boolean coerceWithDeferredReference, Boolean coerceWithCurrentValue, OperationType operationType, Boolean isInternal)
at System.Windows.Baml2006.WpfMemberInvoker.SetValue(Object instance, Object value)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetValue(XamlMember member, Object obj, Object value)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetValue(Object inst, XamlMember property, Object value)
at MS.Internal.Xaml.Runtime.PartialTrustTolerantRuntime.SetValue(Object obj, XamlMember property, Object value)
at System.Xaml.XamlObjectWriter.SetValue(Object inst, XamlMember property, Object value)
at System.Xaml.XamlObjectWriter.Logic_ApplyPropertyValue(ObjectWriterContext ctx, XamlMember prop, Object value, Boolean onParent)
at System.Xaml.XamlObjectWriter.Logic_DoAssignmentToParentProperty(ObjectWriterContext ctx)
at System.Xaml.XamlObjectWriter.Logic_AssignProvidedValue(ObjectWriterContext ctx)
at System.Xaml.XamlObjectWriter.WriteEndMember()
at System.Xaml.XamlWriter.WriteNode(XamlReader reader)
at System.Windows.Markup.WpfXamlLoader.TransformNodes(XamlReader xamlReader, XamlObjectWriter xamlWriter, Boolean onlyLoadOneNode, Boolean skipJournaledProperties, Boolean shouldPassLineNumberInfo, IXamlLineInfo xamlLineInfo, IXamlLineInfoConsumer xamlLineInfoConsumer, XamlContextStack`1 stack, IStyleConnector styleConnector)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
at GE.Energy.Framework.UI.Shell.Shell.InitializeComponent()
at GE.Energy.Framework.UI.Shell.Shell..ctor()
at GE.Energy.Framework.UI.Shell.Shell..ctor(IRegionManager regionManager, IEventAggregator eventAggregator)
--- End of inner exception stack trace ---
at System.ComponentModel.Composition.ReflectionModel.ReflectionComposablePart.CreateInstance(ConstructorInfo constructor, Object[] arguments)

This should not happen because:
Configuring ServiceLocator singleton had happened just before that which means that the ServiceLocator is set.

New Post: Portable version to support all platforms

FelixM — Sat, 02 Feb 2013 14:10:56 GMT

Cool! I found it. Thanks for the quick reply

New Post: Portable version to support all platforms

onovotny — Sat, 02 Feb 2013 14:05:03 GMT

Hi,

I packaged them up as Portable.CommonServiceLocator on NuGet until the official package is updated.

New Post: Portable version to support all platforms

FelixM — Sat, 02 Feb 2013 13:54:38 GMT

it's great that you built a PCL Version! However, it doesn't seem to be available on NuGet. Are there any plans to provide it via NuGet?

Thanks!

New Post: License

roman_d_boiko — Wed, 30 Jan 2013 13:32:32 GMT

New Post: License

roman_d_boiko — Wed, 30 Jan 2013 12:26:51 GMT

Would you mind changing license to MIT? Since CommonServiceLocator is referenced from Portable MVVM Light project which is MIT-licensed, everybody who uses the latter must now also accept Ms-PL which differs significantly.

New Post: Portable version to support all platforms

fcheung — Tue, 27 Nov 2012 21:39:11 GMT

The PCL version has been updated to include the NeutralResourcesLanguageAttribute.

New Post: Portable version to support all platforms

onovotny — Sat, 06 Oct 2012 17:55:28 GMT

The new PCL version is missing the NeutralResourcesLanguageAttribute. That's generating a compiler warning:

Warning 1 The assembly "C:\Users\Public\Downloads\CodePlex\MVVMLight\GalaSoft.MvvmLight\Portable\packages\Portable.CommonServiceLocator.1.2\lib\portable-net4+sl4+wp7+win8\Microsoft.Practices.ServiceLocation.dll" does not have a NeutralResourcesLanguageAttribute on it. To be used in an app package, portable libraries must define a NeutralResourcesLanguageAttribute on their main assembly (ie, the one containing code, not a satellite assembly). C:\Users\Public\Downloads\CodePlex\MVVMLight\GalaSoft.MvvmLight\Portable\packages\Portable.CommonServiceLocator.1.2\lib\portable-net4+sl4+wp7+win8\Microsoft.Practices.ServiceLocation.dll GalaSoft.MvvmLight.Test.Portable.WinRT

Can you please add the attribute and re-release the PCL binary?

Thanks!

New Post: Passing constructor arguments with StructureMap Adapter

Elmer59 — Thu, 13 Sep 2012 09:16:34 GMT

Hello

I have a class with parameter in a constructor
This class is Export by Interface in prism application -> [Export(typeof(interface))]

But I can't get this instance by ServiceLocator;



var newInstance = ServiceLocator.Current.GetInstance<Interface>(my parameter); ???????

??????



When remove parameter in a constructor my getinstance it's ok.

how will we do it?

Thanks.

New Post: Portable version to support all platforms

onovotny — Wed, 29 Aug 2012 18:42:28 GMT

Just wanted to update on this as with the RTM bits, IServiceProvider is in the PCL, so it's possible to target .NET 4, SL4, WP7 and Windows Store as-is. It would be great if you could publish an official portable version signed with the same key.

New Post: ServiceLocatorImplBase seems to break the contract of IServiceProvider

dot_NET_junkie — Mon, 30 Jul 2012 15:15:57 GMT

This has been discussed before here, and this design flaw has been confirmed by Glenn Block, the coordinator of the CSL.

Fixing this is a big breaking change, but not changing this IMO is not really an option, since the current implementation makes the abstraction unusable. For this reason the CSL Adapter for the Simple Injector does not inherit form the ServiceLocatorImplBase. Although the behavior of the Simple Injector adapter correctly implements the IServiceProvider contract, it is still unusable, simply because all other implementations break the contract.

New Post: ServiceLocatorImplBase seems to break the contract of IServiceProvider

FabianSchmied — Fri, 27 Jul 2012 12:08:28 GMT

IServiceLocator extends the BCL interface IServiceProvider. The IServiceProvider.GetService (Type) method is very similar to IServiceLocator.GetInstance (Type), therefore, ServiceLocatorImplBase's implementation of GetService simply delegates to GetInstance.

However, GetInstance is documented to never return null (it must throw an ActivationException). GetService, on the other hand, is documented to return null if there is no service object (no exceptions are documented).

Therefore, it appears that ServiceLocatorImplBase, and with it probably nearly all implementations of IServiceLocator, break the IServiceProvider contract.

Has this been discussed before? Can it still be fixed?

New Post: Are there plans to support Windsor Castle 3.0?

ffoozle — Wed, 16 May 2012 19:09:04 GMT

Windsor Castle 3.0 was released in Dec 2011. Are there any plans to update CommonServiceLocator.WindsorAdapter.dll to support Windsor Castle 3.0?

New Post: Portable version to support all platforms

dot_NET_junkie — Sat, 28 Apr 2012 14:05:11 GMT

I added an issue for this: Portable version to support all platforms.

Let's vote.

New Post: Portable version to support all platforms

kyleburns — Fri, 27 Apr 2012 12:20:06 GMT

New Post: Portable version to support all platforms

JimJams — Thu, 08 Mar 2012 15:04:36 GMT

New Post: Portable version to support all platforms

onovotny — Wed, 07 Mar 2012 18:04:15 GMT

I wanted to propose using the new VS 11 Portable libraries to enable a single instance of the CommonServiceLocator to work with .NET 4, SL4+, WP7.1+, WinRT and XBox 360.

The only breaking change is that IServiceProvider has been removed from WinRT and so isn't available for portable libraries. From an API perspective, in my test build, I simply moved the single GetService method to the IServiceLocator interface instead.

Between using it as a Portable Library and the removal of IServiceProivder, the changes would warrant a version bump to 2.0 to prevent accidental conflicts. If you can get that built and put on to NuGet, it would enable you to have a single binary that all platforms can reference.

New Post: Update for the NuGet package for .NET 2 support ?

styx31 — Tue, 24 May 2011 08:48:45 GMT

The current CommonServiceLocator package targets only specific framework versions NET35 & SL30.

A project for .NET20 can't use the nuget package (quite ironic since the release provided here is only for .net 2)

New Post: Query methods

gblock — Thu, 10 Feb 2011 19:46:52 GMT

Sounds like we might have messed up here. The idea of throwing an exception was an explicit design goal that we all agreed on. Making it implement IServiceProvider was more of a convenience, but sounds like this was overlooked. I imagine 90% or more of the people who use CSL don't use it as an IServiceProvider, however this is a good catch.