I have created several VB .NET web applications and will soon have to
start building "real" executables. This may be involved, but how much
conversion is in a path like this? Is it simply recreating the GUI,
give the GUI controls the same name as in the web app and place the
code in different events than the ASP .NET page?

For example, I have an ASP.NET VB.NET web page, uses a database, etc.
The datagrid control, some textboxes, all that. There are events and
code in those events.

I need to take that page and turn it into an executable. Is this
huge, or is this more manageable because of the .NET platform?

Thank you.

Well it all depends on how your "old" applications are designed. If you have
a nice 3-tier layered application with a service interfaces layer for
example, you will only have to rebuild the GUI layer. But if you don't have
a layered application (e.g. opening connections and executing sql from a
webform) then you'll have to rewrite a lot more.

--
Greetz,
Jan
__________________________________
Read my weblog: http://weblogs.asp.net/jan
"jm" <(E-Mail Removed)> schreef in bericht
news:(E-Mail Removed)...
> I have created several VB .NET web applications and will soon have to
> start building "real" executables. This may be involved, but how much
> conversion is in a path like this? Is it simply recreating the GUI,
> give the GUI controls the same name as in the web app and place the
> code in different events than the ASP .NET page?
>
> For example, I have an ASP.NET VB.NET web page, uses a database, etc.
> The datagrid control, some textboxes, all that. There are events and
> code in those events.
>
> I need to take that page and turn it into an executable. Is this
> huge, or is this more manageable because of the .NET platform?
>
> Thank you.