Click here to Skip to main content

Welcome to the Lounge

For discussing anything related to a software developer's life but is not for programming questions. Got a programming question?

The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.

Member 1054947415-Dec-17 3:34

Member 10549474

15-Dec-17 3:34

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.

Re: Strange errors

F-ES Sitecore15-Dec-17 3:36

15-Dec-17 3:36

vbproj? What the hell is that?

Re: Strange errors

Member 1054947415-Dec-17 3:40

Member 10549474

15-Dec-17 3:40

vbproj = VB Project file.

VB = Visual Basic.

Basic = Beginners All purpose Symbolic Instruction Code.

Ok? Smile | :)

Smile | :)

Re: Strange errors

OriginalGriff15-Dec-17 4:03

15-Dec-17 4:03

There is nothing "OK" about a language which includes On Error Resume Next

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!

Re: Strange errors

den2k8815-Dec-17 4:26

15-Dec-17 4:26

Dreadful words. Have you tried with Option Base 1?

GCS d-- s-/++ a- C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X

Re: Strange errors

F-ES Sitecore15-Dec-17 4:24

15-Dec-17 4:24

Visual Basic? Sorry....I still don't know what that is.

*gets back to proper coding*

Re: Strange errors

ClockMeister18-Dec-17 3:51

18-Dec-17 3:51

(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

Re: Strange errors

H.Brydon26-Dec-17 18:22

26-Dec-17 18:22

Yeah and you should be fined for using it.

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

Re: Strange errors

ClockMeister27-Dec-17 2:13

27-Dec-17 2:13

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

Re: Strange errors

CodeWraith15-Dec-17 3:44

15-Dec-17 3:44

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.

Re: Strange errors

James Lonero19-Dec-17 5:17

19-Dec-17 5:17

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.

Re: Strange errors

CodeWraith19-Dec-17 8:09

19-Dec-17 8:09

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.

Re: Strange errors

S Houghtelin15-Dec-17 3:49

15-Dec-17 3:49

~~The sln file is an IDE environment setup, how you have your toolbars set, windows, the last bit of code you were working on etc.~~
This states what an sln file is correctly. Solution (.Sln) File[^]

Delete the sln file, open the project and setup your environment again. when you close the project you will be prompted to save to a new sln file.

It was broke, so I fixed it.

modified 15-Dec-17 10:08am.

Re: Strange errors

Eddy Vluggen15-Dec-17 3:51

15-Dec-17 3:51

It does not hold toolbar-customizations; it is a list of all the project-files in the solution.

Sounds to me like he simply lost some references - something that is bound to happen if you add references to locally installed products, instead if directly to an assembly in your working-folder.

Bastard Programmer from Hell Suspicious | :suss:

Suspicious | :suss:

If you can't read my code, try converting it here[^]

Re: Strange errors

S Houghtelin15-Dec-17 3:58

15-Dec-17 3:58

Doh! we're both wrong... Blush | :O

Blush | :O

Unsure | :~

This is what it contains

Microsoft Visual Studio Solution File, Format Version 11.00
# Visual C# Express 2010
Project("{FAE04EC0-301F-11D3-BF4B-00004F79EFBC}") = "MyProject", "MyProject.csproj", "{7155F049-C533-41FB-B5BD-ABD502AF3CD3}"
EndProject
Global
	GlobalSection(SolutionConfigurationPlatforms) = preSolution
		Debug|x86 = Debug|x86
		Release|x86 = Release|x86
	EndGlobalSection
	GlobalSection(ProjectConfigurationPlatforms) = postSolution
		{7155F049-C533-41FB-B5BD-ABDEF2AF3CD3}.Debug|x86.ActiveCfg = Debug|x86
		{7155F049-C533-41FB-B5BD-ABDEF2AF3CD3}.Debug|x86.Build.0 = Debug|x86
		{7155F049-C533-41FB-B5BD-ABDEF2AF3CD3}.Release|x86.ActiveCfg = Release|x86
		{7155F049-C533-41FB-B5BD-ABDEF2AF3CD3}.Release|x86.Build.0 = Release|x86
	EndGlobalSection
	GlobalSection(SolutionProperties) = preSolution
		HideSolutionNode = FALSE
	EndGlobalSection
EndGlobal

It was broke, so I fixed it.

Re: Strange errors

Eddy Vluggen15-Dec-17 3:59

15-Dec-17 3:59

I am not wrong.

Projects are organized in a solution. There's a different file for customizations.

Bastard Programmer from Hell Suspicious | :suss:

Suspicious | :suss:

If you can't read my code, try converting it here[^]

Re: Strange errors

S Houghtelin15-Dec-17 4:05

15-Dec-17 4:05

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.

Re: Strange errors

Eddy Vluggen15-Dec-17 5:23

15-Dec-17 5:23

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 Suspicious | :suss:

Suspicious | :suss:

If you can't read my code, try converting it here[^]

Re: Strange errors

lopatir15-Dec-17 3:59

15-Dec-17 3:59

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.

Re: Strange errors

dandy7215-Dec-17 5:36

15-Dec-17 5:36

Lopatir wrote:
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.

Set MS software on fire and let it burn.

Gotcha.

Re: Strange errors

RedDk15-Dec-17 9:11

15-Dec-17 9:11

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?

Re: Strange errors

Member 1054947415-Dec-17 18:07

Member 10549474

15-Dec-17 18:07

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?

Re: Strange errors

KLPounds18-Dec-17 1:41

18-Dec-17 1:41

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.

Re: Strange errors

Bruce Patin18-Dec-17 4:32

18-Dec-17 4:32

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

Re: Strange errors

Member 1054947420-Dec-17 4:50

Member 10549474

20-Dec-17 4:50

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... Blush | :O

Blush | :O

General News Suggestion Question Bug Answer Joke Praise Rant Admin

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.