I'm looking for a way to link to errors CS#.  Such as CS1705 links to <a href="http://msdn.microsoft.com/en-us/library/416tef0c(VS.80).aspx">http://msdn.microsoft.com/en-us/library/416tef0c(VS.80).aspx</a>.  If there is a way to do this an also vary it on the framework used to that would be great.© 2009 Microsoft Corporation. All rights reserved.Thu, 25 Jun 2009 14:18:50 Z7dd845ec-e9fe-4fed-a0d4-ea70d35e7b03http://social.msdn.microsoft.com/Forums/en-US/netfxtoolsdev/thread/7dd845ec-e9fe-4fed-a0d4-ea70d35e7b03#7dd845ec-e9fe-4fed-a0d4-ea70d35e7b03http://social.msdn.microsoft.com/Forums/en-US/netfxtoolsdev/thread/7dd845ec-e9fe-4fed-a0d4-ea70d35e7b03#7dd845ec-e9fe-4fed-a0d4-ea70d35e7b03Ryan Mrachekhttp://social.msdn.microsoft.com/Profile/en-US/?user=Ryan%20MrachekI'm looking for a way to link to errors CS#.  Such as CS1705 links to <a href="http://msdn.microsoft.com/en-us/library/416tef0c(VS.80).aspx">http://msdn.microsoft.com/en-us/library/416tef0c(VS.80).aspx</a>.  If there is a way to do this an also vary it on the framework used to that would be great.Fri, 19 Jun 2009 13:44:22 Z2009-06-19T13:44:22Zhttp://social.msdn.microsoft.com/Forums/en-US/netfxtoolsdev/thread/7dd845ec-e9fe-4fed-a0d4-ea70d35e7b03#0671fee5-c4ae-4502-8947-5a0b36084b90http://social.msdn.microsoft.com/Forums/en-US/netfxtoolsdev/thread/7dd845ec-e9fe-4fed-a0d4-ea70d35e7b03#0671fee5-c4ae-4502-8947-5a0b36084b90Karel Zikmundhttp://social.msdn.microsoft.com/Profile/en-US/?user=Karel%20Zikmund<p>If you need links to MSDN documentation, then note that no one guarantees that the MSDN links are permanent and will work in the future. I have seen some of them to change from time to time in the past couple of years.<br/>That's IMO the main reason why there is not built-in mapping from error number to MSDN link.<br/><br/>You can simply create your own static list of errors and their links by parsing MSDN docs (e.g. parse the list from this HTML page: <a href="http://msdn.microsoft.com/en-us/library/ms228296.aspx">http://msdn.microsoft.com/en-us/library/ms228296.aspx</a>). That's IMO the best thing you can do.<br/><br/>-Karel</p>Mon, 22 Jun 2009 16:29:50 Z2009-06-22T16:29:50Z