Hi all, architectural question here. I have a custom web framework I'm
developing that defines its own component hierarchy - all working
quite smoothly.

Now I'm adding data binding to it and have found I can integrate the
data binding from System.Windows.Forms (BindingSource etc) quite
easily and of course all the nice IDE integration & designers come
with it.

What I'm wondering is will there be any issues with referencing
System.Windows.Forms assemblies in an ASP.NET application? it all
works quite nicely on my dev machine but would there be issues with a
real IIS server hosted on a commercial ISP? e.g. missing assemblies or
security issues?

I would *really* like to avoid cloning even a subset of the existing
Winforms database infrastructure.

Thanks,

Lindsay

Blackpaw wrote:

> Hi all, architectural question here. I have a custom web framework I'm
> developing that defines its own component hierarchy - all working
> quite smoothly.
>
> Now I'm adding data binding to it and have found I can integrate the
> data binding from System.Windows.Forms (BindingSource etc) quite
> easily and of course all the nice IDE integration & designers come
> with it.
>
> What I'm wondering is will there be any issues with referencing
> System.Windows.Forms assemblies in an ASP.NET application? it all
> works quite nicely on my dev machine but would there be issues with a
> real IIS server hosted on a commercial ISP? e.g. missing assemblies or
> security issues?
>
> I would really like to avoid cloning even a subset of the existing
> Winforms database infrastructure.

Databinding in Asp.net works via datasource controls. You shouldn't
use bindingsource controls etc, as these don't offer 2-way databinding,
datasource controls do.

FB


--
------------------------------------------------------------------------
Lead developer of LLBLGen Pro, the productive O/R mapper for .NET
LLBLGen Pro website: http://www.llblgen.com
My .NET blog: http://weblogs.asp.net/fbouma
Microsoft MVP (C#)
------------------------------------------------------------------------

"Blackpaw" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
| Hi all, architectural question here. I have a custom web framework I'm
| developing that defines its own component hierarchy - all working
| quite smoothly.
|
| Now I'm adding data binding to it and have found I can integrate the
| data binding from System.Windows.Forms (BindingSource etc) quite
| easily and of course all the nice IDE integration & designers come
| with it.
|
| What I'm wondering is will there be any issues with referencing
| System.Windows.Forms assemblies in an ASP.NET application? it all
| works quite nicely on my dev machine but would there be issues with a
| real IIS server hosted on a commercial ISP? e.g. missing assemblies or
| security issues?

In theory it should be ok. Both namespaces are part of the framework and you
know for sure it will be present.

But my advice is that you read how the web databinding works and implement a
similar feature. I personally would find weird a web framework using the
databinding mechanism from win apps.


--
Ignacio Machin
machin AT laceupsolutions com

dfghdfh

"Blackpaw" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> dfghdfh
>

Your welcome

On Feb 14, 1:27 am, "Ignacio Machin \( .NET/ C# MVP \)" <machin TA
laceupsolutions.com> wrote:
>
> Your welcome

Sorry - I wrote a long reply which went went missing and then a bit of
scribble to test posting

I've decided to follow your advice and research my own databinding
framework, though give the nature of my framework the winforms model
is a better match than the web framework.

Thanks - Blackpaw