Skip to main content

WCF services and Windows Mobile

Windowsmobilecrap

Been having problems with setting up of the above. Very upsetting. Well, the problem is more because we need it to use secure transport. We have set the WCF service up on our test server, and switched https on and made (what I think are) the correct changes to the config. I then created a test certificate and private key. These were a cer file and a pvk file which I had to perform some magic on to turn into a pfk file. We then put this on as the certificate on the website and also put the certificate on the handheld (which just in itself was a pain in the buttocks as it only wanted to accept the cer file). Anyway after a lot of messing about we still get denied.

The error I get is something along the lines of??Could not establish trust relationship for the SSL/TLS secure channel with authority

Most annoying. I have a feeling that this is because the test certificate we have is not a trusted certificate and when the handheld tries to make the connection it checks for this and falls over. I have tried overriding this check to no avail. In the full framework you can use other cheeky methods and get round this problem but there seems to be some important libraries missing on the compact framework.?

Anyway this isn't going to happen for this release now but I think it's something we need to do in the future. Of course it's possible I'm just going about it in completely the wrong way. grrrrr

Comments

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second