Q

Guidelines for porting VB.NET desktop apps to ASP.NET Web apps

I am looking for guidelines in porting VB.NET desktop applications to ASP.NET Web applications. This is by no means

a definite checklist, but just a guide:

  • Isolate ALL business logic in standalone assemblies.

  • Take a look at the upcoming User Interface Process (UIP) application block from Microsoft. It helps in making the UI navigation independent of the target application type. This is very useful because controlling navigation in a Web application is very different from desktop apps.

  • Use code-behind files for ASP.NET server-side code. This makes it easier for a Web designer to work on the visual aspects of the page, leaving the server-side code for the application developer.

  • Identify most often used pieces of functionality and encapsulate them either in UserControls or CustomControls. This includes translating Windows Forms UserControls.

  • Security must be your top priority. Web applications are potentially exposed to the whole world. Evaluate the different options available in ASP.NET. Use Windows Integrated Authentication if possible (maybe your desktop app already does). This means the user accesses business logic (and databases if you use impersonation) with his own identity, and IIS takes care of the authentication in the most secure way possible.
  • This was first published in June 2003

    Dig deeper on Win Development Resources

    Have a question for an expert?

    Please add a title for your question

    Get answers from a TechTarget expert on whatever's puzzling you.

    You will be able to add details on the next page.

    0 comments

    Oldest 

    Forgot Password?

    No problem! Submit your e-mail address below. We'll send you an email containing your password.

    Your password has been sent to:

    SearchCloudComputing

    SearchSoftwareQuality

    SearchSOA

    TheServerSide

    SearchCloudApplications

    Close