 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Visual Studio.NET / Setup / March 2007XslDebugProxy.exe VS 2005 SP1 wrong version 2.0.50727.42?
When Using VS 2005 SP1, I try to Show XSLT Output and get: TypeLoadException ----------------- Method 'Execute' in type 'Microsoft.Xsl.XslPlugin' from assembly 'Microsoft.XslDebugProxy, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' does not have an implementation. Per another thread, it appears that my VS 2005 SP install created a mismatch between C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\Xml - Microsoft.XslDebugProxy.exe (v. 2.0.50727.42) - Microsoft.XmlEditor.dll (v. 2.0.50727.762) 1. Where can I get the correct Microsoft.XslDebugProxy.exe that goes with Microsoft.XmlEditor.dll (v. 2.0.50727.42)? 2. Or can I drop back and replace Microsoft.XmlEditor.dll (v. 2.0.50727.762) with Microsoft.XmlEditor.dll (v. 2.0.50727.42)? 3. Or, how do I show XSLT Output without the Debugger? The other thread showed Method Signature differences: Microsoft.XslDebugProxy.exe - (v. 2.0.50727.42) Execute(String, Stream) : Void Microsoft.XmlEditor.dll - (v. 2.0.50727.42) Execute(String, Stream) : Void - (v 2.0.50727.762) Execute (String, Stream, XmlOutputMethod&) : Void Any other ideas? Thanks, Doug Hello Doug, Regarding on the xslt debugger assembly mismatching issue, I've searched and found the following MSDN forum thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1056739&SiteID=1 is it also the one you ever referenced? According to the messages in it, some other MSFT engineers has pointed out that the problem is likely due to the XslDebugProxy.exe image is not correctly installed after you installed Visual Studio 2005 sp1. As for the following file/version you mentioned: ========== C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\Xml - Microsoft.XslDebugProxy.exe (v. 2.0.50727.42) - Microsoft.XmlEditor.dll (v. 2.0.50727.762) =========== are they the ones you found on your problem machine? The correct ones(after installed VS 2005 SP1) should be as below(from my local machine): Microsoft.XslDebugProxy.exe 2.0.50727.762 36846 bytes Microsoft.XmlEditor.dll 2.0.50727.762 741,376 bytes Have you any other machine that has vs 2005 and sp1 installed? If so, you can try copying a correct copy from that machine. If you feel necessary, I can send you two copies from my dev box. Else wise, you may consider peform reinstalling against the SP1 of visual studio 2005. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Hi Steven, Yes, that is the thread. No, I do not have another SP1 machine. Yes, please provide me with Microsoft.XslDebugProxy.exe 2.0.50727.762 36846 bytes. It also looks like I need Microsoft.XslDebugger.dll since I have 2.0.50727.42. Please also provide me with Microsoft.XslDebugger.dll (2.0.50727.762?). I don't have much confidence in a reinstall of SP 1 since I do not see any references to XslDebugger in the SP 1 Install Logs but plenty for XmlEditor. Thanks, Doug > Hello Doug, > [quoted text clipped - 59 lines] > This posting is provided "AS IS" with no warranties, and confers no > rights. Hi Doug, Sure, I can send you those two files(dll and exe). Would you please ping me through the email address in my signature(remove "online") so that I can get your address? Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights. Hi Steven, I found someone who had SP1 installed and the sent me: Microsoft.XslDebugger.dll Microsoft.XslDebugProxy.exe These corrected the problem. Thanks, Doug > Hi Doug, > [quoted text clipped - 11 lines] > This posting is provided "AS IS" with no warranties, and confers no > rights. Thanks for your followup Doug, Glad that you've made it working. Have a nice day. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead
Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.