reference madness

  • Thread starter nickfranceschina
  • Start date
N

nickfranceschina

I'm not sure what I'm doing wrong, so I'll explain best I can. nothing
too exciting, I have a VS2005 solution with a website project and a
class library project (website references library with "project
reference") All was well for the past few weeks... class library
builds, then website builds, and everyone is happy. But lately (within
the last week?) I've having this problem where the website project is
telling me that it doesn't see new properties/methods of the class
library... as if it's still looking at an old one. I have ReSharper
installed, and ReSharper shows no errors... it is compiling the library
in memory and showing me the correct props/methods in intellisense...
but if I switch to VS.NET intellisense it says the props/methods don't
exist. When I run a compile (or launch the page) it says it cant find
some props/methods. The class library .dll in the website /bin folder
is the same version # as the one in the class library /bin/debug
folder... so it APPEARS to be pulling the correct version over. I
can't for the life of me figure out why this is happening.

Anyone have any thoughts? can I give anyone more information to help
clarify?
 
N

nickfranceschina

ummm.. yeah... so I manually deleted the /bin AND /obj directories from
the class library, and it started working. Previously I had used the
"clean" function in the IDE, which didn't work... and I manually
deleted the /bin directory (not the /obj) and that didn't work either.
had to manually get rid of /obj

-whatever
 
L

Laurent Bugnion

Hi,

ummm.. yeah... so I manually deleted the /bin AND /obj directories from
the class library, and it started working. Previously I had used the
"clean" function in the IDE, which didn't work... and I manually
deleted the /bin directory (not the /obj) and that didn't work either.
had to manually get rid of /obj

-whatever

That hints towards a cache problem. in ASP.NET, libraries are cached in
different temp folders before they are executed. Often it happens that
the cache is not refreshed correctly when you modify the code. If that
makes things better, it was even worse in ASP.NET 1.1...

And unfortunately, short of deleting the folders manually, I don't know
any cure...

HTH,
Laurent
 
N

nickfranceschina

Thanks Laurent. I rarely had any problems with this in 1.1... but
with this new Website model, it appears to happen more often.

anyways, at least I know how to clear it all out now!
 

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. After that, you can post your question and our members will help you out.

Ask a Question

Top