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. The Lounge
  3. Strange errors

Strange errors

Scheduled Pinned Locked Moved The Lounge
visual-studioquestioncsharpdesignhelp
25 Posts 14 Posters 28 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.
  • M Member 10549474

    Recently updated Visual Studio and when I went back in and loaded a project all was fine until I tried to look at the design of the form. It came up with all kinds of errors to prevent me from viewing the form. Things like my AxMediaplayer was not found; things like ColorPack5,6 and 7 not being found. All kinds of weird things. Finally re-installed VS and things seemed normal again until just now - load a .sln (solution) file and I had the same problem. Closed it down and restarted - had the same thing, but more and different problems to prevent me looking at the form. Thought, Oh no not again, been bashing away at this for more than two days trying to get it sorted. In desperation tried firing up the .vbproj file instead of the .sln file - and hey presto, everything works just fine... So what is going on? Last night the .sln file worked fine, come back to it today and it is NBG. But the vbproj file is fine... Anyhow, anyone else have the same kind of problem, then try loading the vbproj file instead of a sln file.

    R Offline
    R Offline
    RedDk
    wrote on last edited by
    #16

    Just for fun, and because we're all friends here in The Lounge (with a possible exception or two (they know they aren't welcome actually, but post nonsense anyway)), unzip this original assembly of "projection" from the ... uhm ... package into a brand new target directory. To avoid any cross-contamination/etc. Now, comment out the .suo alone. Make it "x.suo.manifest". NOW open the .sln ... does this (gulp) help any?

    M 1 Reply Last reply
    0
    • R RedDk

      Just for fun, and because we're all friends here in The Lounge (with a possible exception or two (they know they aren't welcome actually, but post nonsense anyway)), unzip this original assembly of "projection" from the ... uhm ... package into a brand new target directory. To avoid any cross-contamination/etc. Now, comment out the .suo alone. Make it "x.suo.manifest". NOW open the .sln ... does this (gulp) help any?

      M Offline
      M Offline
      Member 10549474
      wrote on last edited by
      #17

      Well, it seems pretty random - it doesn't do it with all projects, nor all the time. For instance, opened a project, looked at the design of the form, but couldn't, loads of 'errors'. So just closed down Visual Studio, started it up again and went and loaded the same project file and just sat waiting for ten seconds or so, then took deep breath and looked at design of form - all worked perfectly. Do you think I was just too fast trying to look at the form and Visual Studio was still 'loading' part of the project?

      1 Reply Last reply
      0
      • M Member 10549474

        Recently updated Visual Studio and when I went back in and loaded a project all was fine until I tried to look at the design of the form. It came up with all kinds of errors to prevent me from viewing the form. Things like my AxMediaplayer was not found; things like ColorPack5,6 and 7 not being found. All kinds of weird things. Finally re-installed VS and things seemed normal again until just now - load a .sln (solution) file and I had the same problem. Closed it down and restarted - had the same thing, but more and different problems to prevent me looking at the form. Thought, Oh no not again, been bashing away at this for more than two days trying to get it sorted. In desperation tried firing up the .vbproj file instead of the .sln file - and hey presto, everything works just fine... So what is going on? Last night the .sln file worked fine, come back to it today and it is NBG. But the vbproj file is fine... Anyhow, anyone else have the same kind of problem, then try loading the vbproj file instead of a sln file.

        K Offline
        K Offline
        KLPounds
        wrote on last edited by
        #18

        Late to the game and havent read through all the replies yet. There is/was a ticket open with MS on this behavior. Some even had similar project problems in c#. But it was mostly vb projects. The workaround that I found solved this problem was to turn off "allow parallel project I initialization" in VS options. Restart VS and load your project.. this also is supposed to be fixed in 15.5.2. I downloaded it end of day Friday so will be formally testing it this morning. Else parallel project initialization gets turned off again.

        1 Reply Last reply
        0
        • F F ES Sitecore

          Visual Basic? Sorry....I still don't know what that is. *gets back to proper coding*

          C Offline
          C Offline
          ClockMeister
          wrote on last edited by
          #19

          (To the OP) ... Don't listen to these coding snobs ... VB (particularly the .Net version) is a fine language. -CM

          If you think hiring a professional is expensive, wait until you hire an amateur! - Red Adair

          H 1 Reply Last reply
          0
          • M Member 10549474

            Recently updated Visual Studio and when I went back in and loaded a project all was fine until I tried to look at the design of the form. It came up with all kinds of errors to prevent me from viewing the form. Things like my AxMediaplayer was not found; things like ColorPack5,6 and 7 not being found. All kinds of weird things. Finally re-installed VS and things seemed normal again until just now - load a .sln (solution) file and I had the same problem. Closed it down and restarted - had the same thing, but more and different problems to prevent me looking at the form. Thought, Oh no not again, been bashing away at this for more than two days trying to get it sorted. In desperation tried firing up the .vbproj file instead of the .sln file - and hey presto, everything works just fine... So what is going on? Last night the .sln file worked fine, come back to it today and it is NBG. But the vbproj file is fine... Anyhow, anyone else have the same kind of problem, then try loading the vbproj file instead of a sln file.

            B Offline
            B Offline
            Bruce Patin
            wrote on last edited by
            #20

            I always load my forms into a text editor. Never any problem.

            M 1 Reply Last reply
            0
            • C CodeWraith

              Member 10549474 wrote:

              Recently updated Visual Studio

              Big mistake. I would love to believe that Mickeysoft did this intentionally because they want to send VB to the boneyard, but the truth seems to be that they are working hard on driving away all developers.

              I have lived with several Zen masters - all of them were cats.

              J Offline
              J Offline
              James Lonero
              wrote on last edited by
              #21

              I would like to say that VB is Microsoft's answer to JavaScript, but JavaScript came later. So, JavaScript is the rest of the world's Basic with C like syntax.

              C 1 Reply Last reply
              0
              • J James Lonero

                I would like to say that VB is Microsoft's answer to JavaScript, but JavaScript came later. So, JavaScript is the rest of the world's Basic with C like syntax.

                C Offline
                C Offline
                CodeWraith
                wrote on last edited by
                #22

                Exactly. I ever liked intepreters, even back in the days of 8 bit processors. A C compiler on 8 bit computers was not really an option back then, so I just went on with machine code and never looked back.

                I have lived with several Zen masters - all of them were cats.

                1 Reply Last reply
                0
                • B Bruce Patin

                  I always load my forms into a text editor. Never any problem.

                  M Offline
                  M Offline
                  Member 10549474
                  wrote on last edited by
                  #23

                  I don't think it is anything to do with .sln or .vbproj files... I have found now, that almost invariably when I open a project, either by opening the .sln or .vbproj file, the first time you do so, and look at the design page of a form, it is full of errors and you are unable to view the form. So, now I just close down Visual Studio altogether, start it up again and load exactly the same file in the same way and it all works fine - the design page shows my form as it should be. Gawd knows why... I think over xmas I'll format the HDD, reinstall Windows from scratch and reinstall VS - the PC is taking longer to boot up anyway, so it is about time, I suppose. And the TV won't be worth watching anyway... :-O

                  1 Reply Last reply
                  0
                  • C ClockMeister

                    (To the OP) ... Don't listen to these coding snobs ... VB (particularly the .Net version) is a fine language. -CM

                    If you think hiring a professional is expensive, wait until you hire an amateur! - Red Adair

                    H Offline
                    H Offline
                    H Brydon
                    wrote on last edited by
                    #24

                    Yeah and you should be fined for using it.

                    I'm retired. There's a nap for that... - Harvey

                    C 1 Reply Last reply
                    0
                    • H H Brydon

                      Yeah and you should be fined for using it.

                      I'm retired. There's a nap for that... - Harvey

                      C Offline
                      C Offline
                      ClockMeister
                      wrote on last edited by
                      #25

                      You're joking, right? (Tough to tell in a text-only message).

                      If you think hiring a professional is expensive, wait until you hire an amateur! - Red Adair

                      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