This is a major political breakthrough. It is probably a fundamental change in the MS web marketing strategy. Finally, a client-side web browser framework that promises to work on most modern browsers! The "fear" of not shackling client-side web technologies
to MSIE seems conquered. Right?
I consider this an historic moment. The only negative bit is waiting for broad acceptance. When it goes pop, let's hope it won't suffer the fate of being called "AJAX" and credited to non-Microsoft entities. Let's not have LINQ become the DHTML of the
My quip says that this video shows that VB.NET is "responding" to some of the features of Python. This video pushes Channel9 to the edge... a very rough cut... all of us developers need better speaking/presenting skills...
The ASP.NET 2.0 features make this product look great. I am curious about how the installation procedure has changed. The SharePoint "tradition" makes many (like me) actually 'fear' installing Sharepoint. I will assume that this 'imagined burden' has no
basis with the new SharePoint...
This leads to the larger issue of installing/uninstalling Windows-based software. The X-Copy features of .NET applications
must influence new apps like SharePoint, making a clean uninstall perfectly possible.
I've been doing IT for healthcare here in Los Angeles for the last three years. In the University setting here, Microsoft has very little respect and takes a back seat to vendors like IBM, Sun and Open Source stuff. This make my political life difficult.
It's quite a different tablet world for that hospital for Microsoft employees.
It's great to have scientific evidence to back up what I dislike about "traditional management." I simply cannot stand that "randomizing" question, when the manager walks in the cube and asks "What are you working on?" He---and I do mean
he---should already know what I am working on! He needs to consult his metrics at his desk and then approach me more informed instead of with shock and awe. Of course the last sentence can be misinterpreted as an egocentric statement. Science to the
Here's a comment for the old school sages in the audience and I mean old school---and I mean sage: The ideals of Kim Cameron will never be acheived as long as egocentric, imperial consciousness is regarded as a 'legitimate' form of human expression. The
Kafka thang is irresistible to the imperial mind. It is not about the neo-(I need to watch my language) thing (that is just a homicidal work of art). It is about the neo-stasi thing... For you "normal," "regular" people in the audience. This whole post is
silly. You guys keep it real... But I will try anyway: when you call yourself a "regular" person that means you are a regulated and predictable person---you are civilized instead of heroic. This is exactly what any mass market company wants. To easily predict
earnings for shareholders, you need to predict the behavior of your customers. Such power of prediction is irresistible. So ya'll keep it real.
What on earth is wrong with managed code? What is your beef with VBA being ported as managed code into Visual Studio?
Nothing is "wrong" with managed code. In fact, I am translating a few thousand lines of VBA into C# tonight (just like last night). At bottom, my concern is that VSTO 2.0 may require me to translate my code again. Take this for example:
/// Returns a data-only Word XML string.
/// from the specified Word XML Node.
/// <param name="XmlNode">Word XML Node</param>
/// Unfortunately the C# version of VSTO 1.x does not support
/// the <c>Word.XMLNode.XML()</c> method and its "raw getter" is exposed
What's "wrong" with get_XML()? In VBA, it's XmlNode.XML(true). What I need to hear is that Microsoft is eager to hide the "raw getter" get_XML() and wrap it up in XML(). What may really happen, is that this syntax will be replaced with an entirely different approach
that is not compatible with VBA (and VSTO 1.x's incomplete translation of VBA functionality).
I still use VBA for my
Microsoft Word jaunts. And, as Microsoft’s Catherine Heller suggests on Channel9.msdn.com, the next version of VSTO will not radically revisit the extremely complex, application object model covered by VBA. It appears that the next version of VSTO
is preoccupied with all the stuff shown on Channel9 and the ‘boring’ task of making sure that managed code safely and completely replaces VBA appears to be an obscure edge case that about which ‘our’ Mort cares little. I do not find it impossible that Microsoft
will abandon VBA (and VBA-replication) entirely and force us to wait several years before there is a suitable replacement—an equivalent to what we now call “managed.” One possible path is that Office 14 (or maybe Office 12) will run entirely on managed code
and Microsoft will simply say, “Upgrade your documents to the new file format and write your new managed code against the new managed object model.” Microsoft will be successful in file-format backwards compatibility but the code will have to be rewritten—even
code written in C# or VB.NET for VSTO 1.x.