That is what I am asking you. I already have been using msxml3 for client
side xml and xsl transformations. The questions was should I and can I use
the .NET framework client side in an IE6 environment.
As for narrowing the base it is not much of a concern in this project. But
using the same technology client side and server side has its advantages as
well! Things like integration, downstream support and upgrades etc become
more easily managed. Also due to the complexity of the some of the wizard
using custom controls will make life much much easier long term and require
less coding.
It may sound like I am sold on .NET client side but I assure you I am not.
What I am looking for is some advice on the benefits vs. drawbacks.
Narrowing of client base may be true now but may not be in the future as new
versions on Windows are released and .Net propagates more and more. This
project requires me to plan and program for tomorrow not now, which is a
nice place to be!
Keith
"Dimitre Novatchev" <dn********@yahoo.com> wrote in message
news:br************@ID-152440.news.uni-berlin.de...
Keith,
IE6 comes pre-installed with MSXML3.
Why should you artificially narrow down your user base by setting as a
requirement that the y should also have the .Net Framework installed?
=====
Cheers,
Dimitre Novatchev.
http://fxsl.sourceforge.net/ -- the home of FXSL
"Keith Chadwick" <kchadwick[nospam]@leewardsystems.com> wrote in message
news:Ot****************@TK2MSFTNGP12.phx.gbl... I have a several very extensive and complex wizard like interfaces I
have to right shortly which will require the user to have IE6. Each of these
interfaces will rely heavily on xml and xsl transformations for client
side rendering. The end result being a submitted xml file either via
standard http post to a aspx file or to a web service, not sure which yet.
My question is, should I go .NET all the way and require the user to
have the .NET framework installed. The original application used MSXML3.0
for all of the client side transformations and xml manipulation. In this
next version, assuming the user has the framework installed, can I use the
xml, xpath and associated .NET objects client side in Jscript? If so what I
would like to see is 'what are the benefits/drawbacks?'
Cheers
Keith
