news:32CD03E9-6A17-40F4-8729-A565DE51647B@dotnet.itags.org.microsoft.com...
Quote:
Originally Posted by
>I have about 8 production apps, all small functional ones like "Expense
Claiming", "Invoicing", "Reporting" etc.
>
They are all asp.net and some are 1.1 and some 2.0.
>
I want to bring them altogether in a way that you have single sign on for
all of them (or even just the 2.0 ones if it makes it easier). How do I do
this, do I create a new ASP.Net solution with multiple projects in it? Do
I
use one website in IIS or can it handle the multiple websites I already
have?
>
I am thinking of creating a single home page with links to all the apps
that
will save poeple logging in multiple times.
I guess it will depend on several factors:
1) do they all use the same database or, at least, the same database server?
2) how "similar" are they in terms of look and feel?
3) how much effort would be involved in bringing the v1.1 apps up to
v2.0...?
4) how much time would you save in terms of maintenance and future
development, apart from the initial work involved of course, if you had one
single web app...?
I was presented with a very similar situation a few months ago by a new
client. They had a corporate intranet (of sorts!) written in something
called eQuercus (http://www.equercus.com - an absolutely dreadful product!),
plus a handful of small apps e.g. corporate reporting (sales figures etc),
expense claim management, investment fund management, staff directory, old
DOS-based Sun accounts system (yes really!), health & saftey procedures,
staff handbook etc. You get the idea - fairly common corporate intranet
stuff - but, because everything was in separate apps, maintenance was an
absolute nightmare! Loads of data was duplicated across the various systems
and databases, and it was in a right old mess.
In the end, it became obvious that by far the best solution was to
re-architecture a new integral application consisting of a single
multi-schema SQL Server 2005 database, a load of reusable base classes (DAL,
ADSI, Encryption, Mail etc), and a MasterPage / ContentPages scenario for
the presentation layer. The app now consists of a collection of reasonably
discrete but totally linked modules all driven from a single menu, all with
the same look and feel (obviously!), all sharing the same web.config
(obviously!) and no duplication of data."NH" <NH@.discussions.microsoft.comwrote in message
news:800B6730-01E9-4612-AF38-C9D695CE8DF6@.microsoft.com...
Quote:
Originally Posted by
Quote:
Originally Posted by
>1) do they all use the same database or, at least, the same database
>server?
They all use the same database server, and about 4 different databases on
that server.
If you are using SQL Server 2005, I'd be looking to rationalise these
separate databases into one single database with multiple schemas.
Quote:
Originally Posted by
Quote:
Originally Posted by
>2) how "similar" are they in terms of look and feel?
They are not totally the same in look and feel. There would be effort
involved to standardise.
Sure, but probably not that much, right...? Especially if you were able to
use MasterPage / ContentPages... The "top-and-tail" of the existing pages
could probably drop right into a ContentPlaceHolder with minimum re-work...
Quote:
Originally Posted by
Quote:
Originally Posted by
>3) how much effort would be involved in bringing the v1.1 apps up to
>v2.0...?
Not a huge amount. Nothing particualary amazing or complex going on in the
apps.
Well, as you're already using v2 for some apps, you're (probably) going to
upgrade the others at some point - now seems like the perfect opportunity...
:-)
Quote:
Originally Posted by
Quote:
Originally Posted by
>4) how much time would you save in terms of maintenance and future
>development, apart from the initial work involved of course, if you had
>one
>single web app...?
Not overly worried about this, I just want to enure the user gets the best
experience.
Don't you think that might be achieved by having all the apps in one place,
with a common look and feel...?
Quote:
Originally Posted by
So anyways, you think the best approach may be to start afresh?
Judging on what you've said, I think the best approach would be to
rationalise the separate apps into a single app. How much that involves
actually "starting again" will depend on how much of the existing stuff you
can re-use...
0 comments:
Post a Comment