Just went through the MSDN Product Feedback Center. There's been over 10,000 bugs and
suggestions. Is that a sufficient number of issues left unresolved that may or may not
have been or will be blogged somewhere? The whole point is discovering information with
regard to product releases is more a matter of luck and timing than it is a matter of
coordinated management.
For example, I've spent several days trying to search through that resource and the web
trying to determine why controls disappear from the viewstate when using MasterPages.
Still no solution.
Knowledge Management comes to mind as a means to at least try to make it easier, more
efficient and less expensive to remain informed about these issues. One product solution
I've found very impressive is from Endeca who calls their technology 'Guided
Navigation.'
Do you remember infoSeek? They sent me a T-Shirt for suggesing they develop search
results which included an interface to create a second level of search applied against
the results returned from each preceding search. The output of the response I proposed
should use a drill-down navigation that was built from each returned result set. Several
years later Endeca made it happen. IMO Guided Navigation would work very well for
coordinating and managing the information for a product release such as ASP.NET 2.0.
Check out Endeca's Product Flash Demos [2]
<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL
http://metromilwaukee.com/
URL
http://clintongallagher.metromilwaukee.com/
[1]
http://endeca.com/
[2]
http://endeca.com/demos/index.html
Juan T. Llibre said:
Clinton,
re:
The complete list of Beta 2 --> RTM API changes is at :
http://download.microsoft.com/download/E/C/E/ECE1E64C-824D-4905-AE1C-FD13DDC78BC8/Beta2RTMAPI.msi
What is missing from that document ?
Are you aware of any changes which are not included there ?
Juan T. Llibre
ASP.NET MVP
ASP.NET FAQ :
http://asp.net.do/faq/
===========================