|
Strange. I never had you pegged for one of those.
|
|
|
|
|
I think I am a refrigerator. I would go seek help but the wife likes the light when I sleep with my mouth open.
Within you lies the power for good - Use it!
|
|
|
|
|
There seems to be a definite pattern regarding the sluggishness of a normally decent system. It only gets this way when MS updates are wanting to restart the system. I've thought this enough times so that when it starts happening I check and sure enough, today there are 19 important updates! I know that the only way to get a peppy system again is to restart...installing the updates that are waiting.  I feeling like I'm being throttled into submission! 
"Go forth into the source" - Neal Morse
|
|
|
|
|
I've been sluggish all week... Please someone press my restart button
|
|
|
|
|
Sander Rossel wrote: someone press my restart button
 where exactly is this "button"?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
My guess is, you don't want to know.
|
|
|
|
|
I wish I knew!
Although sometimes such buttons can only be pressed by sticking a pin in a tiny hole on the back, so you don't press it accidentally 
On second though... Don't press mine
|
|
|
|
|
I think this is probably not relevant to what you observe, but, just in case:
People with pre-Win10 systems who have installed KB30355, are reporting slow downs and decreased disk-space because, as you may know, that little devil downloads whopping chunks of Win10 even when you have not chosen to upgrade.
cheers, Bill
«I want to stay as close to the edge as I can without going over. Out on the edge you see all kinds of things you can't see from the center» Kurt Vonnegut.
|
|
|
|
|
|
I've noticed this myself, when updates are waiting the machine slows down. I *think* what is happening is that if you don't elect to restart it installs the updates in the background anyway, which (on my machine) takes about 25% of the cpu. I can leave it like this, trickle installing, until it's done or you can do a reboot where the system them instigates the dreaded "Installing 1 of 29...." where the updates are done with the full resources available, ergo quicker.
Just a guess though.
|
|
|
|
|
"Of course it's a coincidence, Harry, but does that mean it's not a conspiracy?" -- Dumbledore
|
|
|
|
|
Hi,
I am converting Visual studio 2010 web site to Visual studio 2015. Also there are so many projects included in solution and referenced to my website.
Currently I am facing so many error while building web site. Error "
The type 'LISTTYPE' is defined in an assembly that is not referenced. You must add a reference to assembly 'App_Code.fk4bcd9f, Version=1.0.5822.18831, Culture=neutral, PublicKeyToken=null' " Most of the errors are on User controls and aspx pages.
Can anyone help me out on this?
Thanks in advance.
Thanks!
Kavita
kmpatel
|
|
|
|
|
|
a) wrong place.
b) the error message is telling you exactly what the problem is. I suggest you speak to your teacher/lecturer and ask them to help you.
c) learn to read.
|
|
|
|
|
R. Giskard Reventlov wrote: the error message is telling you exactly what the problem is
To be honest, App_Code.fk4bcd9f doesn't sound like an assembly you'd find easily...
|
|
|
|
|
 Fair point: but at least it's a start.
|
|
|
|
|
How many do you want?
I can email you as many copies as you need, for a very reasonable price... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
You must be mistaken me for someone who's missing a reference to App_Code.fk4bcd9f 
|
|
|
|
|
Yes, seems to be a conversion snag. Maybe a referenced assembly is still using the older framework.
|
|
|
|
|
R. Giskard Reventlov wrote: the error message is telling you exactly what the problem is.
You've got to be kidding. That's a completely baffling error message, even to me, and I am probably the 42nd smartest guy on this planet. 
|
|
|
|
|
Not really. Go back to the unconverted application. Find that type. Boom! You've made a start.
|
|
|
|
|
R. Giskard Reventlov wrote: Not really. Go back to the unconverted application. Find that type. Boom! You've made a start.
There's no such assembly. It's a Visual Studio generated intermediary. And the name/version etc. varies based on compiler version.
|
|
|
|
|
Agreed. But at least if you know what/where it should be/comes from/does, that's a start.
|
|
|
|
|
It's way harder than that. This seems to be a failed conversion attempt, or a partial success. It may even be a bug in the conversion, or a Nuget issue. There could be a 100 ways this may have been caused, and it will require an experienced person to sit and debug this through to fruition.
|
|
|
|
|
Start at the beginning. If you can figure what it should have been, you're on your way. That isn't to say it won't, ultimately, be one of the myriad other things it might turn out to be but you have to start somewhere. I've done many conversions from one version of VS to another over the years. Yes, it can get complex but quite often it is not.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
