Smart clients require client software that is Web-service enabled... like
the most current version of Microsoft Office, including Infopath.
These tools provide the richest user experience with the lightest download
to the client (e.g. the least maintenance cost). They are not difficult to
develop either.
The downside, of course, is that all users (now and in the future) have to
have the smart client installed on their system. If your users don't want
to upgrade to the newest Office software, then this won't work for them...
you will end up supporting two interfaces, which can be more expensive in
the long run.
Ask your users if they want to make the strategic decision to either support
a generic smart client like Infopath, or install .NET and a custom client
that you write, or just use a browser. They really should just pick one.
If it's the browser, then do a more fully developed .NET web application.
Of course, you should have as LITTLE code in the web app as you can. Make
your code-behinds call a seperate assembly where ALL the work is done. That
way, if your users change their mind about the GUI, you can post a new one
without having to rewrite the business layer.
And, of course, never have the GUI layer call the database objects directly.
Only the business layer can do that.
That will keep your options open, and keep your costs down.
Good luck,
--- Nick
"Duane Phillips" <as***@askme.askme> wrote in message
news:cVwAc.109100$3x.91977@attbi_s54...
Greetings.
Can an app be developed in .Net to deploy like local installed apps, and
then later reuse that code and object set to deploy on a web server?
I have read a little about WEB vs. RICH vs. SMART in .Net. Still vague as
to what path(s) to pursue.
Background:
We have an existing complex VB 6 app front end and MS SQL back end, that I
would like to convert to .Net, and then later deploy somehow on our .Net
web server... (currently have existing VB6 app available to the outside world
via a very restricted Terminal Server / Remote Application Server on
Win2KS). Actually there are 3 independent VB6 front ends for different
needs, but the same MS SQL back end.
We also have an existing ASP.Net web app (simple to moderate in detail),
but as thin as it gets... nottawholottabellsandwhistles.
We currently have about 50+ end user machines in house, and 4 remote
locations in different states of the US, each with anywhere from 4 to 10
PC's each, and several users who access this from their homes and mobile
computing devices.
Portions of this existing app are desired to be used by guests and
employees of other companies in the very near future.
TIA for any advice, and the most wi$e path(s) to reach the end goal$ over
the next 6 months, manpower notwithstanding.
--
~ Duane Phillips.
--
