{"version":"1.0","author_url":"https://blog.hatena.ne.jp/kkamegawa/","title":".NET Framework 3.5 SP1\u306eWPF\u30e1\u30e2\u30ea\u30ea\u30fc\u30afhotfix","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Fkkamegawa.hatenablog.jp%2Fentry%2F20100615%2Fp1\" title=\".NET Framework 3.5 SP1\u306eWPF\u30e1\u30e2\u30ea\u30ea\u30fc\u30afhotfix - kkamegawa&#39;s weblog\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","provider_name":"Hatena Blog","height":"190","url":"https://kkamegawa.hatenablog.jp/entry/20100615/p1","image_url":null,"categories":[".NET","C#","WPF"],"blog_url":"https://kkamegawa.hatenablog.jp/","provider_url":"https://hatena.blog","blog_title":"kkamegawa's weblog","width":"100%","description":"Memory Leak Hotfixes for WPF 3.5 SP1 - WPF Performance and .NET Framework Client Profile - Site Home - MSDN Blogs .NET Framework 3.5 SP1\u306b\u9069\u7528\u3067\u304d\u308b\u3001WPF\u95a2\u4fc2\u306ehofix\u3060\u305d\u3046\u3067\u3059\u3002\u3060\u304b\u3089code gallary\u3068\u304b\u3001connect\u3068\u304b\u3001\u30b5\u30dd\u30fc\u30c8\u7d4c\u7531\u3068\u304b\u3001\u7d71\u4e00\u6027\u306e\u306a\u3044\u30c0\u30a6\u30f3\u30ed\u30fc\u30c9\u3055\u305b\u308b\u306a\u3068\u2026(code gallary\u306f\u9055\u3046\u3093\u3067\u3057\u3087\u3046\u3051\u3069)\u304d\u3063\u3068\u793e\u5185\u898f\u5b9a\u3068\u304b\u3042\u3063\u3066\u306e\u3053\u3068\u306a\u3093\u3067\u3057\u3087\u3046\u304c\u3001\u306a\u3093\u3068\u304b\u306a\u3089\u306a\u3044\u3067\u3057\u3087\u3046\u304b\u306d\u3002 \u305b\u3081\u3066\u30b5\u30dd\u30fc\u30c8\u30da\u30fc\u30b8\u304b\u3089\u30e1\u30fc\u30eb\u30ea\u30af\u30a8\u30b9\u30c8\u3067\u30c0\u2026","author_name":"kkamegawa","published":"2010-06-15 00:00:00","type":"rich"}