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

Why do I keep getting a warning that a reference cannot be overwritten when I compile?

P: n/a
nfr
I keep getting the following warning in my compile:
Warning: The dependency 'WBWebServices, Version=1.0.1289.13943,
Culture=neutral' in project 'WBWin' cannot be copied to the run directory
because it would overwrite the reference 'WBWebServices,
Version=1.0.1289.15088, Culture=neutral'.

If I delete and readd the reference, it compiles fine but when I come leave
and return to Visual Studio.NET, the error pops up again when I recompile
the project.
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
nfr,

You are trying to compile a version of your assembly someplace where a
later version is already in place. Are you using automatic version
numbering on your assembly? In other words, are you explicitly controlling
the version number through the AssemblyVersion attribute?

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- ni**************@exisconsulting.com

"nfr" <nf*@nospam.com> wrote in message
news:uL**************@tk2msftngp13.phx.gbl...
I keep getting the following warning in my compile:
Warning: The dependency 'WBWebServices, Version=1.0.1289.13943,
Culture=neutral' in project 'WBWin' cannot be copied to the run directory
because it would overwrite the reference 'WBWebServices,
Version=1.0.1289.15088, Culture=neutral'.

If I delete and readd the reference, it compiles fine but when I come leave and return to Visual Studio.NET, the error pops up again when I recompile
the project.

Nov 13 '05 #2

P: n/a
nfr
"Nicholas Paldino [.NET/C# MVP]" <ni**************@exisconsulting.com> wrote
in message news:u8**************@tk2msftngp13.phx.gbl...
nfr,

You are trying to compile a version of your assembly someplace where a
later version is already in place. Are you using automatic version
numbering on your assembly? In other words, are you explicitly controlling the version number through the AssemblyVersion attribute?


I don't know. Everythihng is defaulted. Could that cause a problem?
Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.