This creates something called a web class. Which is a combination of an ASP web page and a dll file. It works well if there are not many updates. However you must re-register the dll every time you make a change. In order to do this you must stop IIS.
You basically create a template .asp file with some tags in it that get processed by your VB code. You find an example in the VB help file. One definite advantage is the speed at which it runs. You are executing a compiled dll and not interpreted ASP.
Thanks for taking the time to answer my question. I'm still a little confused though. What did you mean by:
"It works well if there are not many updates"
Not many updates to the database or to the compiled app?
I have a fairly large app in VB (uses a couple of FlexGrids & etc.) I developed and now "the man" wants it to work on the web. I need to do this, of course, as easy as possible but I want it to work well too.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.