tag:blogger.com,1999:blog-3718956085911858962.post2878682679332538284..comments2008-01-09T14:57:42.681+05:30Siduhttp://www.blogger.com/profile/11938300811286150164noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-3718956085911858962.post-31101251273824135952008-01-09T14:57:00.000+05:302008-01-09T14:57:00.000+05:30Jonathan,<BR/><BR/>Thanks for the explanation - that goes a long way toward sorting things out. :-)Siduhttp://www.blogger.com/profile/11938300811286150164noreply@blogger.comtag:blogger.com,1999:blog-3718956085911858962.post-73688111865976609372008-01-09T05:39:00.000+05:302008-01-09T05:39:00.000+05:30Sidu,<BR/><BR/>What is happening is that your browser is launching directly to the focused aspx view page, instead of calling the appropriate route.<BR/><BR/>To work correctly, the browser needs to first direct to the proper route. This will invoke the controller, which will in turn populate ViewData before passing to the view.<BR/><BR/>When you just browse to a aspx view page, no controller is invoked, and ViewData will be null.<BR/><BR/>This is not a bug, its just how Visual Studio (with its emphasis on Webforms) works.Jonathan Hollandhttp://www.blogger.com/profile/09327894878351516143noreply@blogger.comtag:blogger.com,1999:blog-3718956085911858962.post-88529879306804196102008-01-08T01:29:00.000+05:302008-01-08T01:29:00.000+05:30Nope, the error happens even when I'm not running in debug mode, the only difference is I get a stack trace in the browser.Siduhttp://www.blogger.com/profile/11938300811286150164noreply@blogger.comtag:blogger.com,1999:blog-3718956085911858962.post-28112750426160783172008-01-08T01:26:00.000+05:302008-01-08T01:26:00.000+05:30Is it trying to populate the Locals window?Dalehttp://www.blogger.com/profile/01854345391121255098noreply@blogger.com