I thought at the time the decision was pretty much final. We have no advantage to tell you we wont have it and then produce it magically. At the same time I didn’t want to give you false hope. Seven weeks ago we were starting the long process of certifying the November release. When that happens most things go on hold until after the release. Of course we still have teams on some big items but many of the smaller features get put on the back burner. Right before then we had researched doing out of browser but could not find a way to pull it off within the licensing parameters we had. At that point I didn’t want to say well wait for 4-6 week and then we will have it, as I thought it was not going to be possible. As with so many things the answer came when we stopped beating our heads against the wall looking for it. A few days ago one of the guys here noticed one of the new feature on Silverlight 4 and it clicked to him that we could use that as a mechanism for our licensing. Of course once that happened, as the release was out, we jumped on it and implemented it, you should see it on Monday. I always try and give our customers the straight shot as to what I think is going to happen and I am typically an optimist.
As to your project, I don’t think it was a bad decision to write it in WPF. First off if you have a Silverlight app you can try the out of browser and see if it meets your needs and it can offer a backup plan to your current development. Second the WPF is more advanced and should be faster the the Silverlight Edition. Silverlight is still constrained in a number of ways and is slower to disk access etc than WPF, drawing sytem is slower etc. If I were a betting man I would bet that you will eventually find some feature you need that you could not do in Silverlight and you are going to be glad you have the full desktop power in WPF.