Help getting started with a .NET app that runs in a browser.

[Fred Hebert]

30 minutes ago my boss asked me to develop a proof of concept application,
using .NET, that runs in a browser. The idea is that we want an easier way
to deploy application updates. We are thinking of having users connect to
our web server and execute a .NET app that would execute in the browser.
We could then upgrade all of the users just by updating the web server.

I don't expect anyone to do my work for me, but can you just point me to a
simple tutorial for a .NET app that runs in a web browser? My language of
preference is C++, and I have VisualStudio 2003.

I am just trying to get a quick start.

[clintonG]

I think this article [1] may be helpful.

<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee. com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/

[1] http://www.theserverside.net/article...?id=AppUpdater

"Fred Hebert" <fh*****@hotmai l.com> wrote in message
news:Xn******** *************** ********@207.46 .248.16...

30 minutes ago my boss asked me to develop a proof of concept application,
using .NET, that runs in a browser. The idea is that we want an easier
way
to deploy application updates. We are thinking of having users connect to
our web server and execute a .NET app that would execute in the browser.
We could then upgrade all of the users just by updating the web server.

I don't expect anyone to do my work for me, but can you just point me to a
simple tutorial for a .NET app that runs in a web browser? My language of
preference is C++, and I have VisualStudio 2003.

I am just trying to get a quick start.

[Cor Ligthert]

Fred,

What you tell is in my opinion the rich client idea. In my opinion a dead
child as is activeX. The problems with deploying because of the security are
in my opinion even worse.

http://msdn.microsoft.com/msdnmag/is...h/default.aspx

Try the idea as Clinton told. It is easy to make yourself by creating an
update program and a webservice. In the webservice you give the information
from new programs using an update program and according that you download
using your updateprogram the new programs.

The effect is the same as you see Microsoft doing it.

However, Microsoft is integrating this in the software, the name is "click
once" and there are application blocks for it.

http://msdn.microsoft.com/library/de.../updaterv2.asp

I hope this helps,

Cor

[Paul Daly (MCP)]

Create a webpage with a link to the executable on the network. Update the
network application whenever necessary.

The .NET Security on the clients will need to be adjusted to trust the
server on which the application is hosted.

Hope this helps,

Paul
"Fred Hebert" wrote:

30 minutes ago my boss asked me to develop a proof of concept application,
using .NET, that runs in a browser. The idea is that we want an easier way
to deploy application updates. We are thinking of having users connect to
our web server and execute a .NET app that would execute in the browser.
We could then upgrade all of the users just by updating the web server.

I don't expect anyone to do my work for me, but can you just point me to a
simple tutorial for a .NET app that runs in a web browser? My language of
preference is C++, and I have VisualStudio 2003.

I am just trying to get a quick start.

[jabailo]

Fred Hebert wrote:

30 minutes ago my boss asked me to develop a proof of concept application,
using .NET, that runs in a browser. The idea is that we want an easier way
to deploy application updates. We are thinking of having users connect to
our web server and execute a .NET app that would execute in the browser.
We could then upgrade all of the users just by updating the web server.

I don't expect anyone to do my work for me, but can you just point me to a
simple tutorial for a .NET app that runs in a web browser? My language of
preference is C++, and I have VisualStudio 2003.

I am just trying to get a quick start.

You should create a separate UI .exe and client .dll (or .dlls/assemblies).

The UI .exe could download and install new versions of the client .dll (
which contains all the critical funtionality and communications with the
source server). The *.dll could 'restart' the UI when the upgrade is
complete.

If you need to update the UI (which should be less frequent ) the .dll
will do that, and relaunch the UI as above.