More Emails from the Edge:
Dear Ms. Manners:And since Ms. Manners was off boinking the postman, the milkman stopped by and was greeted by the open letter. Since the milkman was a technowiz in his own right, he decided he’d answer the question using Ms. Manners pseudonym, of course:
"Instead of asking about how long after Memorial Day is it proper to wear white, I thought I'd throw more of a twister at you. In two parts, here it goes: Was the patent for 'Emily' applied for after the XML Enabler or is it taking longer? And, if Emily was used to create XML enabler....and the XML Enabler is patented....how come Emily is patent pending? I don't understand the sequencing here. And finally, should I stop cheating on my boyfriend before he proposes or should I wait until after I receive the ring?" - Worried in Winnetka
Here's a hodgepodge of info about Emily and microsoft and their fragmented attempts to make sense of the mess they've found themselves in the middle.
The XML Enabler was granted and the Emily patent was declined by the USPTO on the contention Emily prior art is embodied in Frontpage. VCSY is pursuing the Emily patent further as the challenge against Emily centering in Microsoft's assertions Frontpage covers the claims made by Emily are obviously bogus ... of course, while Microsoft proceeds to put out a new kind of language environment NOT like Frontpage namely Silverlight. Aren't they smart?
BTW (psst)...The way MSFT is skirting stepping on Emily grounds is by keeping XAML out of the discussions when applied to their new "environments".
In fact, it's quite easy to watch and track where certain capabilities entered dotNet and when certain ones left so there should be no trouble in a court of law even if the patent examiner is cowed by MSFT "property".
Elemental issues (Emily is text driven more than graphical or "Visual".). Thus the construction process may be automated.
Using MSBuild is as easy as typing a few commands. It uses the following syntax:
MSBuild.exe ProjectBuild_File.proj /command-line_switch
There are various options available with the MSBuild program. Microsoft provides a great online reference (http://msdn2.microsoft.com/en-us/library/ms164311.aspx) of these options. Note that you don't have to use any of the command-line options unless necessary.
The build process in previous versions of Visual Studio was a kind of black box. Developers didn't know how it worked and they couldn't examine it or use it outside of the IDE. Version 2.0 of the .NET Framework changed it with the inclusion of the MSBuild build tool that is also used in the Visual Studio environment. It provides a consistent build process regardless of how or where the code is created.
Do you or your team use a build process for .NET projects? Do you utilize NAnt or other tools? Share your experience with the .NET community by posting to the article discussion.
And please note, Microsoft is not in a hurry to field their "products"
It's quite nauseating to watch MSFT verbally shift and shimmy to wiggle into the open so they can actually sell this thing.
Compelling cross-platform user experience
At the moment the Silverlight plugins (there are two versions: 1.0 beta and 1.1 alpha) will only work with Internet Explorer 6.0/7.0, Firefox and Safari. Apparently Opera will soon be supported as well.
Windows XP, 2003, Vista and Mac OS X 10.4 are the only compatible Operating Systems. There is no mention of Linux but as was reported in Ars Technica, Mono developer Miguel de Icaza has expressed interest in writing an Open Source Linux-compatible Silverlight implementation.
The Silverlight 1.1 alpha plug-in is about 4MB size (the 1.0 beta plug-in is 2MB) and is a snap to install. Microsoft claims that Silverlight will deliver “stunning user interfaces” and “incorporate video, animation, interactivity”.
...and this piece of crap article was posted May 15 2007! dotNet is "NEW".
What a laugh. This is one of the more fragmented attempts Microsoft has put out in a long time. The fact they are maintaining the "HTML" language references keeps dotNet in the FrontPage arena while their XAML scripting language squarely stands up against Emily... just with no place to go.
Microsoft's Dot Net Architecture (DNA - all puns deliberate, I'm sure!) lays the foundation and provides the tools to build just such an interactive "Web 1. Application". Dot Net provides the means to overcome obstacles that have traditionally been in the way of the development of true web based applications (eg "Session State" - more later!). In this series of articles, I will be taking a look at the building blocks of such an application, taking you step by step through it's development and introducing you to this immensely powerful technology that in this author's humble view, is going to open up new vistas of Internet use. To answer my earlier question, "can we start here?" - I believe this is an excellent place to start - in fact, if you have experience with other web application development technologies - set it aside! This is a new animal, and calls for fresh thinking.
So Worried, I hope that little smidgen of info clears up the Emily question. To answer your last inquiry, yes, get the ring and then dump the cheatin' son-of-a-b*tch...
Ms. Manners aka the Milkman aka Peninsula Port