Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Visual Basic
  4. Windows SDK error message

Windows SDK error message

Scheduled Pinned Locked Moved Visual Basic
helpregexquestion
10 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    DaveC426913
    wrote on last edited by
    #1

    I am trying to get some basic Windows Services up and running, using barebones code from MSDN tutorials. I've downloaded the latest SDK, and used code straight from their site, but I'm getting an error message. System.IO.FileLoadException: The located assembly's manifest definition with name 'interop_msxml' does not match the assembly reference. File name: "interop_msxml" Does this mean I've got either an old dll or old code? Or am I oversimplifying? ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)

    P 1 Reply Last reply
    0
    • D DaveC426913

      I am trying to get some basic Windows Services up and running, using barebones code from MSDN tutorials. I've downloaded the latest SDK, and used code straight from their site, but I'm getting an error message. System.IO.FileLoadException: The located assembly's manifest definition with name 'interop_msxml' does not match the assembly reference. File name: "interop_msxml" Does this mean I've got either an old dll or old code? Or am I oversimplifying? ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)

      P Offline
      P Offline
      progload
      wrote on last edited by
      #2

      Delete the contents in your Bin folder, Recompile your application and turn on your JIT Debugger if it's not on. Where did you get the original source, I'd like to download it. Thanks, progload

      D 2 Replies Last reply
      0
      • P progload

        Delete the contents in your Bin folder, Recompile your application and turn on your JIT Debugger if it's not on. Where did you get the original source, I'd like to download it. Thanks, progload

        D Offline
        D Offline
        DaveC426913
        wrote on last edited by
        #3

        You mean the SDK itself? Here: http://www.microsoft.com/downloads/details.aspx?familyid=EBA0128F-A770-45F1-86F3-7AB010B398A3&displaylang=en Or you mean the code snippet? Here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmsrvsdk/htm/configuringbrdcstpubpt.asp ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)

        P 1 Reply Last reply
        0
        • P progload

          Delete the contents in your Bin folder, Recompile your application and turn on your JIT Debugger if it's not on. Where did you get the original source, I'd like to download it. Thanks, progload

          D Offline
          D Offline
          DaveC426913
          wrote on last edited by
          #4

          "Delete the contents in your Bin folder, " Didn't have any effect. "Recompile your application and turn on your JIT Debugger if it's not on." OK, I did that, but all that does is put the error message in a prettier box to read. Now the error message is this: "An unhandled exception of type 'System.IO.FileLoadException' occurred in system.windows.forms.dll Additional information: The located assembly's manifest definition with name 'interop_msxml' does not match the assembly reference." I have tried removing and then adding the two offending dlls (interop_msxml.dll, microsoft.windowsmediaservices.dll) into the reference, but I can't - they don't show up in the component list at all, even though I've managed to add them. (I can tell I added them because when I try to do it again, it tells me it couldn't, since there is already a reference to this component in the project.) Oddly, the place where it's blowing up isn't near the start, it's at this line: Playlist = BCPubPoint.SharedPlaylist even though there's lost of references prior to this: ... Dim BCPubPoint As IWMSBroadcastPublishingPoint Dim Playlist As IWMSPlaylist ... If BCPubPoint.BroadcastStatus = WMS_BROADCAST_PUBLISHING_POINT_STATUS.WMS_BROADCAST_PUBLISHING_POINT_STOPPED Then BCPubPoint.Start() Playlist = BCPubPoint.SharedPlaylist If I comment that one line, it doesn't blow up. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)

          P 2 Replies Last reply
          0
          • D DaveC426913

            You mean the SDK itself? Here: http://www.microsoft.com/downloads/details.aspx?familyid=EBA0128F-A770-45F1-86F3-7AB010B398A3&displaylang=en Or you mean the code snippet? Here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmsrvsdk/htm/configuringbrdcstpubpt.asp ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)

            P Offline
            P Offline
            progload
            wrote on last edited by
            #5

            Dave, thanks for the links.. progoad

            1 Reply Last reply
            0
            • D DaveC426913

              "Delete the contents in your Bin folder, " Didn't have any effect. "Recompile your application and turn on your JIT Debugger if it's not on." OK, I did that, but all that does is put the error message in a prettier box to read. Now the error message is this: "An unhandled exception of type 'System.IO.FileLoadException' occurred in system.windows.forms.dll Additional information: The located assembly's manifest definition with name 'interop_msxml' does not match the assembly reference." I have tried removing and then adding the two offending dlls (interop_msxml.dll, microsoft.windowsmediaservices.dll) into the reference, but I can't - they don't show up in the component list at all, even though I've managed to add them. (I can tell I added them because when I try to do it again, it tells me it couldn't, since there is already a reference to this component in the project.) Oddly, the place where it's blowing up isn't near the start, it's at this line: Playlist = BCPubPoint.SharedPlaylist even though there's lost of references prior to this: ... Dim BCPubPoint As IWMSBroadcastPublishingPoint Dim Playlist As IWMSPlaylist ... If BCPubPoint.BroadcastStatus = WMS_BROADCAST_PUBLISHING_POINT_STATUS.WMS_BROADCAST_PUBLISHING_POINT_STOPPED Then BCPubPoint.Start() Playlist = BCPubPoint.SharedPlaylist If I comment that one line, it doesn't blow up. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)

              P Offline
              P Offline
              progload
              wrote on last edited by
              #6

              Dave, Sorry, I don't have an answer yet.. Looks like it has something to do with SP1 for server 2003.. Mine is also that way (???), I haven't used the PIA since I put in SP1, I checked the GAC and It has put two different assemblies and manifests in the GAC on mine when I installed SP1, and it seems to have broken a test program I wrote last year. Give me a little time and I'll see if I can track down the problem. If anyone else knows what's going on here, please feel free to comment on this. progload

              1 Reply Last reply
              0
              • D DaveC426913

                "Delete the contents in your Bin folder, " Didn't have any effect. "Recompile your application and turn on your JIT Debugger if it's not on." OK, I did that, but all that does is put the error message in a prettier box to read. Now the error message is this: "An unhandled exception of type 'System.IO.FileLoadException' occurred in system.windows.forms.dll Additional information: The located assembly's manifest definition with name 'interop_msxml' does not match the assembly reference." I have tried removing and then adding the two offending dlls (interop_msxml.dll, microsoft.windowsmediaservices.dll) into the reference, but I can't - they don't show up in the component list at all, even though I've managed to add them. (I can tell I added them because when I try to do it again, it tells me it couldn't, since there is already a reference to this component in the project.) Oddly, the place where it's blowing up isn't near the start, it's at this line: Playlist = BCPubPoint.SharedPlaylist even though there's lost of references prior to this: ... Dim BCPubPoint As IWMSBroadcastPublishingPoint Dim Playlist As IWMSPlaylist ... If BCPubPoint.BroadcastStatus = WMS_BROADCAST_PUBLISHING_POINT_STATUS.WMS_BROADCAST_PUBLISHING_POINT_STOPPED Then BCPubPoint.Start() Playlist = BCPubPoint.SharedPlaylist If I comment that one line, it doesn't blow up. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)

                P Offline
                P Offline
                progload
                wrote on last edited by
                #7

                While CP was Down for the count... I did a little more investigating and came up with this: There are (after W2k3 SP1 Install) "Two" different versions. -interop_msxml.dll in sdk: 2.0.0.0 -interop_msxml.dll in SP1: 9.0.3693 -microsoft.windowsmediaservices.dll in sdk: 9.0.0.3665 -microsoft.windowsmediaservices.dll in SP1: 9.0.0.3693 I referenced the ones from the original SDk (v2.0.0.0 and v9.0.3665) and it seems to go back to working on mine here.. and my old test code is working again. What other problems it will have.. I have not checked out as of this time. When I reference the ones from SP1(v9.0.3693 and v9.0.0.369) I get the error you describe. I'll go ahead and download the New SDK for SP1 and see what happens but it may take a day or two. I hope some of this Helps.. progload

                D 2 Replies Last reply
                0
                • P progload

                  While CP was Down for the count... I did a little more investigating and came up with this: There are (after W2k3 SP1 Install) "Two" different versions. -interop_msxml.dll in sdk: 2.0.0.0 -interop_msxml.dll in SP1: 9.0.3693 -microsoft.windowsmediaservices.dll in sdk: 9.0.0.3665 -microsoft.windowsmediaservices.dll in SP1: 9.0.0.3693 I referenced the ones from the original SDk (v2.0.0.0 and v9.0.3665) and it seems to go back to working on mine here.. and my old test code is working again. What other problems it will have.. I have not checked out as of this time. When I reference the ones from SP1(v9.0.3693 and v9.0.0.369) I get the error you describe. I'll go ahead and download the New SDK for SP1 and see what happens but it may take a day or two. I hope some of this Helps.. progload

                  D Offline
                  D Offline
                  DaveC426913
                  wrote on last edited by
                  #8

                  It's a *huge* help just knowing that it isn't me and my lack of knowledge. So, I don't know if I have versions from before but I'll go looking. Thanks - and keep me posted. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)

                  1 Reply Last reply
                  0
                  • P progload

                    While CP was Down for the count... I did a little more investigating and came up with this: There are (after W2k3 SP1 Install) "Two" different versions. -interop_msxml.dll in sdk: 2.0.0.0 -interop_msxml.dll in SP1: 9.0.3693 -microsoft.windowsmediaservices.dll in sdk: 9.0.0.3665 -microsoft.windowsmediaservices.dll in SP1: 9.0.0.3693 I referenced the ones from the original SDk (v2.0.0.0 and v9.0.3665) and it seems to go back to working on mine here.. and my old test code is working again. What other problems it will have.. I have not checked out as of this time. When I reference the ones from SP1(v9.0.3693 and v9.0.0.369) I get the error you describe. I'll go ahead and download the New SDK for SP1 and see what happens but it may take a day or two. I hope some of this Helps.. progload

                    D Offline
                    D Offline
                    DaveC426913
                    wrote on last edited by
                    #9

                    Well, with a bit of fancy footwork, I seem to have gotten v2.0.0.0 in there and it is behaving thus far. I can't really say how, since I don't really understand the interplay between adding a reference, including the dll in the folder and creating the runtime of the dll. Note there is a diff in filenames between 2.0.0.0 and 9.0.0.*: interop_msxml.dll vs. interop_MSXML.dll. I don't know if that factors in or not. It did allow me to have both dlls in the folders simultaneously whikleI was busy configuring it. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)

                    D 1 Reply Last reply
                    0
                    • D DaveC426913

                      Well, with a bit of fancy footwork, I seem to have gotten v2.0.0.0 in there and it is behaving thus far. I can't really say how, since I don't really understand the interplay between adding a reference, including the dll in the folder and creating the runtime of the dll. Note there is a diff in filenames between 2.0.0.0 and 9.0.0.*: interop_msxml.dll vs. interop_MSXML.dll. I don't know if that factors in or not. It did allow me to have both dlls in the folders simultaneously whikleI was busy configuring it. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)

                      D Offline
                      D Offline
                      DaveC426913
                      wrote on last edited by
                      #10

                      Have you had any luck on tracking this discrepancy down? I continue to have this problem, despite a brief period where I seem to have gotten it working. ________________________________________________________________________ Dave Y10K bug! Let's not get caught with our pants down **AGAIN**! (DC 02002)

                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • World
                      • Users
                      • Groups