Results 1 to 3 of 3

Thread: Guidelines required to design a System on VB.NET

  1. #1

    Thread Starter
    New Member
    Join Date
    Dec 2005
    Posts
    2

    Guidelines required to design a System on VB.NET

    I want to design a software witch works as a client-server system for the time being and later on web. As the client requests for a traditional UI i am looking for VB.NET forms on th client side. Also as this application is going to be hosted in the web I want the UI to be independent from Business and data layers. That is I want a three tier implimentation [Full OO way]for my system with VB.net forms [not web forms] as client and Business and data tier on the server.

    Please give me guidence how to approach this and how the components to be organised using VB.NEt

    Thanks in advance and Regards

  2. #2
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    111,221

    Re: Guidelines required to design a System on VB.NET

    Why is my data not saved to my database? | MSDN Data Walkthroughs
    VBForums Database Development FAQ
    My CodeBank Submissions: VB | C#
    My Blog: Data Among Multiple Forms (3 parts)
    Beginner Tutorials: VB | C# | SQL

  3. #3

    Thread Starter
    New Member
    Join Date
    Dec 2005
    Posts
    2

    Re: Guidelines required to design a System on VB.NET

    Thanks for the solution . I will try it out. But I would also like to know any other alternative to webserver and webservice? Is there any solution that can use VB.NET [not asp.net as resource may not be available immediately]itself as the business tier development tool.

    Regards
    Ajith

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width