Matevž Gačnik's Weblog

Eric Maino writes about an obvious example of misleading writing on this Microsoft page.

I tend to agree. What should also be emphasized is that Web Services are not the only core feature of .NET. There's more meat behind the curtain.

After numerous unsuccessful attempts to contact the Microsoft UDDI team I emailed Karsten Januszewski directly and he managed to get it fixed in less than a day. Thanks Karsten!

We are now at level 2, so we can publish whatever we want. Currently we have seven services and this weblog registered.

What's interesting is that the UDDI categorization scheme seems to have changed. One can now do a successful search in InfoPath/VS.NET only if a service is assigned to wsdlSpec category.

Based on this and this, one can conclude that Avalon and Indigo are both based either on high level interfaces or Don/Chris have god-like memory.

I hope it's the former. It it is, it's going to be a jolly year. If it isn't and the memory statement is true, then Emacs support will drop.

My Inbox is drowning under Swen infected emails. It's getting serious, since I'm getting almost a mail per minute. It seems to me, that the intensity has doubled in the last few hours.

Virus/worm/trojan writers should be treated with <insert your punishment>.

We are unsuccessful with our emails to Microsoft UDDI team to upgrade our UDDI account to level 2 status. If anyone knows an appropriate contact or is able to help directly, please do so.

UDDI Provider name: Gama System
Current UDDI level: 1

The last post generated quite a stir, and I know why, but I deleted it anyway.

I'm actually not under Whidbey NDA, but to keep myself from disclosing something that is one month from being publicly available, and to keep everybody who has a hard time being silent about this happy, I'm shutting it down.

Thanks for reminding.

Since Jeff is having trouble finding a hotel for PDC, here's one I'm staying at. Reserved today.

While preparing for my Tuesday demonstration of XML features in Office 2003 I found out that Word XML namespace changed from: http://schemas.microsoft.com/office/word/2003/2/wordml to http://schemas.microsoft.com/office/word/2003/wordml.

It's not that I'm opposed to changing beta-time namespaces but all my documents, saved in Office 2003 beta2 as XML, won't open up properly in Office 2003 RTM. I have to change them by hand.

Another thing that pops a question is: What if Microsoft releases two Word versions within a year that need different namespaces? That has not happened yet, but this kind of namespace naming convention is not as flexible as a standard year/month, W3C like one.

Changing the namespace to http://schemas.microsoft.com/office/word/2003/10/wordml would break things too, but wouldn't brake the convention.

Conventions, especially namespace declarations, carry a semantic meaning and one should avoid breaking them.

Brad Abrams asks:

Then I thought I’d ask you folks – what do you value?  What gets you to give high marks on the session survey?  (we take that very seriously you know)..

Make demos simple. If possible write them by hand. Use as little as possible precooked. Describe every line, method and mechanism. Don't demonstrate 7 pages of code. Things can be done efficiently in 5 lines of code for demonstration purposes. Entertain.

Mono guys are dogfooding their own product. The Mono homepage is running on top of Mono ASP .NET implementation.

Bad news is: their site is down.

I just installed and used Skype beta and I like it.

Windows Messenger and it's voice calls are peanuts, compared to this app. Microsoft should embrace and extend again.

I fell asleep for a couple of days.

Jeff is doing a tremendous job with Snippet Compiler. I use this tool to show can-be-done-quickly demos. What makes is special? It sits patiently in my system tray, has the ability to increase font size and is lightweight. Just cool.

Now. What I miss is the ability to generate snippets from command prompt tools. Since code generation is the second best thing, I would like to click File/New/Snippet from Command Prompt and type "wsdl http://myserver/myservice.asmx" or "xsd /c myschema.xsd". Then I just need a simple cross referencing ability to compile my client and auto generated code. And yes, I know about the references textbox.

I also wonder if Jeff is still accepting donations. He managed to get that textbox control from Syncfusion donated, but a man can't eat .NET components.

Latest daily build of Mono already allows web service proxy creation, compilation and execution. I had to manually compile the wsdl.exe equivalent (called MonoWSDL.exe) and then do:

• mono MonoWSDL.exe http://www.gama-system.com/webservices/stockquotes.asmx?wsdl (outputs StockQuotes.cs proxy)
• mcs /r:/usr/local/lib/System.Web.Services.dll /t:library StockQuotes.cs
• write a simple console web service client app (StockQuotesClient.cs)
• compile it using mcs /r:StockQuotes.dll StockQuotesClient.cs
• run it with mono StockQuotesClient.exe NASDAQ MSFT

What did I get?

This:

That's sweet. But Mono can now also do it the other way around. I can generate proxies on our platform using the standard wsdl.exe tool. Mono web services test page looks like this:

When one adds the "?wsdl" suffix to a web service endpoint WSDL is returned as expected.

I like it.

[Note: http://www.gama-system.com/webservices/stockquotes.asmx is our free stock ticker web service]

To require a reboot for every security path installed is simply unacceptable. An OS like Win2K3 should never have to be rebooted and should be able to go a year or more without a reboot.
[Via: Sam Gentile's Blog]

This is so true. The frequency of patch distribution is too high for Microsoft to push "perfect OS - no patches needed" strategy. It is definitely more expensive (if not impossible, nowadays) to eliminate all possible buffer overruns in Windows Server 2003. Patches are here, and they will keep coming here for quite some time. We need a different application method.

Based on my previous posting I knew someone else would be affected too.

Today it was Pete Cole.

Here's my implementation of Microsoft.com Web Services client: http://www.request-response.com/playground/mscomws.

It's done manually:

1. Create SOAP Request
2. Get response
3. Scrape through response using XSLT
4. Generate HTML, using XSLT's for-each, value-of, concat, substring-before, ...
5. Insert HTML into .aspx page

I finally found some time, so I reorganized my site layout and updated some old, old pages with the new design.

Check out the playground section.

Since vdirs have been changed, my RSS Query web service is no longer available on http://www.request-response.com/webservices/rssquery/rssquery.asmx.

It has a new home: http://www.request-response.com/playground/rssquery/rssquery.asmx.

Two words: Jeff Key.

Version 1.4 of Snippet Compiler will be used in one of my next demos. If v 1.5 comes out with an option to halt the command prompt process (keep it alive) after ending (simple programmatic Console.Readline() injection would suffice), I will marry it.

In case you're wondering, how's the weather like here - in Ljubljana.

62 minutes ago, at 19:00 UTC, the wind was blowing at a speed of 0.5 meters per second (1.2 miles per hour) from variable directions in Ljubljana / Brnik. The temperature was 12 degrees Celsius (54 degrees Fahrenheit), and the pressure was 1,027 hPa (30.33 inHg). The relative humidity was 81.9%. There are no clouds below 1,524 meter (5,000 feet). The visibility was >10 kilometers (>6.2 miles).

Based on my last sentence in previous posting, this explains it pretty good.

Most favourite claims made by THOSE people:

• Microsoft doesn't respect its customers
• Products are unreliable and insecure
• Microsoft is evil
• Company's products are overpriced

It should be noted that we live in a market economy (most of us) and the will to change is not punished. Do it.