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

[Obsolete("Doesn't work across multiple solutions", true)]

P: n/a
Is there any way to get the 'Obsolete' attribute to work across multiple
solutions?
I currently have 70 solutions, each with 3 projects in them, and would like
to change some base architecture, letting the app developers fix their own
code over time.
It works great in the first solution, but any solution consuming classes
defined in an earlier solution does not respond to the attribute at all.
Nov 15 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Womble,
It sounds like the other solutions are not getting a newer version of the
assembly where you put the Obsolete attribute.

Hope this helps
Jay

"Womble One" <wo****@wimbledon.common> wrote in message
news:u$**************@TK2MSFTNGP09.phx.gbl...
Is there any way to get the 'Obsolete' attribute to work across multiple
solutions?
I currently have 70 solutions, each with 3 projects in them, and would like to change some base architecture, letting the app developers fix their own
code over time.
It works great in the first solution, but any solution consuming classes
defined in an earlier solution does not respond to the attribute at all.

Nov 15 '05 #2

P: n/a
Yay! You are so right.
The one project I tested it on had our base architecture dll in its
directory.

"Jay B. Harlow [MVP - Outlook]" <Ja********@email.msn.com> wrote in message
news:OD****************@TK2MSFTNGP11.phx.gbl...
Womble,
It sounds like the other solutions are not getting a newer version of the
assembly where you put the Obsolete attribute.

Hope this helps
Jay

"Womble One" <wo****@wimbledon.common> wrote in message
news:u$**************@TK2MSFTNGP09.phx.gbl...
Is there any way to get the 'Obsolete' attribute to work across multiple
solutions?
I currently have 70 solutions, each with 3 projects in them, and would

like
to change some base architecture, letting the app developers fix their own code over time.
It works great in the first solution, but any solution consuming classes
defined in an earlier solution does not respond to the attribute at all.


Nov 15 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.