By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,446 Members | 3,031 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,446 IT Pros & Developers. It's quick & easy.

REPOST: More Reference problems & custom controls disappearing

P: n/a
Hi all,

I'm reposting this message as I'm experiencing this problem more and
more frequently :

I really hope someone out there can help me as I've been tearing my
hair out on this one for a good while and I'm getting really
frustrated now!

My problem is this - my custom controls periodically disappear from my
project when I build it. First of I get the message about a missing
dependency, then if I rebuild after that - the control just physically
disappears from the form, and I get an object not found error when I
run, (although sometimes when I rebuild the control can reappear!)

My background - I'm working in a small team of developers, we are
using vb.net in visual studio with visual source safe.

As I've said I've been battling with this for a while and have done
some reading on this - I know that it is to do with references.
Therefore I am trying to do what all the Microsoft articles I've read
recommend with regard to references: - setting copy to local = true,
using project references not file references, and setting the build
order but to no avail. (Incidentally I still get this problem when
using file references).

Some more information - the custom controls are using a data access
object, and this data access object is also being used by another
object which the main form also uses. It is the reference to this data
access object that is the one that that I get the message about the
missing dependency.

I received some advice last time I posted about manually
re-inserting the code for the custom control back into the designer
generated region when this happens to get over the problem, but I
found that VSS just wouldn't accept it and disappeared the code that I
just added back in every time that I tried to rebuild.

What I'd like to know is why am I getting the file or assembly not
found error in the first place if I'm using project references, copy
local = true etc? I believe this is the reason why the Windows Forms
designer is removing the control.

Also I'm a bit unclear about how adding the custom control on to the
toolbox fits into all this file vs. project references debate? Am I
actually referencing a specific version of the custom control's dll by
adding it on to the toolbox in the first place?

When I drag it from the toolbox onto my form does that mean I am then
referencing that specific version (by a file reference) even though I
am including the custom control as a project reference in my solution?
Could that be why I'm getting that error message?

Please help - I think I'm spending more time adding my existing
controls back to my form than writing anything new at the moment
Thank you
Suzanne
Nov 20 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Forgive me if this may seem a bit simplistic but ?

The problem with this sort of question is that unless this is a well known
phenomenon, it is highly unlikely that you will get a resolution with this
level of diagnostic description.

I'm not suggesting that you are not looking at the problem in a logical
fashion ( I'm sure you are ), but what sort of science have you put behind
solving this.

For example, have you been able to repeat the disapearance of the controls
with a known set of steps ? You refer to the "Periodic" disapearance of the
controls, is the period defined ( IE Every time, one in three, random
periods ).

Q.) Is there any other event happening on this machine which may be causing
a problem, for example, do you have a virus scanner operational?

Q.) Any other programs running which may be altering either your files or
file attributes?

Q.) Is the program you are running altering the file structure, attributes
or files ?

Q.) Does your machine have a virus.?

Q.) Have you tried this without source safe ?

The disapearance of these controls is VERY unlikely to be a random event.
( Notwithstanding external influences already mentioned ).
Regards OHM

----------------------------


Suzanne wrote:
Hi all,

I'm reposting this message as I'm experiencing this problem more and
more frequently :

I really hope someone out there can help me as I've been tearing my
hair out on this one for a good while and I'm getting really
frustrated now!

My problem is this - my custom controls periodically disappear from my
project when I build it. First of I get the message about a missing
dependency, then if I rebuild after that - the control just physically
disappears from the form, and I get an object not found error when I
run, (although sometimes when I rebuild the control can reappear!)

My background - I'm working in a small team of developers, we are
using vb.net in visual studio with visual source safe.

As I've said I've been battling with this for a while and have done
some reading on this - I know that it is to do with references.
Therefore I am trying to do what all the Microsoft articles I've read
recommend with regard to references: - setting copy to local = true,
using project references not file references, and setting the build
order but to no avail. (Incidentally I still get this problem when
using file references).

Some more information - the custom controls are using a data access
object, and this data access object is also being used by another
object which the main form also uses. It is the reference to this data
access object that is the one that that I get the message about the
missing dependency.

I received some advice last time I posted about manually
re-inserting the code for the custom control back into the designer
generated region when this happens to get over the problem, but I
found that VSS just wouldn't accept it and disappeared the code that I
just added back in every time that I tried to rebuild.

What I'd like to know is why am I getting the file or assembly not
found error in the first place if I'm using project references, copy
local = true etc? I believe this is the reason why the Windows Forms
designer is removing the control.

Also I'm a bit unclear about how adding the custom control on to the
toolbox fits into all this file vs. project references debate? Am I
actually referencing a specific version of the custom control's dll by
adding it on to the toolbox in the first place?

When I drag it from the toolbox onto my form does that mean I am then
referencing that specific version (by a file reference) even though I
am including the custom control as a project reference in my solution?
Could that be why I'm getting that error message?

Please help - I think I'm spending more time adding my existing
controls back to my form than writing anything new at the moment
Thank you
Suzanne

Nov 20 '05 #2

P: n/a
Forgive me if this may seem a bit simplistic but ?

The problem with this sort of question is that unless this is a well known
phenomenon, it is highly unlikely that you will get a resolution with this
level of diagnostic description.

I'm not suggesting that you are not looking at the problem in a logical
fashion ( I'm sure you are ), but what sort of science have you put behind
solving this.

For example, have you been able to repeat the disapearance of the controls
with a known set of steps ? You refer to the "Periodic" disapearance of the
controls, is the period defined ( IE Every time, one in three, random
periods ).

Q.) Is there any other event happening on this machine which may be causing
a problem, for example, do you have a virus scanner operational?

Q.) Any other programs running which may be altering either your files or
file attributes?

Q.) Is the program you are running altering the file structure, attributes
or files ?

Q.) Does your machine have a virus.?

Q.) Have you tried this without source safe ?

The disapearance of these controls is VERY unlikely to be a random event.
( Notwithstanding external influences already mentioned ).
Regards OHM

----------------------------


Suzanne wrote:
Hi all,

I'm reposting this message as I'm experiencing this problem more and
more frequently :

I really hope someone out there can help me as I've been tearing my
hair out on this one for a good while and I'm getting really
frustrated now!

My problem is this - my custom controls periodically disappear from my
project when I build it. First of I get the message about a missing
dependency, then if I rebuild after that - the control just physically
disappears from the form, and I get an object not found error when I
run, (although sometimes when I rebuild the control can reappear!)

My background - I'm working in a small team of developers, we are
using vb.net in visual studio with visual source safe.

As I've said I've been battling with this for a while and have done
some reading on this - I know that it is to do with references.
Therefore I am trying to do what all the Microsoft articles I've read
recommend with regard to references: - setting copy to local = true,
using project references not file references, and setting the build
order but to no avail. (Incidentally I still get this problem when
using file references).

Some more information - the custom controls are using a data access
object, and this data access object is also being used by another
object which the main form also uses. It is the reference to this data
access object that is the one that that I get the message about the
missing dependency.

I received some advice last time I posted about manually
re-inserting the code for the custom control back into the designer
generated region when this happens to get over the problem, but I
found that VSS just wouldn't accept it and disappeared the code that I
just added back in every time that I tried to rebuild.

What I'd like to know is why am I getting the file or assembly not
found error in the first place if I'm using project references, copy
local = true etc? I believe this is the reason why the Windows Forms
designer is removing the control.

Also I'm a bit unclear about how adding the custom control on to the
toolbox fits into all this file vs. project references debate? Am I
actually referencing a specific version of the custom control's dll by
adding it on to the toolbox in the first place?

When I drag it from the toolbox onto my form does that mean I am then
referencing that specific version (by a file reference) even though I
am including the custom control as a project reference in my solution?
Could that be why I'm getting that error message?

Please help - I think I'm spending more time adding my existing
controls back to my form than writing anything new at the moment
Thank you
Suzanne
Suzanne wrote: Hi all,

I'm reposting this message as I'm experiencing this problem more and
more frequently :

I really hope someone out there can help me as I've been tearing my
hair out on this one for a good while and I'm getting really
frustrated now!

My problem is this - my custom controls periodically disappear from my
project when I build it. First of I get the message about a missing
dependency, then if I rebuild after that - the control just physically
disappears from the form, and I get an object not found error when I
run, (although sometimes when I rebuild the control can reappear!)

My background - I'm working in a small team of developers, we are
using vb.net in visual studio with visual source safe.

As I've said I've been battling with this for a while and have done
some reading on this - I know that it is to do with references.
Therefore I am trying to do what all the Microsoft articles I've read
recommend with regard to references: - setting copy to local = true,
using project references not file references, and setting the build
order but to no avail. (Incidentally I still get this problem when
using file references).

Some more information - the custom controls are using a data access
object, and this data access object is also being used by another
object which the main form also uses. It is the reference to this data
access object that is the one that that I get the message about the
missing dependency.

I received some advice last time I posted about manually
re-inserting the code for the custom control back into the designer
generated region when this happens to get over the problem, but I
found that VSS just wouldn't accept it and disappeared the code that I
just added back in every time that I tried to rebuild.

What I'd like to know is why am I getting the file or assembly not
found error in the first place if I'm using project references, copy
local = true etc? I believe this is the reason why the Windows Forms
designer is removing the control.

Also I'm a bit unclear about how adding the custom control on to the
toolbox fits into all this file vs. project references debate? Am I
actually referencing a specific version of the custom control's dll by
adding it on to the toolbox in the first place?

When I drag it from the toolbox onto my form does that mean I am then
referencing that specific version (by a file reference) even though I
am including the custom control as a project reference in my solution?
Could that be why I'm getting that error message?

Please help - I think I'm spending more time adding my existing
controls back to my form than writing anything new at the moment
Thank you
Suzanne

Nov 20 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.