Problem with an MSDN article sample code

  • Thread starter Thread starter Bob
  • Start date Start date
B

Bob

I just downloaded the sample for the configure this article from
msdn.microsoft.com/msdnmag/code06.aspx. Executing the exe I unzipped it to
my folder c:\projectsVB2005\ and it created a subfolder Configuration. All
the stuff looks like its in there OK. When I try to see the form view of
EditElementDialog.vb in the MSDN.Configuration project I get a big red X in
the development window
and a message that tells me that basicaly it could not find
MSDN.Configuration.ElementEditor. But if you look at the Solution Explorer
you find that ElementEditor is part of the project in which I try to see the
form ElementEditDialog.vb


I tried unzipping the app to a subfolder of my
c:\downloads\ConfigurationSample folder, where it created the same
Configuration subfolder and when I open the solution there and try to look
at the ElementEditDialog.vb I can open it OK

I've had these types of red screens a number of times previously in 2003 I
had hoped 2005 would be better in this regard. Does anyone know why this is
occurring? What should I do to be able to see this file in design view?

Any help would be greatly appreciated.

Bob
 
Bob said:
I just downloaded the sample for the configure this article from
msdn.microsoft.com/msdnmag/code06.aspx. Executing the exe I unzipped it to
my folder c:\projectsVB2005\ and it created a subfolder Configuration. All
the stuff looks like its in there OK. When I try to see the form view of
EditElementDialog.vb in the MSDN.Configuration project I get a big red X in
the development window
and a message that tells me that basicaly it could not find
MSDN.Configuration.ElementEditor. But if you look at the Solution Explorer
you find that ElementEditor is part of the project in which I try to see the
form ElementEditDialog.vb


I tried unzipping the app to a subfolder of my
c:\downloads\ConfigurationSample folder, where it created the same
Configuration subfolder and when I open the solution there and try to look
at the ElementEditDialog.vb I can open it OK

I've had these types of red screens a number of times previously in 2003 I
had hoped 2005 would be better in this regard. Does anyone know why this is
occurring? What should I do to be able to see this file in design view?
Click to expand...

Build the solution.
 
Back
Top