Could somebody please sacrifice a sheep or a virgin or whatever
-
DaveAuld wrote:
What, a sheep or a virgin, or a virgin sheep?
Well, the third one covers all the bases.
I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be
Forgive your enemies - it messes with their heads
-
OriginalGriff wrote:
Here the men have to run fast...
... to catch the sheep.
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
Regretably, not. They like their chips in Wales[^]
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
-
Regretably, not. They like their chips in Wales[^]
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
-
Sure you didn't change anything. :-D (been there, done that, got so many f'ing T-shirts I could make sails for the Queen Mary 2[^] out of them)
Software Zen:
delete this;
You may have some trouble fitting all those T-shirts to the Queen Mary 2. They seem to have hidden the masts from you. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
-
I live in Wales - no virgins for miles. And definitely no virgin sheep - before you get started about Cardiff Leisure Centres... :laugh:
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Is that you mister Brittas? :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
-
You may have some trouble fitting all those T-shirts to the Queen Mary 2. They seem to have hidden the masts from you. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
Details, details...
Software Zen:
delete this;
-
My work here is done... :laugh:
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
-
I'm working away quite happily in Visual Studio (2008 if that matters). Suddenly on one of my attempts to run the app I have 102 errors, and a worrying message that the number of errors has exceeded the maximum. Nothing has changed I splutter... Visual Studio is unimpressed by my entreaty. I get Subversion to weigh in on the debate, hoping it will persuade Visual Studio that nothing has changed. Visual Studio laughs at Subversion calling it a "puny Open Source type thing" and farting in it's general direction. I'm not overly worried, this happened a few days ago and kicking Visual Studio upside it's head did the trick. I shut down Visual Studio and start a new instance. Usually new instances are more compliant than instances that have been around a while and had a chance to get stroppy. But no. This time my new instance has been in tough with the old instance and gotten the run down on how to piss me off. So, I'm still stuck with 102 and maybe more errors. Still nothing has changed. I'm about to reboot the PC which will probably fix the issue. In the mean time could somebody please sacrifice a sheep or a virgin to whatever Gods determine Visual Studio's mood. I don't have either close to hand. -Rd
OK, thanks to all those who have been ritually mutilating lifestock, I am now back up and running. Rebooting and heading to the canteen didn't do it. The secret, and this might be important for others, was to actually go outside the building and come back in while rebooting. I'm now searching for the GO_GET_FRESH_AIR flag in Visual Studio so I can turn it off. Again, thanks to all, particularly the virgin sheep that gave their lives for a good cause. Please let me hit production before the gods get the munchies again. -Rd
-
I'm working away quite happily in Visual Studio (2008 if that matters). Suddenly on one of my attempts to run the app I have 102 errors, and a worrying message that the number of errors has exceeded the maximum. Nothing has changed I splutter... Visual Studio is unimpressed by my entreaty. I get Subversion to weigh in on the debate, hoping it will persuade Visual Studio that nothing has changed. Visual Studio laughs at Subversion calling it a "puny Open Source type thing" and farting in it's general direction. I'm not overly worried, this happened a few days ago and kicking Visual Studio upside it's head did the trick. I shut down Visual Studio and start a new instance. Usually new instances are more compliant than instances that have been around a while and had a chance to get stroppy. But no. This time my new instance has been in tough with the old instance and gotten the run down on how to piss me off. So, I'm still stuck with 102 and maybe more errors. Still nothing has changed. I'm about to reboot the PC which will probably fix the issue. In the mean time could somebody please sacrifice a sheep or a virgin to whatever Gods determine Visual Studio's mood. I don't have either close to hand. -Rd
Sorry, I thought we had requested 72 from procurement, but the shipment got blown up.
-
I'm working away quite happily in Visual Studio (2008 if that matters). Suddenly on one of my attempts to run the app I have 102 errors, and a worrying message that the number of errors has exceeded the maximum. Nothing has changed I splutter... Visual Studio is unimpressed by my entreaty. I get Subversion to weigh in on the debate, hoping it will persuade Visual Studio that nothing has changed. Visual Studio laughs at Subversion calling it a "puny Open Source type thing" and farting in it's general direction. I'm not overly worried, this happened a few days ago and kicking Visual Studio upside it's head did the trick. I shut down Visual Studio and start a new instance. Usually new instances are more compliant than instances that have been around a while and had a chance to get stroppy. But no. This time my new instance has been in tough with the old instance and gotten the run down on how to piss me off. So, I'm still stuck with 102 and maybe more errors. Still nothing has changed. I'm about to reboot the PC which will probably fix the issue. In the mean time could somebody please sacrifice a sheep or a virgin to whatever Gods determine Visual Studio's mood. I don't have either close to hand. -Rd
Richard A. Dalton wrote:
I'm about to reboot the PC which will probably fix the issue.
You might also consider deleting that project's temp files and folders.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Man who follows car will be exhausted." - Confucius
-
Yes. Bacon is the solutions to all of life's problems. Or is that beer...
"Benjamin is nobody's friend. If Benjamin were an ice cream flavor, he'd be pralines and dick." ~ Garth Algar "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." ~ Paul Neal "Red" Adair
-
I'm working away quite happily in Visual Studio (2008 if that matters). Suddenly on one of my attempts to run the app I have 102 errors, and a worrying message that the number of errors has exceeded the maximum. Nothing has changed I splutter... Visual Studio is unimpressed by my entreaty. I get Subversion to weigh in on the debate, hoping it will persuade Visual Studio that nothing has changed. Visual Studio laughs at Subversion calling it a "puny Open Source type thing" and farting in it's general direction. I'm not overly worried, this happened a few days ago and kicking Visual Studio upside it's head did the trick. I shut down Visual Studio and start a new instance. Usually new instances are more compliant than instances that have been around a while and had a chance to get stroppy. But no. This time my new instance has been in tough with the old instance and gotten the run down on how to piss me off. So, I'm still stuck with 102 and maybe more errors. Still nothing has changed. I'm about to reboot the PC which will probably fix the issue. In the mean time could somebody please sacrifice a sheep or a virgin to whatever Gods determine Visual Studio's mood. I don't have either close to hand. -Rd
It's probably an issue with the designer being stupid and re-adding files or references that it shouldn't. On the project I'm currently working on, the Infragistics designer likes randomly adding a circular project reference whenever I press Control+Z in the source view of a page with the Infragistics toolbar control. This might not fit your problem exactly, but hopefully it gives you an idea of where to start looking.