Home Dashboard Directory Help

Database Project in Solution breaks Page Inspector by CMOYA


 as Accepted Help for as Accepted

Sign in
to vote
Type: Bug
ID: 781504
Opened: 3/16/2013 4:22:09 PM
Access Restriction: Public
User(s) can reproduce this bug


A Solution containing both a Web Application and a SQL Server Database Project will cause an "Object reference not set to an instance of an object" error when you try to debug the Web Application using the Page Inspector option. It doesn't matter whether you set the Database Project to not do anything in Configuration Manager. (To see the error you have to restart Visual Studio after adding the Database Project).
Sign in to post a comment.
Posted by Microsoft on 4/29/2014 at 12:29 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from: http://go.microsoft.com/?linkid=9832436
Posted by Microsoft on 6/4/2013 at 4:08 PM
This is fixed in the latest Web Tools Extensions for Dev11 (1.3 version) which could ge got by installing the Azure SDK 2.0 bundle.

Thank you for your feedback.
Posted by Microsoft on 3/18/2013 at 12:35 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 3/16/2013 at 4:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
Posted by JimboSchneider on 5/22/2013 at 10:57 AM
Found a tip http://forums.asp.net/p/1894770/5402549.aspx/1?p=True&t=635048276960408798 The third post down suggests installing VS 2012 Web Express. I did this and now Page Inspector is working perfectly. Not sure what was missing that this wired up but it works.
Posted by luca morelli on 3/29/2013 at 11:32 AM
1. I open vs, start mvc app and I have the problem.
2. Unload the db project from the solution.
3. Start the mvc app and this time start.
4. reload the db project.
3. Start the mvc app and this time start.

Looks like that if I skip the point 3, I have still the problem.