Glad I found this thread (sorry you ran into it also, however). I have run
into the same issue with System.dll and System.Drawing. dll, and reading this
thread I wasn't sure what exactly the ultimate resolution was. Can you share
how the warning was addressed, or was it?
"Steven Cheng [MSFT]" wrote:
into the same issue with System.dll and System.Drawing. dll, and reading this
thread I wasn't sure what exactly the ultimate resolution was. Can you share
how the warning was addressed, or was it?
"Steven Cheng [MSFT]" wrote:
Thanks for your followup Bob,
>
Yes, for projects that may contain large number of assemblies and complex
reference graph, it would be helpful to point out the error point. Sure,
you're welcome to submit this as feature request on the connect site.
Really appreciate your feedback.
>
Sincerely,
>
Steven Cheng
>
Microsoft MSDN Online Support Lead
>
>
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsof t.com.
>
=============== =============== =============== =====
Get notification to my posts through email? Please refer to
ications.
>
This posting is provided "AS IS" with no warranties, and confers no rights.
>
--------------------
>
>
It would have been helpful if the warning message clearly told me which
assemblies were involved in the version conflict. It turned out that the
assembly that brought in the conflicting version was indirectly referenced
by another assembly. In other words:
My app references A and B
A references B and C
C references an older version of A
I didn't realize (until I did a lot of digging) that assembly C was even
part of the issue. I was focused on looking at assemblies A and B, since
those are the only assemblies I directly use. Even the "diagnostic " build
log didn't point me at assembly C as being the culprit. I had to use
ildasm
references.
I guess it's time for a trip to MS Connect for an "enhancemen t" request...
Bob
>
>
>
Yes, for projects that may contain large number of assemblies and complex
reference graph, it would be helpful to point out the error point. Sure,
you're welcome to submit this as feature request on the connect site.
Really appreciate your feedback.
>
Sincerely,
>
Steven Cheng
>
Microsoft MSDN Online Support Lead
>
>
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@microsof t.com.
>
=============== =============== =============== =====
Get notification to my posts through email? Please refer to
ications.
>
This posting is provided "AS IS" with no warranties, and confers no rights.
>
--------------------
>
In-Reply-To: <tDpLfqtkIHA.42 00@TK2MSFTNGHUB 02.phx.gbl>
Subject: Re: Version conflicts between local and GAC
Date: Mon, 31 Mar 2008 08:49:38 -0700
Subject: Re: Version conflicts between local and GAC
Date: Mon, 31 Mar 2008 08:49:38 -0700
I'm glad that you've figured out the issue. Also glad that the Visual
Studio works in the correct way :)
Studio works in the correct way :)
It would have been helpful if the warning message clearly told me which
assemblies were involved in the version conflict. It turned out that the
assembly that brought in the conflicting version was indirectly referenced
by another assembly. In other words:
My app references A and B
A references B and C
C references an older version of A
I didn't realize (until I did a lot of digging) that assembly C was even
part of the issue. I was focused on looking at assemblies A and B, since
those are the only assemblies I directly use. Even the "diagnostic " build
log didn't point me at assembly C as being the culprit. I had to use
to go digging through the assembly manifests looking at external
I guess it's time for a trip to MS Connect for an "enhancemen t" request...
Bob
>