Property imports will never be set while running the constructor, since you can't set properties on an object until it's constructed The other problem is that in InfModule, you are setting the exported value too late. MEF only looks at the value for an export once, after that it caches the value and doesn't call the getter again. In this case it is getting the export before Initialize() is called.
The logic to set the export needs to either run from the constructor or from code in the property getter.
Property imports will never be set while running the constructor, since you can't set properties on an object until it's constructed. The other problem is that in InfModule, you are setting the exported value too late. MEF only looks at the value for an export once, after that it caches the value and doesn't call the getter again.In this case it is getting the export before Initialize() is called.
The logic to set the export needs to either run from the constructor or from code in the property getter.
Thanks, that solved it. I initialized the MenuService in the getter and added the IMenuService as an argument to the ImportingConstructor in the module. I commented out the ModuleDependency line and it still works... not really sure why.
– Chris Klepeis Feb 8 at 16:35 1 @Chris Klepis: this is because the order of module initialization happens to fall where you want it. Adding the ModuleDependency guarantees the order will fall where you want it. If you truly have a dependency, you'll want to add that dependency back to ensure there are no issues later on.
– Anderson Imes Feb 8 at 18:27.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.