C1 Community

Hello,

I have a MDI app which loads up Forms at runtime from their respective dll file.  Each Form object that gets instantiated is using any number of C1 objects (C1Chart, FlexGrid, CommandDock, etc.).  Each Form is then plugged into a C1Sizer object within the main MDI Container.  Essentially, there is a lot of nessting of GUI objects in particular C1 components.  The dynamic loading and functionality was working great until I upgraded from .NET1.x using VS2003 to .NET2.0 using VS2005. 

There may be some other factors at work here, but I've confirmed that the dynamically loaded Forms work fine as standalone apps.  The MDI container also works well when it's not loading any Forms with C1Components.  So, it seems that it's just the combination.  The error is caused when creating an instance of a Form with contains C1Components in the following code:

Activator.CreateInstance(/*name of form which uses a c1component.net2.0*/);

Thank you for your time.

-Stefan

This sounds interesting.

Can you post or send me a sample?



<roth.stefan> wrote in message news:186919@test.componentone.com...
> Hello,
>
> I have a MDI app which loads up Forms at runtime from their respective dll
> file. Each Form object that gets instantiated is using any number of C1
> objects (C1Chart, FlexGrid, CommandDock, etc.). Each Form is then plugged
> into a C1Sizer object within the main MDI Container. Essentially, there
> is a lot of nessting of GUI objects in particular C1 components. The
> dynamic loading and functionality was working great until I upgraded from
> .NET1.x using VS2003 to .NET2.0 using VS2005.
>
> There may be some other factors at work here, but I've confirmed that the
> dynamically loaded Forms work fine as standalone apps. The MDI container
> also works well when it's not loading any Forms with C1Components. So, it
> seems that it's just the combination. The error is caused when creating
> an instance of a Form with contains C1Components in the following code:
>
> Activator.CreateInstance(/*name of form which uses a
> c1component.net2.0*/);
>
> Thank you for your time.
>
> -Stefan
>

Well it turned out to be operator error.  I had not changed the C1 dlls from 1.x to 2.0 which was causing the load error.