inconsistent compile results?

[Tim]

hi, I'm wondering if anyone else has seen this. I've just built and
published a web site on my developer machine, then copied the
precompiled web to a staging / test machine. The code runs fine on my
machine. On the staging machine I get a compile error:

Compiler Error Message: CS0012: The type 'ASP....is defined in an
assembly that is not referenced. You must add a reference to assembly
'App_Web_box

How can this be? I've already compiled everything on my machine.

Both are running dotnet 2.0 beta 2. I have visual studio running
locally whereas the staging / test machine has only the framework. But
that shouldn't matter, should it? We're hoping to go live with a
similar architecture: staging, test, and live machines have only the
framework.

But this won't be feasible if a successful compile on a developer
machine does not guarantee an identical result on the staging, test, or
live machines.

cheers,

Tim Hanson

[Marina]

Re: inconsistent compile results?

Do you have the DLL on the staging machine?

That kind of error usually means the page is set to inherit from a class
that .net expects to find in the DLL compiled for the project, but it cann't
find any DLL's with the right class.

"Tim" <t.hanson@faz.d e> wrote in message
news:1117202001 .438137.181130@ g14g2000cwa.goo glegroups.com.. .[color=blue]
> hi, I'm wondering if anyone else has seen this. I've just built and
> published a web site on my developer machine, then copied the
> precompiled web to a staging / test machine. The code runs fine on my
> machine. On the staging machine I get a compile error:
>
> Compiler Error Message: CS0012: The type 'ASP....is defined in an
> assembly that is not referenced. You must add a reference to assembly
> 'App_Web_box
>
> How can this be? I've already compiled everything on my machine.
>
> Both are running dotnet 2.0 beta 2. I have visual studio running
> locally whereas the staging / test machine has only the framework. But
> that shouldn't matter, should it? We're hoping to go live with a
> similar architecture: staging, test, and live machines have only the
> framework.
>
> But this won't be feasible if a successful compile on a developer
> machine does not guarantee an identical result on the staging, test, or
> live machines.
>
> cheers,
>
> Tim Hanson
>[/color]

[Tim]

Re: inconsistent compile results?

thanks, yes. i copied the whole precompiled web, so, as I understand
it, i have everything of relevance.

discovered an interesting additional clue that solves the problem for
me: if when "publishing " the web site I unclick the box "allow this
precompiled site to be updateable" (disallowing this) one side-effect
is that the compile process was more demanding. i found several of
these missing assembly problems that had been cropping up on the
staging machine. now i had to fix them on my development machine to get
a clean compile/build/publish. i guess I'm still confused why a local
compile is somehow "friendly" in the sense of not complaining about
problems that will crop up later. i assume this is a bug that MS would
be interested in fixing.

thanks again for the question and suggestion.

cheers,

Tim