• Home
  • About
  • Resume

Solution for ASPNETCOMPILER ASPRUNTIME error: Object reference not set to an instance of an object

By , 08/17/2009 3:12 PM

If you’re using Web Deployment project and during build getting errror “Object reference not set to an instance of an object” error from ASPNETCOMPILER, check the BIN folder of the project you’re compiling. Chances are, there’re some *.compiled files there. Remove them and your deployment will go thru.

13 Responses to “Solution for ASPNETCOMPILER ASPRUNTIME error: Object reference not set to an instance of an object”

  1. Tungster says:

    thank you for a great post. I was already wasted so many hours and couldn’t resolve this issue until now. Thank you again…

  2. Ravi says:

    Thanks allot buddyy…its like a life jacket for me..

    again thank . Great solution

  3. aguirre says:

    tnx dude! Im just wondering! what is the connection *.compiled files to the error..

    anyway! Thanks again and Great solution!

  4. Rahul says:

    this a fantastic solution as i was scrubbing my head for past hours to overcome this issue.

  5. AR says:

    Thank you so much πŸ˜€

  6. Ahmad Ali says:

    Thank you. You rescued me before my deadline πŸ™‚

  7. Jim says:

    Thanks for the post. Simple solution for such an abstract error message.

  8. Dima says:

    Man you’re a genius. You saved me a lot of time. Good job

  9. Leslie says:

    Thank you very much, you saved us a lot of time. By the way what is the reason for this fail?

  10. Nice Work says:

    Worked for me. Great post!

  11. Mohit Juneja says:

    I don’t have *.compiled files over there but still i am getting this issue … m stuck

  12. Jhonattan says:

    When select publish, in the settings section -> File Publish Options check “Exclude files from the App_Data folder”. Work for me.

  13. Ann says:

    well i am using FTP deploy and there are no .complied in my bin folder. any other option ?

Leave a Reply

Panorama Theme by Themocracy