G
genc ymeri
Hello there,
What MS has designed/aimed/or assumed that programmers will use for .Net
'Applets' (equivalent of the Java applets) ?
IMHO, even though .Net has been around for years, most of the components (if
not all) for image manipulations, scanning for ASP.Net are still ActiveX
controls. I did google and there is no much information out there for
building .Net 'applets'. Basically those few links show how a winform
control can be run in IE . That's fine, I expected this in the first place.
But what it worries me is that (based on those links) there are so many
problems, especially with updating the .net framework from 1.1 to 2.0. In
that case the .Net 'applet' controls do not behave the same. (Also in
another link I read that in .Net 2.0, .Net 'applets' would not start running
unless clicked over .... or problems of other nature....)
Finding no much information from MS how to build .Net 'applets', it lead me
think that MS has done this deliberately when better approaches may be
available......(or I may have the wrong assumption )
Any inputs/tips/hints/opinions/links are very much appreciated,
Thanks in advance,
Genc Ymeri
Sr. Software Engineer
Reston, VA
PS:
We are trying to get rid of the ocx/activex(s) written in VB6 for image
viewing/scanning/annotations and other image manipulations. We still use
ActiveX/OCX withASP.Net. We hate the fact they need to be installed in
client machines but at this point I 'see' no better alternatives......
What MS has designed/aimed/or assumed that programmers will use for .Net
'Applets' (equivalent of the Java applets) ?
IMHO, even though .Net has been around for years, most of the components (if
not all) for image manipulations, scanning for ASP.Net are still ActiveX
controls. I did google and there is no much information out there for
building .Net 'applets'. Basically those few links show how a winform
control can be run in IE . That's fine, I expected this in the first place.
But what it worries me is that (based on those links) there are so many
problems, especially with updating the .net framework from 1.1 to 2.0. In
that case the .Net 'applet' controls do not behave the same. (Also in
another link I read that in .Net 2.0, .Net 'applets' would not start running
unless clicked over .... or problems of other nature....)
Finding no much information from MS how to build .Net 'applets', it lead me
think that MS has done this deliberately when better approaches may be
available......(or I may have the wrong assumption )
Any inputs/tips/hints/opinions/links are very much appreciated,
Thanks in advance,
Genc Ymeri
Sr. Software Engineer
Reston, VA
PS:
We are trying to get rid of the ocx/activex(s) written in VB6 for image
viewing/scanning/annotations and other image manipulations. We still use
ActiveX/OCX withASP.Net. We hate the fact they need to be installed in
client machines but at this point I 'see' no better alternatives......