|Windows 7 - playing DVDs||Sunday 20th February 2011|
I recently tried to do something that I haven't done in a long time. Play a DVD film on my PC.|
I slotted in the disk, fired up Windows Media Player and bam:
"Windows Media Player cannot play this DVD because there is a problem with the digital copy protection between your DVD drive, decoder, and video card. Try installing an updated driver for your video card."
Hmph. Strange. A bit of rummaging suggests that the problem is related to Windows 7 not working with DVD-ROM drives that don't have region encoding (which should mean you can play a DVD from any region).
It's a bit of a bummer, but you can use VLC Media Player. Or alternatively use a program like DVD Shrink that will remove the copy protection from your DVD (and the added bonus of removing adverts, trailers, menus and other crap that really aren't required for a film).
|svcutil: Cannot import wsdl:binding||Tuesday 1st February 2011|
When trying to consume a web-service WSDL in Visual Studio 2010 I received an odd error, which also appeared when running the WSDL through "svcutil.exe".|
The WSDL adds fine using the "old" Add Web Service method, or in Visual Studio 2005.
Error: Cannot import wsdl:portType
Detail: An exception was thrown while running a WSDL import extension: System.ServiceModel.Descripti
Error: Object reference not set to an instance of an object.
There are a lot of topics on an exception being thrown, but these are generally namespaces or missing references. The Object reference not set is a horrible error that is the bane of my life as it could be anything. There is little on this combination of errors out there.
After some painstaking trial and error I narrowed it down to the XSD schema included in the <wsdl:types> section needed to have the attribute "elementFormDefault" specified at the root of the schema.
This resolved the error. I'm not sure exactly why this causes an error as it's not a required attribute in an XSD (as there are defaults) - and I have also seen other WSDL files that will import fine without this attribute specified. I assume it's down to complex types and namespaces - but I don't have the time (or need) to investigate further.
I hope this saves somebody else some time.