Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Apr 27, 2012 05:51 PM by edowney10
Apr 27, 2012 05:15 PM|LINK
Hi Folks, I just migrated to a brand new PC at my office. I installed VS2010 copied my asp.net c# solution over and opened it up. Everything looked good. I F5'd it and everything seemed to work fine. Then I went to publish the website and bam! Publication
(web): Object reference not set to an instance of an object. What's that about??? How's that kind of error even possible during a publish? Certainly at run time but at the tail end of the publish?
So I scoured the interent in search of a solution to this perculiar problem. A lot of people said to dump the bin directories and start fresh. Done! Try cleaning the solution. Done! Stand on your head and drink a six pack. Too old for that! I even
went so far as to create a new solution and readd each of the projects and the website back in and recompile. Still won't publish.
Any suggestions would be greatly appreciated! This is now day three of banging my head against the wall...and it's starting to hurt a lot...
Apr 27, 2012 05:21 PM|LINK
Have you scoured the Package/Publish Settings to make sure there isn't any build events or weird Target Framework settings?
Apr 27, 2012 05:51 PM|LINK
Do you mean View/Property Pages? I hadn't looked at that previously. Looking at it now I didn't see anything odd or out of whack. In the references section there are some System stuff (System.Design, .Drawing and .Security) that are listed as version
18.104.22.168 while others are listed as 22.214.171.124. It's in the GAC. I also have 7 other projects that are part of this solution. Some are used by the website while others are used by each other - I'm running an NHibernate DDD website application for the State
What would be really helpful would be if VS would give some more detailed info like what object is it having issues with - or even which project was having the issue. It's a huge site so it's kind of daunting to pin point where the actual problem is located.