Compilation failure with inherited user controls

  • Thread starter Thread starter Mike Ruane-Torr
  • Start date Start date
M

Mike Ruane-Torr

I am suddenly getting this message from VS.Net very frequently. It seemed
to being when I introduced inherited user controls into my solution. I am
building a project in C# that uses a set of class libraries, and user
controls inherit from other controls in other class libraries.

I have noticed a couple of things:

1. Often a user control that is placed in a tab control within another
user control will mysteriously disappear from the designer. It is present
in the properties tool window and shows a location of 0,0 - but I can't
see it. It doesn't appear in the runtime instance either. The only
solution so far is to delete the control and add it again.

2. I often get the error message, "A failure occurred while attempting to
start the compilation.", when I have modified one of the inherited user
controls. The only fix seems to be to restart VS.

This looks like a bug to me. Has anyone else experienced it?
 
I am suddenly getting this message from VS.Net very frequently. It
seemed to being when I introduced inherited user controls into my
solution. I am building a project in C# that uses a set of class
libraries, and user controls inherit from other controls in other class
libraries.

I have noticed a couple of things:

1. Often a user control that is placed in a tab control within another
user control will mysteriously disappear from the designer. It is
present in the properties tool window and shows a location of 0,0 - but
I can't see it. It doesn't appear in the runtime instance either. The
only solution so far is to delete the control and add it again.

2. I often get the error message, "A failure occurred while attempting
to start the compilation.", when I have modified one of the inherited
user controls. The only fix seems to be to restart VS.

This looks like a bug to me. Has anyone else experienced it?
Click to expand...

An update:

A quick look at before and after versions using FileSync (excellent
product, does anyone know if it's still supported? The company that made
it don't seem to exist now) has revealed some more facts.

It seems that the control is still being created in the component init
code, but is not being correctly attached to the tabpage of the tab
control in which it is supposed to reside.

I now also know what causes it to detach - but not why. If I press F5 to
run a test harness that I've written, which uses the compound control I'm
talking about, I can actually see the control disappear from the tab page
in the designer as the application starts up! It looks as if running this
project is causing the control to disappear. This is not because I have
the designer open. I tried it without it open, and the same thing happens
next time I open it.

Very strange bug. Causing me quite a lot of grief, because I'm trying to
design my controls and they keep going AWOL :\
 
I know I'm talking to myself here, sorry about that! Anyway, it appears
that this error only occurs when I "Rebuild" a project. If I restrict
myself to using "Build", it doesn't seem to happen.
 
I have the same problem Mike
But i think you are a bit lucky than me beacuse either i rebuild nor build the project it always gives the same error "A failure occurred while attempting to start the compilation."
And addition to this error i also take an error The located assembly manifest destination file is not same ......

I could not write code about 1 day because of these errors. Restarting VS.NET also did not solve my problem.

Is there any one who soleve this problem or is this a bug of VS.NET if so is there any fixes for it to download

Thanks ...
 
Back
Top