Visual Studio 2005 WTF indeed....



  • Today at work I was trying to add an Inherited Form to the application for a new process when I get this:

    Sorry for the crappy image, but the error message says "Object reference not set to an instance of an object" This one made me say WTF??!! out loud. I built the project (thinking this would fix the problem), no go, closed VS2005, then built the project, still no go. This one almost made my day 

     



  • I hate to say it, but I believe the WTF may be on your end, not VS.

    Since you are using an inherited form, trace back through all your references, I'm sure you will find one that isn't valid somewhere. 



  • KattMan,

    I've done that ahd have found nothing, it doesn't get far enough to allow me to select a form to inherit from. I've seen this before and rebuilding the solution always fixes the problem (things get a little wonky when multiple people are working on the same application in VSS) but nothing has fixed this. Rebuilding - NOTHING - Restarting then Rebuilding - NOTHING. Rebooting computer,Restarting then Rebuilding - NOTHING.



  • This happens all the time in ASP.NET when you do something the web forms designer doesn't like, such as not inheriting directly from System.Web.UI.Page. The web forms designer uses the attribute metadata to support the web forms designer, and attributes aren't inherited, so when you don't inherit from System.Web.UI.Page directly you lose designer support.

    The underlying WTF is the .NET platform. The platform designers missed the whole class on "why inheritance is useful" and invented vital class metadata that can't be inherited or directly copied.

     



  • Another serious wtf is using visual source safe, the worst product to ever come out of microsoft, including me and clippy.



  • @flukus said:

    Another serious wtf is using visual source safe, the worst product to ever come out of microsoft, including me and clippy.

    I completely agree, I've never liked VSS but this is what the company decided to use (since we are completely a MSFT house) 



  • Microsoft didn't write VSS from scratch... They bought it and modified it.

    One could argue that Visual SourceSafe didn't come out of Microsoft.  (Not directly anyways)



  • flukus: Another serious wtf is using visual source safe, the worst product to ever come out of microsoft, including me and clippy.

     

    What about Bob?

     

     


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.