Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 203
  • Last Modified:

Web Application in VB.NET

After I develop a windows (VB.NET Application) how do I make it a web application to run in the Intranet? Do I have to rewrite it from scratch or make too much modification to it ? How does this get achieved?

we have users in California/Texas/Florida/New york


Please explain with some step by step.

Thanks
0
jskfan
Asked:
jskfan
  • 2
2 Solutions
 
lostcarparkCommented:
I assume your application is currently a Windows Forms application.

If you want to make it available over an Intranet in its current form, you could roll out the application across the network (often not a preferred option as it requires the .NET framework to be on the client machines, requires them to be able to access relevant network resources, which isn't always possible, and requires you to maintain the .NET executables across the network, which can mean that users can end up out of sync with the current version.

A variation of this approach is to move the back end database access and business logic into a seperate middle tier, which you can deploy as a Web Service. This allows the Windows Forms client application to access it using only web protocols, which means that the application can work through firewalls. It also means that minor changes to the business logic can be rolled out without requiring any change to the client application.

If you want a full zero-footprint intranet application deployed through the web browser, you're probably going to have to redevelop the application as an ASP.NET application. This is quite similar to Windows Forms, but has a different set of controls, and a slightly different way of developing the application. Web applications generally won't have quite as rich a user interface as a Forms app, though this is gradually changing.

If you use the Web Services middle tier suggested above, it can actually be relatively easy to have both a Windows Forms app for power users, and an ASP.NET web application for the bulk of users, both running off a shared middle tier.

Finally, if you want a quick solution, you could look at deploying the application over Terminal Services or Citrix Server, which runs the Windows Forms app on a server, but displays the output on a client PC over an Intranet to Internet. This would allow you to give users full functionality of the Windows App, without requiring it to be installed on individual PCs, or requiring any redevelopment.
0
 
jskfanAuthor Commented:
<<<<Terminal Services or Citrix Server, which runs the Windows Forms app on a server, but displays the output on a client PC over an Intranet to Internet>>>>

1- TS are slow and I don't understand how do they show Windows forms as Web Forms. Can you explain this?

2-If I deploy Windows Forms application into clients and leave just the database in SQL Server, would this work without having to ocnvert to web application?


0
 
lostcarparkCommented:
> 1- TS are slow and I don't understand how do they show Windows forms as Web Forms. Can you explain this?

It won't turn Windows Forms into Web Forms, but it will allow the app to run without modification through a browser plugin.

> 2-If I deploy Windows Forms application into clients and leave just the database in SQL Server, would this work without having to ocnvert to web application?

It depends on your network.As long as the clients can connect to the SQL Server port accross the network, you should be okay.

If you moved the database access into a web service, you should almost certainly be covered, since even the tightest firewalls should let port 80 through.
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now