multi project solution > have to BUILD whole solution to see changes in a single project (DLL)

[sonic_soul]

I have this 58 project solution I maintained for 6 months now after
taking over.

Usually the advantage of having it broken down in many projects was,
that i could just edit a single .cs file, than compile the project it
is in. this would generate the appropriate DLL and i could just
"reload" the current page of the application I was on, and see the
changes take effect.

Now after installing the app on a new machine, I noticed that after i
make changes to a file in project, and build that project, and step
through it with debugger, it does not see the changes and attempts to
step on the lines as they were before my change. Until i run a BUILD
on whole solution.

i am suspecting that this might have something to do with my project
refrences.

Not exactly sure yet.

TIA.

 

[Michael Giagnocavo [MVP]]

Well, just rebuilding one DLL doesn't mean the rest are linked up to it.
How long does a full build take? If the other projects don't have changes,
then they should take about half a sec.

Another possible workaround would be to have a post-build event, and copy
the resulting DLL to wherever it needs to be (for instance, to you main
executable's bin dir).

-mike
MVP

 

[SoniC SouL]

hey.. thanx!
i actually realized it was an issue with DLL's not being copied after
posting this question, so i added a refrence that would ensure the dll
copied into the project that is running the test and it started to work
properly.

- raf