VB.Net on the network

  • Thread starter Thread starter Marcus via DotNetMonster.com
  • Start date Start date
M

Marcus via DotNetMonster.com

We have 200+ concurrent users. We are looking at using Oracle database as
the backend and VB.Net on the network as the front-end. Does anyone know if
this will work and how?

We will go to the web in a couple of years, but right now we are limited to
the network with concurrent users of up to 200+.

Thanks,
Marcus
 
We have only 4 weeks to deploy this application on the network. The company
intranet is controlled by our IT department. To deploy ASP.Net on the
web/intranet means IT would need to prioritized the work and put the project
into a pool of project which could take up to 6 months to deploy.

Can an ASP.Net application can be deployed on the Network? with 200+
concurrent users?

Thanks,
Marcus
Make an internal ASP.NET web application. No problem.
We have 200+ concurrent users. We are looking at using Oracle database as
the backend and VB.Net on the network as the front-end. Does anyone know
Click to expand...
[quoted text clipped - 7 lines]
Thanks,
Marcus
Click to expand...
Click to expand...
 
We have only 4 weeks to deploy this application on the network. The company
intranet is controlled by our IT department. To deploy ASP.Net on the
web/intranet means IT would need to prioritized the work and put the project
into a pool of project which could take up to 6 months to deploy.

Can an ASP.Net application can be deployed on the Network? with 200+
concurrent users?

Thanks,
Marcus
Make an internal ASP.NET web application. No problem.
We have 200+ concurrent users. We are looking at using Oracle database as
the backend and VB.Net on the network as the front-end. Does anyone know
Click to expand...
[quoted text clipped - 7 lines]
Thanks,
Marcus
Click to expand...
Click to expand...
Click to expand...

You have two options here:
1) Create a ASP.NET application, using VB.NET (Since i gather you have
vb.net skills in house). Deployment becomes as simple as giving a URL to
your users
2) Create a Click Once .NET Application, to simplify deployment. Again
deployment would be pointing your users to the setup URL
 
Back
Top