Written by: Matthew Hile 7/30/2008 5:41 AM
I was working on a new DNN module and had made a variety of changes. I clicked the debug button to get a fresh build to test and ... nothing. My build failed but there were 0 errors. So I dumped the web cache, restarted IIS rolled back of the code to a previous version and ... "build failed" 0 errors. Doing a search, I found that this was not a unique experience (with as many folks as there are doing development how could there be a unique experience - we all share the same pains). The kernel of my solution was found in this post. The steps in Visual Studio (2008 is the version I am using) that did the trick were: Tools > Options Projects and Solutions > General Check the box for "Show Output window when build starts" Projects and Solutions > Build and Run (if you do not see the last option make sure that the "Show all settings" check box, at the bottom left of the Options window, is checked.) Set MSBuild project build output verbosity to "Diagnostic" In my case at least, this gave me enough information to figure out where I was failing and got me on the road to fixing the problem.
I was working on a new DNN module and had made a variety of changes. I clicked the debug button to get a fresh build to test and ... nothing. My build failed but there were 0 errors. So I dumped the web cache, restarted IIS rolled back of the code to a previous version and ... "build failed" 0 errors.
Doing a search, I found that this was not a unique experience (with as many folks as there are doing development how could there be a unique experience - we all share the same pains). The kernel of my solution was found in this post. The steps in Visual Studio (2008 is the version I am using) that did the trick were:
In my case at least, this gave me enough information to figure out where I was failing and got me on the road to fixing the problem.
0 comments so far...