Website won't build -- build failed with no errors, warnings or messages (VS2005)

Discussion in 'ASP .Net' started by Guest, Aug 2, 2006.

  1. Guest

    Guest Guest

    I'm having a problem finding the cause for this problem. I have a solution
    in Visual Studio 2005 that contains two projects -- a Web Site and a Class
    Library. The web site references the class library.

    After the project became larger, the build process would sometimes fail with
    no errors. The "quick fix" for this was to rebuild the whole solution and
    things seemed ok. When this didn't solve the problem any longer, I went to
    the property pages and changed the build action (F5) to Build Page and not
    Web Site. After running it once successfully, I changed it back to Web Site
    and then the build process did not fail. Great!

    Still, this leaves me with no answer since I didn't actually find the cause.
    What happened?

    Any advice appreciated!
    Guest, Aug 2, 2006
    1. Advertisements

  2. Hello Kenneth,

    Based on my understanding, you will encounter some problem on web
    application building/compiling (ASP.NET 2.0/VS2005) when the project grow
    large. As for ASP.NET 2.0 web project( web site application), it has been
    much different from the original 1.1/vs 2003 one. In VS 2003/ 1.1
    web project, when we build the project, it will compile all the codebehind
    files and generate a main project assembly(the same as other .net project
    such as winform or console project).

    While in ASP.NET 2.0/VS 2005, this is not the case, the 2.0 web project use
    dynamic compilation by default, so it do not require us to precompile a
    website at development time. When we use "build" command to build the web
    site application in VS 2005(or use ctrl+F5 to start a page), it actually
    perform all the dynamic compilation which will also be done at runtime
    (after deployment). And if there is any error during the whole web
    application's dynamic compilation, it will report error. (when we only
    select one page in the solution explorer to view, it will be opened in
    webbrowser and only this certain page and the resource such as ascx it
    references will be dynamic compiled). This is the difference between "view
    a page" and build the whole project(or use ctrl+F5 to start a page).

    Here are some articles which are helpful on clarify the build/compilation
    of ASP.NET 2.0 web project:

    For your problem here, I'm wondering the detailed symptom and behavior when
    you get the error:

    After the project became larger, the build process would sometimes fail
    no errors.

    I know it may be difficult for you to create a simple reproduct project
    since it occurs when the project grow large. So you can provide us some
    detailed info on how the problem occurs, for example, after the silent
    build error, will it cause a page display incorrect or report a compilation
    error on the browser screen?

    Also, ASP.NET 2.0 project support precompilation, through the
    aspnet_compiler.exe or the "Build--->Publish Web Site" IDE menu item. Will
    these precompilation options also behave incorrectly when that problem

    BTW, there is an add-on project for precompile ASP.NET 2.0 web application
    which provide more customization options. Here is the link to is in case
    you haven't had a chance to have look:

    #Visual Studio 2005 Web Deployment Projects

    Please feel free to post here if you have any other finding or any other
    information you wonder.


    Steven Cheng

    Microsoft MSDN Online Support Lead

    This posting is provided "AS IS" with no warranties, and confers no rights.
    Steven Cheng[MSFT], Aug 3, 2006
    1. Advertisements

  3. Guest


    Nov 15, 2006
    Likes Received:
    0 2.0 Build fails, but no error

    I was having the same issue.

    First Narrow it down to the suspect page...basically right click on every page in the project and click build...find the one which the build fails, but oddly enough not giving any errors or warnings...

    Go to the code, comment out all of the code...
    Build page...
    Probably get a nice page of warnings...
    Uncomment all the code..
    rebuild page...
    Page should now build correctly...

    I have NO idea why, but this worked..

    NewLaw, Nov 15, 2006
  4. Guest


    Apr 16, 2007
    Likes Received:
    Same problem different solution

    I ran into the same problem today, unfortunately when I went page by page through both projects in my solution, every page built successfully. After I went through all pages and the ran build on both projects the site would open in the debugger. I had to do this every time to run the solution.

    I did however find an issue that once resolved, made the problem go away. I had a class file in my app_code directory with a class declaration that had the same name as one of my partial class code behind files. Once I changed the code behind class name and the inherits property in my register tag, the site compiles and runs fine.

    I though for sure I would have gotten a fat error message on this but the class declaration was auto-generated by MyGeneration dOOdads so that may be why.
    malicious, Apr 16, 2007
  5. Guest


    Jul 24, 2007
    Likes Received:
    just fixed mine took me about 2 weeks

    I have encountered this problem several times.
    I doubted vb compiler everytime.
    However, vb compiler has proved that it's my fault everytime.
    I always use my own generator to generate all the classes I need. They can't be wrong theoretically.
    Finally I resolved it and the problem is configuration.
    I found that one of my class library projects has been configuated as "Realease". However I reference the "Debug" in my Web Project.
    Then I changed the configurations and deleted all the files in bin directories of each project. After all, I rebuild the solution and got a build successfully message. I cryed....

    Maybe you have the same problem.
    SeanTsang, Jul 24, 2007
  6. Guest


    May 26, 2007
    Likes Received:
    ASP.Net Build Failed - Solution

    For whatever reason the IDE is failing to identify the source of the compilation errors. Happens infrequently, but often enough that I've found a quick to get past this.

    In the VStudio IDE, close all the open files except the "Start Page".
    Now rebuild and it will show you the page errors.

    David Rodecker
    “getting local business online
    drodecker, Sep 2, 2007
  7. Guest


    May 19, 2012
    Likes Received:
    Late Post. But can be helpful

    I have got similar problem. Build unsuccessful, but 0 errors. I browsed through many forums. Finally I got rid of the problem and hence posting it here. It may help somebody like me.

    Some specific errors were not reported by my Visual Studios. To get all assemblies in place, I installed ReportViewer.exe from the following location in OS Drive. Rebuilding the project again displayed specific errors which I could correct subsequently.

    ....\Program Files\Microsoft Visual Studio 8\SDK\v2.0\BootStrapper\Packages\ReportViewer

    Sravani, May 19, 2012
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.