asp/vb.net over vb.net app

  • Thread starter Thread starter gerryR
  • Start date Start date
G

gerryR

Hi All

Just a quick question from a beginner. I'm currently learning vb.net,
asp.net and sql in my own time.

I'm wondering, are there things you can do in a vb.net windows application
that you cannot do when using vb.net in an asp.net page?

If there arent, why would you program a vb.net application which needs to be
copied or installed to all machines that use it when you could program an
asp/ vb.net page that everyone can access.

If there are, are there many limitations of using asp/vb.net over vb.net
windows applications or is it just a few specific things?

Sorry if this is a broad question, I'm just looking for a general idea.

Thanks
gerryR
 
Gerry,

This was often a thought which started about 2000 when Net was starting to
become open for public.

As we are talking about a ASPNet application, we mostly speak about a HTTP
hypertext application (webbrowser), that gives unsufficient posibilities to
do the same as with a WinForm application. There has been actions to
integrate those two, but because of violating security this was impossible.

However, you can do all your actions with a WindowsForm aplication over the
Web, while installing a WindowsForm application is not that difficult
anymore as it was in past. Look by instance at Ms-Office, IE, Chrome and
other browsers. It is all done automaticly over the web with autoupdate.

On the other hand is the wish to do it with one program not stopped.
Therefore are the actions in WPF and Silverlight, however, those have not
yet all the possibilities and stability as ASP.Net and Winforms.

http://msdn.microsoft.com/en-us/netframework/aa663326.aspx

I hope this explains it a little bit.

Cor
 
Thanks for the info Patrice.



Patrice said:
This is very different. Ultimately an ASP.NET application renders HTML
markup and possibly JavaScript that is then handled by the browser. For
security reasons you can't access to local resources plus HTML is not as
rich as a Windows application when it comes to rendering the user
interface...

A third path could be to use a plugin such as SilverLight... So it
depends what kind of application you are doing but they likely still have
their own niche w<ith some overlapping for moderately complex
applications...
Click to expand...
 
Thanks for the info Cor.


Cor Ligthert said:
Gerry,

This was often a thought which started about 2000 when Net was starting to
become open for public.

As we are talking about a ASPNet application, we mostly speak about a HTTP
hypertext application (webbrowser), that gives unsufficient posibilities
to do the same as with a WinForm application. There has been actions to
integrate those two, but because of violating security this was
impossible.

However, you can do all your actions with a WindowsForm aplication over
the Web, while installing a WindowsForm application is not that difficult
anymore as it was in past. Look by instance at Ms-Office, IE, Chrome and
other browsers. It is all done automaticly over the web with autoupdate.

On the other hand is the wish to do it with one program not stopped.
Therefore are the actions in WPF and Silverlight, however, those have not
yet all the possibilities and stability as ASP.Net and Winforms.

http://msdn.microsoft.com/en-us/netframework/aa663326.aspx

I hope this explains it a little bit.

Cor
Click to expand...
 
Hi Gerry,

To add to the already excellent replies, don't forget that a web app runs
mainly on the server, it doesn'y use any of the processing power of you
local computer. This is fine for many applications, above all for those that
require/use a central database, but unless you use a Java app you cannot
harness your local processor for heavy work.

I have a fine example here of a windows forms data processing app that runs
on my computer (because I do most of the processing) but which also has an
interface via a web application on our intranet server so that people can
submit jobs remotely then pick up their results later.
 
There are many differences between a windows and ASP application. The main
advantages you get with Windows (VB.NET) application are following:
1. Application Performance : In Windows app, you do need to bother about the
load time, refresh, submitting a form to the server. Hence less coding and
you concentrate mainly on fulfilling functional needs.
2. Security: With ASP applications you have limitations and security
boundaries in terms of accessing local resources of user computer like
printer, file system of user computer, outlook etc.. But with windows
application these issues doesn't exist.
3. Web Server : For running ASP applications you need to have a shared or
dedicated web server. However for Windows app, you do not have a dependency
like this.
4. Scripting/HTML: There are certain pieces that needs scripting language
like (Javascrip/VB Script). Example mandatory fields validation on a form.
You should also be aware of scripting and HTML (to place controls) before
writing a web application.

So it is always good to go for Windows application if it has to be accessed
inside a local network. If you need an application to be available any time
any where, you should choose a web application.
 
gerryR said:
Hi All

Just a quick question from a beginner. I'm currently learning vb.net,
asp.net and sql in my own time.

I'm wondering, are there things you can do in a vb.net windows application
that you cannot do when using vb.net in an asp.net page?
Click to expand...

The main thing is keeping constant state with the application, which a
Windows application can do because it runs locally on the computer. As
opposed to an ASP.NET solution, a Web server doesn't keep state with an
application so that many users can use the same application on a Web server
with the Web server servicing many requests from clients.
If there arent, why would you program a vb.net application which needs to
be copied or installed to all machines that use it when you could program
an asp/ vb.net page that everyone can access.
Click to expand...

It would be done to let processing happen more at the workstation and use
the local compute's resouces and CPU power.
If there are, are there many limitations of using asp/vb.net over vb.net
windows applications or is it just a few specific things?
Click to expand...

ASP.NET lends itself well to SOA solutions and "cloud" technology, computing
services via the Internet, where as, the process are quick let them use the
service, get them out the way, drop the connection and process the next
request from a client, a volatile environment. Windows desktop solutions
lend them self well to process intensive or long running processes,
non-volatile environment.
 
Back
Top