eogar
April 28th, 2003, 03:37 PM
My company is moving to the .Net platform in "two releases" but I am required to write a new component for a JSP-based application in the "next release." I am trying to minimize my future pain by writing the component so that it will be usable by either (though I am not too familiar with .Net yet).
What is the best way to go about this? Write it as an ActiveX component? Is there another .Net web-component better suited to this problem?
Thanks for the help.
What is the best way to go about this? Write it as an ActiveX component? Is there another .Net web-component better suited to this problem?
Thanks for the help.