Matt:
You can also use a product called DesignBais. It handles most of the
issues you'll encounter going to a "stateless" environment. It has it's
own framework already built so you can piggyback right onto these
frameworks. It uses UniObjects and is easy to install and setup in a U2
environment (I don't know about other environments). It's fast and will
be able to handle your needs. Your learning curve will be significantly
lower than an ASP.NET environment, where you'll have to learn everything
and build your own frameworks to do most everything.
We use both ASP.NET and DesignBais and have found it significantly
easier to work with DB. This is because I don't have the time or
patience to become an ASP.NET expert and to build all the ASP.NET
frameworks required by any MV application. This is even true as we use
mv.NET for our ASP.NET connectivity. Without this "middleware" product
earlier development was pretty much impossible to get right using 3rd
party ASP.NET developers and me. But with mv.NET we're able to get
things done and I can manage all of the connectivity issues.
HTH,
Bill
------------------------------------------------------------------------
br...@brianleach.co.uk said the following on 9/23/2009 11:39 PM:
Hi
If you want a simple way to develop, check out [AD] mvScript [/AD].
Otherwise, UO.Net is easy to use but you will need to handle the concurrency
issues brought about by a move to a stateless environment: decide how you are
going to use optimistic locking and merging, and how to handle existing
subroutines that expect common block entries, user based lists etc. That's true
whatever you use for your development.
Note; If you are using UO.Net or UOJ for web development you need to have
connection pooled licences. Check out the text on your licence agreement:
anything else other than connect-on-demand is a breach (mvScript
supports both). Maybe Rocket will be more reasonable about this: personally I
think the cost of purchasing connection pools is unjustifiable in this market.
For the best results, RedBack/WebDE is scalable, fast and a very good model. It
is also mature (at least the RedBack part is) and has powered many websites very
successfully. Either that or UO.Net will be good, once you have mastered the
client langauge of your choice. ASP.Net has the advantage of being reasonably
simple, well documented with lots of blogs/examples etc on the internet. But if
you're handling lots of multivalued entries their data grid is just appalling:
expect to spend money on good components. And don't get the Microsoft self paced
materials - they are really, really terrible.
I've been working with Silverlight, and it's an uphill struggle to get anything
working - not that it is hugely difficult, just it takes sooo long to achieve
anything. Fine if you have large dedicated team of developers and designers, but
that doesn't sound like the situation here :)
Brian
On 23 September 2009 at 23:06 Matthew Day <matthew4...@ymail.com> wrote:
Hi,
We currently have a system with a VB6 front end and use Universe for the
database and business logic. We are looking to develop a web solution for our
product.
What are people using to inteface universe with the web, and what are your
experiences ( both good and bad ) with the route you have chosen.
Thanks,
Matt
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
