This seems like an IIS issue so I am trying it here as a last resort. I have the following 2 "Jump to URL" expressions in a report: =BLOCKED SCRIPTvoid(window.open('http://www.google.com','_blank')) and =BLOCKED SCRIPTvoid window.open('http://barn/apx/PortfolioDetail.aspx?linkfield=749', '_blank') There...

For a complete walk-through of how to enable Visual Studio 2005 F5 debugging for ASP.NET applications running on IIS7 / Vista, check out this post: http://mvolo.com/blogs/serverside/archive/2006/12/28/Fix-problems-with-Visual-Studio-F5-debugging-of-ASP.NET-applications-on-IIS7-Vista.aspx . Thanks,

Larry, sorry for the late reply. The ASP.NET runtime issue I am referring to here has indeed been fixed for RC1. However, due to a number of changes in Vista security and IIS7, it currently takes a few extra steps to get VS debugging working. These are documented here: http://blogs.msdn.com/webdevtools...