tag:blogger.com,1999:blog-652174954000901332.post8662917128792011039..comments2008-10-09T09:02:51.985+01:00Øyvind Vallandhttp://www.blogger.com/profile/17595718624373482981noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-652174954000901332.post-84152505882970056082008-10-09T09:02:51.985+01:002008-10-09T09:02:51.985+01:00thanks man, glad you've wrote about it. keep the good stuff coming ;)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-652174954000901332.post-28935805308239140682008-10-02T17:19:54.485+01:002008-10-02T17:19:54.485+01:00thanks! Great help!Krishna.Khttp://www.blogger.com/profile/00247531300407419302noreply@blogger.comtag:blogger.com,1999:blog-652174954000901332.post-63842405242563743342008-09-25T22:25:10.035+01:002008-09-25T22:25:10.035+01:00Hello guys,<BR/><BR/>I'm glad that this is of help. The real thanks goes to Steve F, though - for finding this fix. I'm just a messenger. Now if only Steve would set himself up with a blog...<BR/><BR/>Anyway, it <I>does</I> appear that this fix isn't universal, meaning that it doesn't work for everyone. I can only say that if you find another fix, please post it on forums.asp.net, and put a comment here with a link as well so that people can find it.<BR/><BR/>Hopefully ASP.NET MVC will be in BETA soon, and then I'm sure these problems will be gone!Øyvind Vallandhttp://www.blogger.com/profile/17595718624373482981noreply@blogger.comtag:blogger.com,1999:blog-652174954000901332.post-981653433177450572008-09-25T22:19:56.521+01:002008-09-25T22:19:56.521+01:00Thanks!!!!!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-652174954000901332.post-14708233435502021622008-09-24T19:49:32.328+01:002008-09-24T19:49:32.328+01:00I had same problems and posted my workaround on forums.asp.net. In my case, that workaround wasn't enough.panjkovhttp://www.blogger.com/profile/05065847524689205579noreply@blogger.com