locked
Staging Server Blues RRS feed

  • Question

  • Here's what I have:

    A web service application.

     

    I build development in the Visual Studio Environment. The code works.

    I copy the development dlls to staging and the code doesn't work.

     

    I build the code on our build server and deploy to staging the code doesn't work.

    I copy the build server dlls to development and the code works.

     

    What doesn't work is the primary DLL is searching for a project referenced DLL.

     

    Using PROCMON on staging I can see that it sees the project referenced dll (say B.dll) but somehow it doesn't use that dll when it creates the temporary ASP.NET files.

    If I place B.dll into c:\windows\system32\inetsrv The code works.

     

    I've spent 2 days on this problem and I'm out of places to look.

     

    Any thoughts?

     

    • Moved by Wesley Yao Monday, March 29, 2010 4:39 AM not MSBuild question, not sure where it should go (From:MSBuild)
    • Moved by Wesley Yao Monday, March 29, 2010 4:39 AM not MSBuild question, not sure where it should go (From:MSBuild)
    Friday, March 26, 2010 11:06 PM

Answers

All replies

  • I love it when you post and then have an "ah-ha" moment....

     

    I was compiling the project on the build server. I tried to compile the solution and I now have a more solid error:

                    CSC : error CS0006: Metadata file 'XXX.dll' could not be found

    The solution is structured as:

                   Proj A

    Solution---

                   Proj B

     

    Proj A has a project reference to Proj B in its .csproj file of ..\proj B

    The compiler builds proj B and then resolves the project reference in A to 'proj A\proj B'

    But I still don't know what I'm doing wrong.

     

    Friday, March 26, 2010 11:34 PM
  • What language?

    Thanks!


    Ed Price (a.k.a User Ed), SQL Server Experience Program Manager (Blog, Twitter, Wiki)

    Tuesday, June 19, 2012 4:24 PM