ASPNETCOMPILER : error ASPRUNTIME: 未将对象引用设置到对象的实例

vs2010+devexpress插件开发是一个不错的开发模式，效率较高。在编译个一个项目的时候，报出了如下错误：ASPNETCOMPILER : error ASPRUNTIME: 未将对象引用设置到对象的实例。后经查找，是汉化资源dll冲突，去掉bin目录中的App_GlobalResources.resources.dll文件，问题解决。

参考文献地址：

http://social.msdn.microsoft.com/Forums/zh-CN/fb2e6148-49be-4f1c-8d3e-f74c43680045/aspnetcompiler-error-aspruntime?forum=msbuild

ASPNETCOMPILER : error ASPRUNTIME: 

Visual Studio Development

 > 

MSBuild

• 问题

• 

  

  0

  登录进行投票

  We have a build script that uses the <MSBuild> task to call a solution file like so.

  <MSBuild Projects="MySolution.sln" Properties="Configuration=Release;OutDir=c:\MyOuput"/>

  For some reason we seem to get the error "ASPNETCOMPILER : error ASPRUNTIME: Object reference not set to an instance of an object" when calling our solution file.  The error does not seem to be very descriptive so we're really not sure what to look at.

  The MSBuild task splits out the following before spitting out the error:

  "C:\WINNT\Microsoft.NET\Framework\v2.0.50727\aspnet_compiler.exe -v /localhost -p ..\webservices\ -u -f c:\MyOutput\_PublishedWebsites\webservices\"

  We're thinking the error has to do with something to do with the parameters supplied or not supplied to the asp.net compiler.  The other two projects in the solution file are class libraries and compile just fine.  They are setup as project references to the website.

  Anyone have insight on where we should start looking?

  Mac

  
   

   

   

   

  2006年3月2日 17:33

  回复

  |

  引用

  mcdonaldn

  150 分数

答案

• 

  

  0

  登录进行投票

  As often happens, the poster of issues finds out the solution soon after hitting "post."

  For those of you who run into an obscure error like this, here is what caused our error.

  This project gets some additional built APIs (e.g. OtherGroup.dll) from another development group at build time. In the past with .NET 1.x this has worked slick as we just take their output from our company API landing string and stick them in the .\bin folder. With .NET 2.0 we noticed the other development group has begun to ship App_Code.dll and App_global.asax.dll (and their *.compile files) with their APIs. This caused our build to fail so we removed the two assemblies (dll), but forgot about the two ".compile" files. After removing the two ".compile" files, we have success.

  Does anyone know what the ".compile" files are used for and if they are needed for deployment?

  2006年3月2日 19:32

  回复

  |

  引用

  mcdonaldn

  150 分数

全部回复

• 

  

  0

  登录进行投票

  As often happens, the poster of issues finds out the solution soon after hitting "post."

  For those of you who run into an obscure error like this, here is what caused our error.

  This project gets some additional built APIs (e.g. OtherGroup.dll) from another development group at build time. In the past with .NET 1.x this has worked slick as we just take their output from our company API landing string and stick them in the .\bin folder. With .NET 2.0 we noticed the other development group has begun to ship App_Code.dll and App_global.asax.dll (and their *.compile files) with their APIs. This caused our build to fail so we removed the two assemblies (dll), but forgot about the two ".compile" files. After removing the two ".compile" files, we have success.

  Does anyone know what the ".compile" files are used for and if they are needed for deployment?

  2006年3月2日 19:32

  回复

  |

  引用

  mcdonaldn

  150 分数
• 

  

  0

  登录进行投票

  I knw this is an old post but i just had a similar problem but this time it was caused by an app_offline.htm file sitting in the source folder!!
  
  Very odd!
  
  Pete