Message="Could not load file or assembly myType.XmlSerializers"
The wacky world of serializers
Message="Could not load file or assembly myType.XmlSerializers"
Thumbnail = (
string)story.Element("thumbnail"), to Thumbnail = (string)story.Element("thumbnail").Attribute("src"),public Uri HrefUri{get{return new Uri(this.HrefLink);}}
The next trick is that when I double click the document the converter from the compatibility kit kicks in but then the dumb thing launches WordPad instead of the 2003 viewer. So currently I’m forced to open the viewer first and browse to the docx.
Ok, so if you read any of the SDK you’d figure it out, but I was interested to see if the approach had become…obvious, it hasn’t. For me it still remains the most cumbersome of the developer experiences but that’s probably more due to the improvements elsewhere against the relatively immature interface for Silverlight. I realise there is a lot more to think about but it still fills a bit clunky. I’d certainly like to see VS giving me member fields for controls rather than me having to code that manually via FindName. Still, I’m very excited to start some Silverlight projects in earnest, I’ve a couple of ideas, so hopefully…watch this space for some demos.
static void Main(string[] args)
{
Page page = new Page();
MockManager.Init();
MockObject sessionMock = MockManager.MockObject(typeof(HttpSessionState));
Mock pageMock = MockManager.MockAll(page.GetType());
pageMock.ExpectGet("Session", sessionMock.Object);
sessionMock.ExpectGetIndex("bert");
string value = (string)page.Session["bert"];
Console.ReadKey();
MockManager.Verify();
MockManager.ClearAll();
}
First off, you need to use the remote debugging monitor that ships with VS2008, although they look identical the VS2005 monitor won’t work with VS2008. Next problem is where to find the monitor. In VS2005 it was a separate install on the VS2005 setup disks, in VS2008 it’s installed into the common IDE folder under VS2008 (…Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\x86). You simply copy the files from there to the machine you want to monitor. As for getting it to use breakpoints and the like then it’s back to the old tricks of remote debugging. Basically to make life easy it’s much better to just rebuild the DLLs you’re interested in and ship them to the target…saves a lot of hassle.