Archives / 2005 / July
  • Project and Solution Pain in 2005

    Does anyone know why you can no longer run a website as a class library in Visual Studio 2005?  Well you can, but WOW it is painful.

    I finally just took the Web ItemTemplates and put them in My Documents\Visual Studio 2005\Templates\ItemTemplates\CodeMakerX

    This at least allowed me to add Web items like WebForm, UserControls, etc.. to a Class Library.  The problem is that it doesn't work seamlessly like it did in 2003.  I have to put all of my code in App_Code, ok fine I can live with that.  What I find difficult to comprehend is that all those smart people at Microsoft missed the boat on the most effective way (albeit maybe this is just my opinion, but I know I am not alone ( to manage web projects.  None of the ItemTemplates for aspx|master pages work correctly in a class library, I also cannot nest related files (aspx files and their code behinds). 

    When it really comes down to it, Web Projects are the pretty much the same thing as Class Libraries with the addition of some deployable resources (.aspx|.ascx|.css|etc...).  I am trying to come to terms with the now project file-less web project and I really don't like it.

    This is a major annoyance and I hope it gets fixed soon.

  • Hiring Practices Discussion

    Rob and Ian are having a discussion over Good Hiring Practices here and here.  My two cents listed below...

    I don't think that Ian is correct in labeling these things bad practices.  I think that it really boils down to a people problem.  Rob likes to ask those questions because it lets him judge if he can work to solve problems with the person.  He doesn't care about the answers that the person provides, but more about way a person arrives at a particular answer.  If that makes Rob feel comfortable about hiring someone, how can you call that a bad hiring practice?  It has worked for Microsoft and countless other companies that practice it.