|
I hate Chrome. Every few days I have to close it, then go into Task Manager and kill all the "extra" Chrome processes that hang around even after closing the browser.
If I don't, the mouse starts hesitating and disconnecting.
But I'm stuck with Chrome for some things, so I can't not use it. :'(
|
|
|
|
|
we could do this[^]. Or not. Probably not.
On the other hand, you have different fingers. - Steven Wright
|
|
|
|
|
I don't need this tool. I have a built-in device attached to myself and can do this especially when i drink lots of beer.
|
|
|
|
|
I see some minor differences there, especially when you are crawling on the ground and can't find your way out of the garden anymore. Bonus points if it's not your garden and they have to call the cops to drag you out.
So what do we learn? You are not drunk as long as you can still lie on the floor without holding onto something.
|
|
|
|
|
Vincent Maverick Durano wrote: I have a built-in device attached to myself and can do this especially when i drink lots of beer.
That's very much corded.
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy Falcon.
|
|
|
|
|
I wonder how many people do NOT see the problem with that...
|
|
|
|
|
Why should I see a problem? Every minute a sucker is born and there we have our customers. Ever since we replaced the guys from sales and marketing with trained monkeys there also are no problems anymore, no matter what we are trying to sell.
|
|
|
|
|
Sander Rossel wrote: I wonder how many people do NOT see the problem with that.
You mean putting all the heads together?
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy Falcon.
|
|
|
|
|
Vunic wrote: You mean putting all the heads together?
On the other hand, you have different fingers. - Steven Wright
|
|
|
|
|
Are you saying that you CAN NOT solve the problem?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
In Ireland we have the cloud hosted version of that.
Can't see how you turn it off though.
|
|
|
|
|
We have that technology in Wales as well - all I need now is a remote control for it...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Duncan Edwards Jones wrote: In Ireland we have the cloud hosted version of that.
Can't see how you turn it off though.
But hey, you can water entire neighborhoods at once!
On the other hand, you have different fingers. - Steven Wright
|
|
|
|
|
Well ... Kickstarter has funded dafter projects ...
All we need for this is the well-proven Star Trek replicators in a small package. Or Teleport technology, perhaps.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Either that, or take the device to a clear mountain stream, and apply the Law of Contagion
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
"Homeopathic Hosepipe"? Yeah, that could work. Kickstarter would get that backed in no time!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Two days ago I started a new solution in Visual Studio 2017 Community that has several projects, targeting .Net 4.7. Very soon I noticed in the App.config file of every project, that intellisense was whining that the configuration element was not set. It was just a warning, the solution compiled fine. Nevertheless I found it irritating and set out to get rid of the warning.
I tried every trick I could think of, kept me busy for hours and I was contemplating drastic action, including suicide!
In the end it finally dawned on me: Targeting the brand new .NET 4.7, there was something amiss in the schemas called for in the config file. Another hour or so struggling with schemas, I tried to change the catalog.xml file that is in this folder:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Xml\Schemas
In the catalog.xml file, edit the line that contains ".NETFramework,Version=v4.6" and change 4.6 to 4.7
Problem solved! But it took the better part of a day.
Get me coffee and no one gets hurt!
|
|
|
|
|
This is irritating. I solve it by opening the main menu item XML, Schemas and selecting 'use this schema' for DotNetConfig.xsd. Shouldn't have to do this.
|
|
|
|
|
If you follow my steps and edit the catalog file, you will find that the schema: DotNetConfig.xsd is automatically selected for all projects in the solution.
[Edit] This solution only works for projects targeting .NET 4.7 If you target any earlier version, you most probably will run into the same issue.[/Edit]
Get me coffee and no one gets hurt!
modified 1-Aug-17 20:33pm.
|
|
|
|
|
Done.
Thanks
|
|
|
|
|
This "BUG" had corrupted the configuration data of every single one of our internal software and a published one that depend on .NET configuration system after a certain Windows upgrade that includes 4.7. I don't think that is a good way of upgrading a system, that's not a "feature" at all
|
|
|
|
|
|
Quote: I'd just delete it What? And forego the satisfaction of a nasty problem solved?
Get me coffee and no one gets hurt!
|
|
|
|
|
If you have been tasked with "removing roadblocks", then you may find that posting a detour sign is insufficient.
|
|
|
|
|
Cornelius Henning wrote: I was contemplating drastic action, including suicide! OK - but don't keep us in suspense.
Did you or didn't you, and if so, how did it work out?
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|