B
Blackpaw
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
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