471,318 Members | 1,988 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,318 software developers and data experts.

VS.NET Randomly Deletes Referenced Assemblies

Bob
I have an application that builds to the same directory that contains outside
references and it seems to be very buggy.

Random outside assemblies (referenced by projects in the solution) get
deleted once in a while for no reason at all. This usually seems to happen
during build or deploy (not sure which). One time it wiped out the entire
directory.

This latest time it happened I added a new project to the solution...
deleted it (no changes or added references to the project) and it deleted
several class libraries and removed references in other projects in the
solution to those class libraries.

Is there a workaround for this behavior? It is annoying to have to
rebuild/restore assemblies and fix my project over and over again after
VS.NET deletes stuff.
Jul 21 '05 #1
2 1010
CMM
I'm not sure when exactly this happens but I've noticed this at times when a
class' interface changes... thus theoretically breaking other components that
rely on it. This is especially true with "designed" classes (controls and
"components") as it prevents the IDE from serializing their properties when
saving forms that contain them.

Tweaking your Build Order should fix the problem.

"Bob" wrote:
I have an application that builds to the same directory that contains outside
references and it seems to be very buggy.

Random outside assemblies (referenced by projects in the solution) get
deleted once in a while for no reason at all. This usually seems to happen
during build or deploy (not sure which). One time it wiped out the entire
directory.

This latest time it happened I added a new project to the solution...
deleted it (no changes or added references to the project) and it deleted
several class libraries and removed references in other projects in the
solution to those class libraries.

Is there a workaround for this behavior? It is annoying to have to
rebuild/restore assemblies and fix my project over and over again after
VS.NET deletes stuff.

Jul 21 '05 #2
CMM
I'm not sure when exactly this happens but I've noticed this at times when a
class' interface changes... thus theoretically breaking other components that
rely on it. This is especially true with "designed" classes (controls and
"components") as it prevents the IDE from serializing their properties when
saving forms that contain them.

Tweaking your Build Order should fix the problem.

"Bob" wrote:
I have an application that builds to the same directory that contains outside
references and it seems to be very buggy.

Random outside assemblies (referenced by projects in the solution) get
deleted once in a while for no reason at all. This usually seems to happen
during build or deploy (not sure which). One time it wiped out the entire
directory.

This latest time it happened I added a new project to the solution...
deleted it (no changes or added references to the project) and it deleted
several class libraries and removed references in other projects in the
solution to those class libraries.

Is there a workaround for this behavior? It is annoying to have to
rebuild/restore assemblies and fix my project over and over again after
VS.NET deletes stuff.

Jul 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Steve Long | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.