I was looking at the solution for a Windows Server AppFabric class (from this Microsoft download) and found a funny namespace used for the WCF contracts:
http://www.demo.com/fourthcoffee/entities/1
First thought, isn’t the demo.com domain owned by the DEMO conference?
Uh, yup.
Not a good idea to use a “random” URI for namespaces.
The content for the class looks pretty good, but I’m surprised that neither Ron Jacobs nor Zoiner Tejada caught the problem namespace.
I’ve been looking a bit at .NET 4 Workflow Services as a part of AppFabric. I’m surprised to find no way to build these services from existing message contracts. I can understand imposing limitations on doing so – even that there might be no reasonable tool support – but this is a real stumbling block.
Certainly contract-first is not the only way to build services, but it is if you are implementing a published standard. Maybe there is some way to tinker around with the output of the tools sets to make a Workflow Service compatible with some existing WSDL, but would it be worth it?
One answer might be to put a pure WCF facade over the Workflow Services. Kind of a headache, but maybe workable.
This makes me think that .NET 4 Workflow Services are really targeted to be internal to the enterprise or at least where contract definition is flexible and controlled by one entity.
This follows a standard Microsoft pattern: help the enterprise dev in V1 and then expand from there. This strategy makes sense, I just want it all in VS 2010, not in V.next.
I am extremely annoyed with Windows Virtual PC.
It is markedly slower than Virtual PC 2007. And startup times are six to ten times worse. Same host, same VHD. Painfully slow.
I have witnessed this on three different host machines. I’ve seen other complaints of this online, but all of the suggestions of help completely miss the point.
There are some threads that suggest that it is caused by aggressive CPU throttling. In a comment on a post, Virtual PC guy suggested that installing SETI@Home might solve the problem. Seriously?
Virtual PC 2007 didn’t suffer from this problem, so I’m not going to bother with that. It would be great if I could find confirmation that either:
I have rolled back to Virtual PC 2007. I shouldn’t really care, except that I prefer the integration in Windows Virtual PC. I suppose I should move onto VMWare, but I really don’t want to hassle with this anymore. It works well enough for now.
Microsoft, are you acknowledging the problem? Perhaps you can blame it on the laptop vendors, but the customer experience is just terrible.
BTW: I recorded a video of starting a Windows 7 guest using Windows Virtual PC, but a 3 minute video of a crawling progress bar seemed intolerable.
Tags: Virtual PC, Windows, Windows7
FriendFeed Status
About me
Main feed
Email subscriptions
