Old Class Library Objects Keep Showing Up!

  • Thread starter Thread starter Steven C
  • Start date Start date
S

Steven C

Hello:

I have a C# app that I'm trying to build. I have three projects in
the solution, the first of which stores the base object definitions
(base form, base textbox, base commandbutton, etc), the second project
holds an intermediate class level (subclassed from the base class
stuff), and a third class level that holds the end forms. I'm trying
to add a form called "AddCustomer" to the highest level project. The
problem is, I decided to change some controls around on the base form
(add some commandbuttons), but the old layout is showing up on the
derived classes. ie, The form objects from the old build of the base
project are still showing up on the end forms.

Why aren't the new changes in the base form reflected in the derived
form, after a solution rebuild? Why am I still seeing the old layout?

Thanks!

Steven
 
Steven, check the "bin" folder(s) of your projects and see if they have the
latest date/time of the topmost (or base) project. If they are not in
synch, right-click the solution & choose "Rebuild Solution". Sometimes I'm
not sure that Visual Studio always updates my referenced dlls, but
rebuilding the whole solution usually works.

You might try right-clicking the solution, then choose "Configuration
Manager". That's how Visual Studio knows which to build & not build for a
given configuration. Do you think your settings are correct? --Marty
 
Steven, check the "bin" folder(s) of your projects and see if they have the
latest date/time of the topmost (or base) project. If they are not in
synch, right-click the solution & choose "Rebuild Solution". Sometimes I'm
not sure that Visual Studio always updates my referenced dlls, but
rebuilding the whole solution usually works.

You might try right-clicking the solution, then choose "Configuration
Manager". That's how Visual Studio knows which to build & not build for a
given configuration. Do you think your settings are correct? --Marty
Thanks, Marty:

I have all three class level dll's in separate folders, and the
versioning is correct.

I went ahead and deleted the form to start again, and when I try to
right click on my topmost project and choose ADD | Add Inherited Form,
I get another wacky message. I enter the name frmAddCustomer, click
Open, and get the message:

Unable to load assembly D:\Path\App1\obj\debug\App1.dll
Ensure that the file is a valid .Net Framework assembly.

, where App1 is the baseclass app that contains the form class that
I'm trying to inherit. First of all, It's compiling the .dll to the
\bin folder, but this message indicates that it expects to find the
dll in the \obj folder. Something is wacked here. All of the
settings via the configuration manager for the solution are correct
(compile all three projects to debug)..

Ideas?

Thanks!

Steven
 

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

Back
Top