ioc Discussions Rss Feed

New Post: At Workspace Add method, SmartPart added to RootWorkItem.SmartParts already exist

ctacke — Mon, 19 Nov 2012 18:50:08 GMT

Thanks for the report. I've included this fix in my latest check-in (earlier today).

New Post: At Workspace Add method, SmartPart added to RootWorkItem.SmartParts already exist

fduzceker — Wed, 14 Nov 2012 14:37:35 GMT

public void ShowControl()
{
// get smartpart from container
var existingPart = RootWorkItem.SmartParts["MySmartPart"];

// if we called "Close" on the SmartPart, it will no longer be in the collection
if (existingPart == null)
{
Debug.WriteLine("Recreating 'MySmartPart'...");

// Addnew smartpart and ObjectFactory.DoInjections working
existingPart = RootWorkItem.SmartParts.AddNew<UserControl1>("MySmartPart");
existingPart.Name = "MySmartPart";
}

// Show it

// WorkSpace Show ->OnShow -> Add -> RootWorkItem.SmartParts.Add and twice ObjectFactory.DoInjections working

// if there is a EventSubcription. Event invoke twice.
RootWorkItem.Workspaces[WorkspaceNames.Main].Show(existingPart);
}

I Changed WorkSpace.cs

/// <summary>
/// Adds a SmartPart to the Workspace without showing it
/// </summary>
/// <param name="smartPart"></param>
public virtual void Add(ISmartPart smartPart)
{
if (smartPart == null) throw new ArgumentNullException("smartPart");

this.InvokeIfRequired(d =>
{
var control = smartPart as Control;
if (control == null) throw new ArgumentException("smartPart must be a Control");

if (!SmartParts.Contains(smartPart))
{
smartPart.Workspace = this;
m_smartParts.Add(smartPart);

// I added if statement
if (!RootWorkItem.SmartParts.ContainsObject(smartPart))
RootWorkItem.SmartParts.Add(smartPart, Guid.NewGuid().ToString());
this.Controls.Add(control);
}
});
}

New Post: Defining what concrete classes implement what interface

ctacke — Tue, 13 Nov 2012 14:54:29 GMT

I believe you're asking how can you store many instances of a specific interface in the IoC DI container, correct? This is what the Items collection is for.

// create two items that derive from the same interface
IFoo a = new FooA();
IFoo b = new FooB();

// put them in the container. 
// use a unique name in case we want to get one by name later
// you can omit the name and IoC will give it one if you wish
RootWorkItem.Items.Add(a, "uidA");
RootWorkItem.Items.Add(b, "uidB");

// this will get just one item
var testA = RootWorkItem.Items.Get("uidA");

// this will get all items of a specific type
var foos = RootWorkItem.Items.Get();

New Post: Defining what concrete classes implement what interface

webber55 — Tue, 13 Nov 2012 09:57:26 GMT

There is an interface called IFoo and a class called Bar that can contain 0 to many instances of IFoo.

The class that implements of IFoo depends on what customer is using our product.

How can class Bar create 1 to many instances of the desired implementation of IFoo on demand?

I haven't been able to find cases like this in the documentation or the example projects.

New Post: KeyPreview

ctacke — Fri, 21 Sep 2012 18:00:39 GMT

The latest change set (just checked in) fixes the issue. It was due to the SmartPart not getting Focused when it was activated.

New Post: KeyPreview

webber55 — Mon, 17 Sep 2012 15:04:20 GMT

I had the same issue.

It can be reproduced by adding key events to the controls in any of the sample projects, where this issue occurs also.

New Post: Build 1.0.12221 is broken for MonoTouch.IoC project.

ctacke — Wed, 12 Sep 2012 14:40:29 GMT

I've not rebuild for MonoTouch real recently - largely because it means I have to get out the MacBook to do the build. All of the source is there and should be compatible (it all works with Mono for Android), so you should be able to just "add existing items" to get it building again. I'll look at getting the MonoTouch project files in the repository updated later in the week.

New Post: Build 1.0.12221 is broken for MonoTouch.IoC project.

sergii_iefimov — Tue, 11 Sep 2012 20:33:00 GMT

Hello,

Last night I have took last binaries and have not found any binary files for MonoTouch/IPhone , I also have not found any example which I can use this framework for IPhone using MonoTouch. So I took last sources and tried to build it on MacOS. I used OpenNETCF.MonoTouch.IoC project but unfortunately some files are missed, such as "Guard.cs" and "GenericEventArgs.cs". For the previous build 1.0.11235 we have the same problem: file "GenericEventArgs.cs" is missed.
Using commit history I have found this 69860 by ctacke
Associated with Release: Build 1.0.12221. Verified build success for FFx, CF, Mono and WinPhone
May be it's my mistake and I am doing something wrong?
It will be very helpfull to have some simple example for iOS platform.

Thanks.

New Post: WifiSurvey application broken

ctacke — Wed, 05 Sep 2012 14:03:01 GMT

I just verified that it runs fine for me. The exception you're seeing indicates that the AccessPointPresenter cannot be created because the DI container does not hold an IAPMonitorService instance. This means that the WifiSurvey.Infrastructure.Module module was probably not loaded. This is common if it's not deployed with the app. Put a break point in Module.cs, line 18 or so and I bet it never gets hit.

New Post: WifiSurvey application broken

webber55 — Wed, 05 Sep 2012 12:10:55 GMT

I downloaded the sample applications and have also tried to run the sample WiFiSurvery solution. I also get the above exception. I googled the exception message and found this page. The stack trace is below.

OpenNETCF.IoC.ServiceMissingException was unhandled

Message="Type 'AccessPointPresenter' has a service dependency on type 'IAPMonitorService'"

StackTrace:

at OpenNETCF.IoC.ObjectFactory.DoInjections(Object instance, WorkItem root)

at OpenNETCF.IoC.ManagedObjectCollection`1.Add(Object item, String id, Boolean expectNullId)

at OpenNETCF.IoC.ManagedObjectCollection`1.AddNew(Type typeToBuild, String id, Boolean expectNullId, Boolean wrapDisposables)

at OpenNETCF.IoC.ManagedObjectCollection`1.AddNew(Type typeToBuild, String id)

at OpenNETCF.IoC.ManagedObjectCollection`1.AddNew[TTypeToBuild](String id)

at WiFiSurvey.Shell.Views.APListView..ctor()

at System.Reflection.RuntimeConstructorInfo.InternalInvoke(RuntimeConstructorInfo rtci, BindingFlags invokeAttr, Binder binder, Object parameters, CultureInfo culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess, StackCrawlMark& stackMark)

at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

at System.Reflection.ConstructorInfo.Invoke(Object[] parameters)

at OpenNETCF.IoC.ObjectFactory.CreateObject(Type t, WorkItem root)

at OpenNETCF.IoC.ManagedObjectCollection`1.AddNew(Type typeToBuild, String id, Boolean expectNullId, Boolean wrapDisposables)

at OpenNETCF.IoC.ManagedObjectCollection`1.AddNew(Type typeToBuild, String id)

at OpenNETCF.IoC.ManagedObjectCollection`1.AddNew[TTypeToBuild](String id)

at WiFiSurvey.Shell.ContainerForm..ctor()

at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

at System.Reflection.ConstructorInfo.Invoke(Object[] parameters)

at OpenNETCF.IoC.ObjectFactory.CreateObject(Type t, WorkItem root)

at OpenNETCF.IoC.ManagedObjectCollection`1.AddNew(Type typeToBuild, String id, Boolean expectNullId, Boolean wrapDisposables)

at OpenNETCF.IoC.ManagedObjectCollection`1.AddNew(Type typeToBuild)

at OpenNETCF.IoC.ManagedObjectCollection`1.AddNew[TTypeToBuild]()

at OpenNETCF.IoC.UI.SmartClientApplication`1.Start(IModuleInfoStore store)

at OpenNETCF.IoC.UI.SmartClientApplication`1.Start()

at WiFiSurvey.Shell.Program.Main()

New Post: How to correctly Dispose SmartPart from Workspace

ctacke — Tue, 07 Aug 2012 14:26:15 GMT

First, sorry for my delayed reply. I've been busy with the ORM project and some other things.

Vincent, yes, you're right. The Dispose was redundant, and the ActiveSmartPart should be getting cleared. I've checked in changes for these and updated the WorkspaceDisposal sample app to show valid Closing of a SmartPart.

Marco, yes, the project is still active. There isn't a lot of activity in the code base because I think the library is pretty mature. If there are missing features, I'd be happy to add them, but we currently use IoC in all of our commercial products, so it's heavily used across many platforms. I've updated the SmartPartTests app to better handle when a SmartPart is Disposed. I'm not having any trouble running it multiple times.

New Post: How to correctly Dispose SmartPart from Workspace

mcNETCF — Thu, 21 Jun 2012 08:56:38 GMT

Hi everibody, is this project still alive ?

I'm facing the same problem as Vincent :

Can't understand how to add again a smartpart previously closed (which remains 'IsDisposed=True' as ActiveSmartPart).

I'm not able to run twice the SmartPartTests sample, too.

Any suggestion ?

Thanks

Marco

New Post: How to correctly Dispose SmartPart from Workspace

vramona — Tue, 06 Mar 2012 06:44:12 GMT

Hi Chris,

Still a little question. It seems that it's still not enough. Indeed, in Workspace.Close method, the smartpart I want to release is correctly removed and disposed (even twice), but it's still referenced as the ActiveSmartPart so when I try to display an other smartpart, it throws the ObjectDisposedException when in the Activate() method the framework find that the new smartpart is not the Active one, so he think it should DeActivate the Active one but it's the one he previously Remove, Closed and Disposed.

So I think that the Workspace.Close method should DeActivate the View and the DeActivate should make ActiveSmartPart to a null value.

Any comments ?

Here's a simple repro :

    public partial class Form1 : Form
    {
        private Workspace wks = new Workspace();
        private SmartPart spA = new SmartPart();
        private SmartPart spB = new SmartPart();

        public Form1()
        {
            InitializeComponent();
            Controls.Add(wks);
            RootWorkItem.Workspaces.Add(wks);
            wks.Show(spA);
            wks.Close(spA);
            wks.Show(spB);
        }
    }

As the Workspace.ActiveSmartPart has a private set I have no way with the framework to Dispose a SmartPart a soon as I don't need it anymore

What's your opinion ?

New Post: How to correctly Dispose SmartPart from Workspace

vramona — Mon, 05 Mar 2012 17:37:51 GMT

Thanks Chris for your reply

That's what I was looking for inside the source code.

So I've got a question : in OpenNETCF.IoC.UI.Workspace, inside OnClose(ISmartPart smartPart) method, at the end it's coded

RootWorkItem.SmartParts.Remove(smartPart);

smartPart.Dispose();

I think its redundant because in the Remove method of ManagedObjectCollection, IDisposable object are Disposed.

Finally I used Close in my application because, just calling Dispose cause runtime error on device when Showing another smartPart 'cause the IoC.UI Fwk try to make the disposed (but not removed) smartPart not visible.

Vincent

New Post: How to correctly Dispose SmartPart from Workspace

ctacke — Mon, 05 Mar 2012 16:36:14 GMT

You can call Dispose() as you would normally, but it is important to *remove* the item from the DI container before doing so, otherwise you'll end up getting an ObjectDisposedException when the framework tries to use the Disposed item. This is probably a scenario I should add better support for, as right now the general assumption is that you'll create the object, but never remove it.

New Post: How to correctly Dispose SmartPart from Workspace

vramona — Mon, 05 Mar 2012 16:27:24 GMT

What's the correct way to Dispose Views (smartparts) shown in DeckWorkspaces ?

Calling Dispose raise some errors at Runtime?

not Calling it means not disposing at all.

Do I need to use Close or DeActivate ?

What's the better way to do it ?

New Post: Improved support for WorkItems?

klei0777 — Fri, 24 Feb 2012 19:38:51 GMT

My original intention was to use the status of a WorkItem to control flow through individual use cases. However, after further investigation of SCSF, I realized that a SmartPart activates its parent WorkItem, even if you use the SmartPart from a different WorkItem. Our application currently has 1 DeckWorkspace and 50+ SmartParts, some of which are used in multiple workflows, meaning my original approach isn't going to work. I found an alternative solution but wanted to say thanks for the IoC Framework. It's been critical to the design of our application.

klei0777

New Post: Improved support for WorkItems?

ctacke — Wed, 22 Feb 2012 21:01:19 GMT

You're correct that we're not trying to make IoC be a mobile version SCSF. That said, if extending WorkItes would help you do your job, then it's definitely something we can consider. We'd need to know what type of support/extensions you'd be interested in. If you could create a very simple desktop app that shows your usage of a WorkItem, we can eitehr work to get it working under IoC or at least point you in the right direction.

New Post: Improved support for WorkItems?

klei0777 — Wed, 22 Feb 2012 19:42:51 GMT

Hi, do you have any plans to improve the support for WorkItems? There is a WorkItem class in the framework, but it lacks many of the features available in SCSF on the desktop, such as the relationship between a WorkItem and it's SmartParts and the ability to track status. I understand that the IoC Framework is not meant to be a mobile version of SCSF, but it would be useful to use WorkItem for building use cases like you do in SCSF.

Thanks,

klei0777

New Post: Ioc.Ui in WP7

ctacke — Thu, 01 Dec 2011 20:15:17 GMT

I had thought about it, yes, and it's still not off the table. The main issue is that Phone changes paradigms wildly with respect to screen creation, so it's not obvious that there are fully analogous pieces for the UI bits. The DI Container/EventAggregation stuff all works fine, it's just shoehorning the Workspace/SmartPart stuff in isn't 100% clear. Maybe a PivotWorkspace or a PanoramaWorkspace would make sense?