Re: SQL Server Express: Anybody Using It?



"ed.markell@xxxxxxxxx" <ed.markell@xxxxxxxxx> wrote in
news:1140706473.990566.207500@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:

David W. Fenton wrote:


My bet is that these web pages Lyle is creating use proprietary,
IE-only coding that won't run in any other browser, which makes
it completely unacceptable as far as I'm concerned, since IE is
not an acceptable browser for use by anyone (and IE7 isn't going
to change that -- the problems are too fundamental to the design
of IE and Windows).

Visual Studio 2005 produces compliant HTML by default, at least in
my experience. . . .

But it's styled by CSS, no? And IE6 is the least CSS-compliant
current browser out there.

Secondly, there's JavaScript (or, if VS is really stupidly designed,
JScript or VBScript), which is not cross-compatible between IE and
other browsers if the IE-only document model is used.

If it were just pure HTML, then it wouldn't be very useful at all,
so I can only presume that people are getting excited about VS
producing something a lot more elaborate than plain old
garden-variety HTML, and that means client-side scripting with
CSS/CSS2.

. . . Obviously the developer needs to deal with different
browsers, and the lack of standards compliance in IE is a definite
issue. But the built in controls provided by ASP.NET produce
compliant HTML, using VS 2005 and the .NET framework 2.0 (and the
IDE flags bad markup).

Eh? How does the client side of an application delivered in a
browser depend on the .NET framework? That's even worse if it does.

As to the "built in controls" what does that mean? Does something
have to be downloaded, or are these predefined classes that your
code can use to get extended functionality from the standard widgets
plus DHTML?

I'm not commenting on the time to develop required by these
platforms at all, just adressing that one issue.

You haven't really said anything that convinces me that VS is
producing good cross-browser code. If it renders differently in IE
than in FireFox, then it's not properly compliant. Based on my
experience with Outlook Web Access in IE vs. other browsers, I'd be
very surprised if MS would sacrifice additional functionality just
so that the code was not IE-specific. It would go against the whole
organization of all MS product lines, which is to decommoditize
standards and force you to build into your apps dependencies on MS
technologies and products (unless you sacrifice functionality).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.



Relevant Pages

  • Re: Using VS2005/C++, how to create a function call (directed) graph or cross ref. table
    ... it is not practical for producing a total function calls graph (or cross ref. ... You can use call browser, which is part of VS2005 IDE. ...
    (microsoft.public.vc.language)
  • Re: Why should I eschew prototype.js?
    ... relieves the developer of the effort of considering browser quirks ... The code required to perform some common and repeated javascript ... commonly-used functionality so access to that functionality is shorter ...
    (comp.lang.javascript)
  • Re: OT - Re: Internet Explorer 7
    ... And encryption isn't one of those mechanisms. ... and Firefox doesn't display it in the same broken way that IE does. ... I'm focusing on functionality. ... broken browser and it renders as they expect there, ...
    (rec.collecting.coins)
  • RE: Doc collaboration, how to group-edit a document via only a bro
    ... entirely from within a browser. ... We tried the threaded discussion functionality. ... Simply using the Basic Page as the document template doesn’t accomplish the ... Should we not be trying to use MOSS 2007 for this? ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: single page apps, URL hash setting, bookmarking, & the back button.
    ... bookmarking of url's to return to a given page in a web site/app in a ... Your argument is that this functionality shouldn't even be required, ... ignore those browser problems and just not support those browsers. ... if it already works _with_ these hacks? ...
    (comp.lang.javascript)

Loading