Strange errors
-
vbproj = VB Project file. VB = Visual Basic. Basic = Beginners All purpose Symbolic Instruction Code. Ok? :)
There is nothing "OK" about a language which includes
On Error Resume NextBad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
Eddy Vluggen wrote:
It does not hold toolbar-customizations; it is a list of all the project-files in the solution.
I was wrong about the customization, however, I see one file listed, my project has well over a dozen. I don't wish to turn this into a debate, I did test deleting the sln file and was prompted to save new one, that part works. Cheers!
It was broke, so I fixed it.
-
vbproj = VB Project file. VB = Visual Basic. Basic = Beginners All purpose Symbolic Instruction Code. Ok? :)
Visual Basic? Sorry....I still don't know what that is. *gets back to proper coding*
-
There is nothing "OK" about a language which includes
On Error Resume NextBad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!
-
Eddy Vluggen wrote:
It does not hold toolbar-customizations; it is a list of all the project-files in the solution.
I was wrong about the customization, however, I see one file listed, my project has well over a dozen. I don't wish to turn this into a debate, I did test deleting the sln file and was prompted to save new one, that part works. Cheers!
It was broke, so I fixed it.
S Houghtelin wrote:
I see one file listed, my project has well over a dozen.
Because it is not a project file, but a solution - a list of proj files.
S Houghtelin wrote:
I don't wish to turn this into a debate
It was a correction, not an invitation to a debate indeed. Solution (.Sln) File[^]
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
Member 10549474 wrote:
Recently updated Visual Studio
A boy scout motto is "once your camp fire is burning OK a sure way to put it out is to try and improve it." ... I've found microsoft products are exactly like that. (in fact even more-so, because camp fires I sometimes have managed to improve.)
Signature ready for installation. Please Reboot now.
-
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.
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?
-
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?
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?
-
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.
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.
-
Visual Basic? Sorry....I still don't know what that is. *gets back to proper coding*
(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
-
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.
I always load my forms into a text editor. Never any problem.
-
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.
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.
-
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.
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.
-
I always load my forms into a text editor. Never any problem.
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
-
(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
-
Yeah and you should be fined for using it.
I'm retired. There's a nap for that... - Harvey
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
