days and nights of Visual Studio hell
-
This post is made based on the belief that: "suffering shared is suffering diluted" ... which does seem to me to be one modal use of the Lounge :) You have all been in software "hell," I'd bet; if not with Visual Studio, then with an OS issue, or some other issue with an application, or your own code, that, suddenly, begins to malfunction for no apparent reason; an application that won't install, etc., etc. And, I suspect, that you, like me, have tarried long in software hell, because you wanted, at all cost, to avoid the dreaded re-install of the OS, followed by endless upgrading, and endless re-install of all your tools, and programs. I'll spare you the "Google street-level view," which I am exposing, and getting some help with, kind of, on the MS Visual Studio install forum. Here's a high-altitude fly-by view: It started with installing an upgrade to the MindScape dingus (Add In ? Extension ?) to Visual Studio RC 1. Then, the next day, trying to start Visual Studio: it goes into an endless loop presenting a dialog "Loading Components." Only way out: Task Manager: kill devenv.exe. So, what could be more natural, at this time, when MS has a free 90 day trial of Visual Studio 2012 Pro RTM, than to uninstall the RC 1, and install the RTM ? Un-install of RC1 fails with countless issues. Hand editing the Registry to remove all RC1 and FrameWork 4.5RC references, results in the apparent removal of RC1, but then RTM will not install. Endless fiddling with more registry entries, removing selected .NET components: finally RTM installs, but will show, on first launch, when I try to create a Windows Forms solution, a dialog telling me it can't "create the compiler." If I then ignore this dialog, and create a second solution; I end up with a viable solution that will build and run (!), but which will not allow me to access to the Design view, of any Form or UserControl :) I bet you've seen that window with deep blue on top, and a yellow panel top-side, that usually appears when you have done some kind of messing around with the Designer.cs file in a WinForms project. I'd estimate I have now spent nearly twenty hours of my life, over the last five days, unable to use Visual Studio 2012, trying to get the RTM to work, and now trying to get it un-installed. That's major withdrawal syndrome for me, because: using VS is a favorite past-time, and I like to answer QA questions here, checking my answers by coding in 2012, before posting them, to make sure they are correct. Some of the help files I've be
-
This post is made based on the belief that: "suffering shared is suffering diluted" ... which does seem to me to be one modal use of the Lounge :) You have all been in software "hell," I'd bet; if not with Visual Studio, then with an OS issue, or some other issue with an application, or your own code, that, suddenly, begins to malfunction for no apparent reason; an application that won't install, etc., etc. And, I suspect, that you, like me, have tarried long in software hell, because you wanted, at all cost, to avoid the dreaded re-install of the OS, followed by endless upgrading, and endless re-install of all your tools, and programs. I'll spare you the "Google street-level view," which I am exposing, and getting some help with, kind of, on the MS Visual Studio install forum. Here's a high-altitude fly-by view: It started with installing an upgrade to the MindScape dingus (Add In ? Extension ?) to Visual Studio RC 1. Then, the next day, trying to start Visual Studio: it goes into an endless loop presenting a dialog "Loading Components." Only way out: Task Manager: kill devenv.exe. So, what could be more natural, at this time, when MS has a free 90 day trial of Visual Studio 2012 Pro RTM, than to uninstall the RC 1, and install the RTM ? Un-install of RC1 fails with countless issues. Hand editing the Registry to remove all RC1 and FrameWork 4.5RC references, results in the apparent removal of RC1, but then RTM will not install. Endless fiddling with more registry entries, removing selected .NET components: finally RTM installs, but will show, on first launch, when I try to create a Windows Forms solution, a dialog telling me it can't "create the compiler." If I then ignore this dialog, and create a second solution; I end up with a viable solution that will build and run (!), but which will not allow me to access to the Design view, of any Form or UserControl :) I bet you've seen that window with deep blue on top, and a yellow panel top-side, that usually appears when you have done some kind of messing around with the Designer.cs file in a WinForms project. I'd estimate I have now spent nearly twenty hours of my life, over the last five days, unable to use Visual Studio 2012, trying to get the RTM to work, and now trying to get it un-installed. That's major withdrawal syndrome for me, because: using VS is a favorite past-time, and I like to answer QA questions here, checking my answers by coding in 2012, before posting them, to make sure they are correct. Some of the help files I've be
Sorry to hear it - but this is why I don't touch "Release Candidate" or "Release To Market" or any other MS beta, until they ship the first true release version: SP1. Sorry, but I've been bitten by them too many times: I keep hoping they will improve, but they never do.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
-
This post is made based on the belief that: "suffering shared is suffering diluted" ... which does seem to me to be one modal use of the Lounge :) You have all been in software "hell," I'd bet; if not with Visual Studio, then with an OS issue, or some other issue with an application, or your own code, that, suddenly, begins to malfunction for no apparent reason; an application that won't install, etc., etc. And, I suspect, that you, like me, have tarried long in software hell, because you wanted, at all cost, to avoid the dreaded re-install of the OS, followed by endless upgrading, and endless re-install of all your tools, and programs. I'll spare you the "Google street-level view," which I am exposing, and getting some help with, kind of, on the MS Visual Studio install forum. Here's a high-altitude fly-by view: It started with installing an upgrade to the MindScape dingus (Add In ? Extension ?) to Visual Studio RC 1. Then, the next day, trying to start Visual Studio: it goes into an endless loop presenting a dialog "Loading Components." Only way out: Task Manager: kill devenv.exe. So, what could be more natural, at this time, when MS has a free 90 day trial of Visual Studio 2012 Pro RTM, than to uninstall the RC 1, and install the RTM ? Un-install of RC1 fails with countless issues. Hand editing the Registry to remove all RC1 and FrameWork 4.5RC references, results in the apparent removal of RC1, but then RTM will not install. Endless fiddling with more registry entries, removing selected .NET components: finally RTM installs, but will show, on first launch, when I try to create a Windows Forms solution, a dialog telling me it can't "create the compiler." If I then ignore this dialog, and create a second solution; I end up with a viable solution that will build and run (!), but which will not allow me to access to the Design view, of any Form or UserControl :) I bet you've seen that window with deep blue on top, and a yellow panel top-side, that usually appears when you have done some kind of messing around with the Designer.cs file in a WinForms project. I'd estimate I have now spent nearly twenty hours of my life, over the last five days, unable to use Visual Studio 2012, trying to get the RTM to work, and now trying to get it un-installed. That's major withdrawal syndrome for me, because: using VS is a favorite past-time, and I like to answer QA questions here, checking my answers by coding in 2012, before posting them, to make sure they are correct. Some of the help files I've be
Perhaps I'm naive, but I still tend to feel that this is how it should be done: Install: Copy file structure into an empty directory on the target machine Uninstall: Delete that directory Never, ever, put anything into the windows directory Read and write configuration information to/from files - if they are placed outside the target directory, document where they are located. If you are doing COM related stuff, or anything else that requires information to be added to the registry, provide a commandline utility that cleans up the registry.
Espen Harlinn Principal Architect, Software - Goodtech Projects & Services AS Projects promoting programming in "natural language" are intrinsically doomed to fail. Edsger W.Dijkstra
-
This post is made based on the belief that: "suffering shared is suffering diluted" ... which does seem to me to be one modal use of the Lounge :) You have all been in software "hell," I'd bet; if not with Visual Studio, then with an OS issue, or some other issue with an application, or your own code, that, suddenly, begins to malfunction for no apparent reason; an application that won't install, etc., etc. And, I suspect, that you, like me, have tarried long in software hell, because you wanted, at all cost, to avoid the dreaded re-install of the OS, followed by endless upgrading, and endless re-install of all your tools, and programs. I'll spare you the "Google street-level view," which I am exposing, and getting some help with, kind of, on the MS Visual Studio install forum. Here's a high-altitude fly-by view: It started with installing an upgrade to the MindScape dingus (Add In ? Extension ?) to Visual Studio RC 1. Then, the next day, trying to start Visual Studio: it goes into an endless loop presenting a dialog "Loading Components." Only way out: Task Manager: kill devenv.exe. So, what could be more natural, at this time, when MS has a free 90 day trial of Visual Studio 2012 Pro RTM, than to uninstall the RC 1, and install the RTM ? Un-install of RC1 fails with countless issues. Hand editing the Registry to remove all RC1 and FrameWork 4.5RC references, results in the apparent removal of RC1, but then RTM will not install. Endless fiddling with more registry entries, removing selected .NET components: finally RTM installs, but will show, on first launch, when I try to create a Windows Forms solution, a dialog telling me it can't "create the compiler." If I then ignore this dialog, and create a second solution; I end up with a viable solution that will build and run (!), but which will not allow me to access to the Design view, of any Form or UserControl :) I bet you've seen that window with deep blue on top, and a yellow panel top-side, that usually appears when you have done some kind of messing around with the Designer.cs file in a WinForms project. I'd estimate I have now spent nearly twenty hours of my life, over the last five days, unable to use Visual Studio 2012, trying to get the RTM to work, and now trying to get it un-installed. That's major withdrawal syndrome for me, because: using VS is a favorite past-time, and I like to answer QA questions here, checking my answers by coding in 2012, before posting them, to make sure they are correct. Some of the help files I've be
Got a new desktop a few weeks ago; a 64-bit monster-machine with 2 Gb of RAM, Windows 7 and Visual Studio 2010. Read a lot of rants when it came out, but it seems to be stable and it's relatively fast. Thank you, a hundred times, for beta-testing the software. Windows 7 is not as much a disaster as everybody claimed. Good luck with Win8 and VS2012 :)
BillWoodruff wrote:
I find it rather amazing that at this time of such sophistication in software, there isn't an un-installer program, produced by Microsoft, that can figure out what needs to be done: and "just do it."
There are Virtual Machines available - don't use your primary environment for experiments, it sucks when you have to live in the ruins of a failed experiment.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
Got a new desktop a few weeks ago; a 64-bit monster-machine with 2 Gb of RAM, Windows 7 and Visual Studio 2010. Read a lot of rants when it came out, but it seems to be stable and it's relatively fast. Thank you, a hundred times, for beta-testing the software. Windows 7 is not as much a disaster as everybody claimed. Good luck with Win8 and VS2012 :)
BillWoodruff wrote:
I find it rather amazing that at this time of such sophistication in software, there isn't an un-installer program, produced by Microsoft, that can figure out what needs to be done: and "just do it."
There are Virtual Machines available - don't use your primary environment for experiments, it sucks when you have to live in the ruins of a failed experiment.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
Eddy Vluggen wrote:
Got a new desktop a few weeks ago; a 64-bit monster-machine with 2 Gb of RAM, Windows 7...
Both my kids laptops are better specced than that.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
-
Eddy Vluggen wrote:
Got a new desktop a few weeks ago; a 64-bit monster-machine with 2 Gb of RAM, Windows 7...
Both my kids laptops are better specced than that.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
My laptop is as well. (6GB RAM, Intel i5 4-core CPU, 620 GB HDD, etc.)
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image. Stephen Hawking
-
Eddy Vluggen wrote:
Got a new desktop a few weeks ago; a 64-bit monster-machine with 2 Gb of RAM, Windows 7...
Both my kids laptops are better specced than that.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
Michael Martin wrote:
Both my kids laptops are better specced than that.
You upgraded them to the latest Visual Studio? ..look at it this way; if my application runs fast enough on my machine to "not" go on my nerves, it'll probably be good enough for a clients' machine.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
Got a new desktop a few weeks ago; a 64-bit monster-machine with 2 Gb of RAM, Windows 7 and Visual Studio 2010. Read a lot of rants when it came out, but it seems to be stable and it's relatively fast. Thank you, a hundred times, for beta-testing the software. Windows 7 is not as much a disaster as everybody claimed. Good luck with Win8 and VS2012 :)
BillWoodruff wrote:
I find it rather amazing that at this time of such sophistication in software, there isn't an un-installer program, produced by Microsoft, that can figure out what needs to be done: and "just do it."
There are Virtual Machines available - don't use your primary environment for experiments, it sucks when you have to live in the ruins of a failed experiment.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
Eddy Vluggen wrote:
a 64-bit monster-machine with 2 Gb of RAM
I'm assuming that's a typo.
Eddy Vluggen wrote:
There are Virtual Machines available - don't use your primary environment for experiments, it sucks when you have to live in the ruins of a failed experiment
I'm with you on this. My development environment is now virtualized, and getting rid of the RC was just a matter of deleting the machine, and installing the RTM on a clean OS. I still have VS 2008 and 2010 VMs ready to be fired up at any time (in fact, I still develop with 2010; I only have 2012 installed for tinkering with, until I'm ready to commit to it).
-
Eddy Vluggen wrote:
a 64-bit monster-machine with 2 Gb of RAM
I'm assuming that's a typo.
Eddy Vluggen wrote:
There are Virtual Machines available - don't use your primary environment for experiments, it sucks when you have to live in the ruins of a failed experiment
I'm with you on this. My development environment is now virtualized, and getting rid of the RC was just a matter of deleting the machine, and installing the RTM on a clean OS. I still have VS 2008 and 2010 VMs ready to be fired up at any time (in fact, I still develop with 2010; I only have 2012 installed for tinkering with, until I'm ready to commit to it).
-
Michael Martin wrote:
Both my kids laptops are better specced than that.
You upgraded them to the latest Visual Studio? ..look at it this way; if my application runs fast enough on my machine to "not" go on my nerves, it'll probably be good enough for a clients' machine.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
Eddy Vluggen wrote:
You upgraded them to the latest Visual Studio?
You'll notice I never mentioned Visual Studio at all in my reply, just the laptop specs. 4GB of RAM in both kids laptops.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
-
Got a new desktop a few weeks ago; a 64-bit monster-machine with 2 Gb of RAM, Windows 7 and Visual Studio 2010. Read a lot of rants when it came out, but it seems to be stable and it's relatively fast. Thank you, a hundred times, for beta-testing the software. Windows 7 is not as much a disaster as everybody claimed. Good luck with Win8 and VS2012 :)
BillWoodruff wrote:
I find it rather amazing that at this time of such sophistication in software, there isn't an un-installer program, produced by Microsoft, that can figure out what needs to be done: and "just do it."
There are Virtual Machines available - don't use your primary environment for experiments, it sucks when you have to live in the ruins of a failed experiment.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
Eddie, If your new rig is a monster to you, I think, by gosh, it's monstrous ! Not to worry: Michael is from Oz, where, for males, size really matters (but not as much as beer), and Zac, an American, is an Eagle Scout with all 129 Merit Badges. That should give you a perspective on their comments here :) best, Bill
~ Confused by Windows 8 ? This may help: [^] !
-
Got a new desktop a few weeks ago; a 64-bit monster-machine with 2 Gb of RAM, Windows 7 and Visual Studio 2010. Read a lot of rants when it came out, but it seems to be stable and it's relatively fast. Thank you, a hundred times, for beta-testing the software. Windows 7 is not as much a disaster as everybody claimed. Good luck with Win8 and VS2012 :)
BillWoodruff wrote:
I find it rather amazing that at this time of such sophistication in software, there isn't an un-installer program, produced by Microsoft, that can figure out what needs to be done: and "just do it."
There are Virtual Machines available - don't use your primary environment for experiments, it sucks when you have to live in the ruins of a failed experiment.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
Eddy Vluggen wrote:
monster-machine with 2 Gb of RAM
:(( I didn't even know they sold computers that low-speced nowadays. :rose: Seriously, 16GB of RAM would cost, maybe, $100. My computer from high school, which I graduated from about 10 years ago, had something like 2GB of RAM. There are graphics cards now that come with 3GB of DDR5 RAM. My God, man, you poor soul. :rose: :rose: :rose:
-
This post is made based on the belief that: "suffering shared is suffering diluted" ... which does seem to me to be one modal use of the Lounge :) You have all been in software "hell," I'd bet; if not with Visual Studio, then with an OS issue, or some other issue with an application, or your own code, that, suddenly, begins to malfunction for no apparent reason; an application that won't install, etc., etc. And, I suspect, that you, like me, have tarried long in software hell, because you wanted, at all cost, to avoid the dreaded re-install of the OS, followed by endless upgrading, and endless re-install of all your tools, and programs. I'll spare you the "Google street-level view," which I am exposing, and getting some help with, kind of, on the MS Visual Studio install forum. Here's a high-altitude fly-by view: It started with installing an upgrade to the MindScape dingus (Add In ? Extension ?) to Visual Studio RC 1. Then, the next day, trying to start Visual Studio: it goes into an endless loop presenting a dialog "Loading Components." Only way out: Task Manager: kill devenv.exe. So, what could be more natural, at this time, when MS has a free 90 day trial of Visual Studio 2012 Pro RTM, than to uninstall the RC 1, and install the RTM ? Un-install of RC1 fails with countless issues. Hand editing the Registry to remove all RC1 and FrameWork 4.5RC references, results in the apparent removal of RC1, but then RTM will not install. Endless fiddling with more registry entries, removing selected .NET components: finally RTM installs, but will show, on first launch, when I try to create a Windows Forms solution, a dialog telling me it can't "create the compiler." If I then ignore this dialog, and create a second solution; I end up with a viable solution that will build and run (!), but which will not allow me to access to the Design view, of any Form or UserControl :) I bet you've seen that window with deep blue on top, and a yellow panel top-side, that usually appears when you have done some kind of messing around with the Designer.cs file in a WinForms project. I'd estimate I have now spent nearly twenty hours of my life, over the last five days, unable to use Visual Studio 2012, trying to get the RTM to work, and now trying to get it un-installed. That's major withdrawal syndrome for me, because: using VS is a favorite past-time, and I like to answer QA questions here, checking my answers by coding in 2012, before posting them, to make sure they are correct. Some of the help files I've be
It is and has been known for ages that Windows cannot neither install nor uninstall programs reliably. Nothing to wonder here. All "installers" are just tools to fool "common users" and the real pain is that MS treats developers as such. The sad news is that those without a recent backup deserve that treatment. One must have the OS partition backup and all installers run after it was made handy at all times. If it takes you more than 4 hours to reinstall everything you are not doing that right. Paranoid souls may also use Ashampoo uninstaller or equivalent, this is also necessary if you care about what installers do to your system. This is why healthier communities offer ZIP installers and portable programs. The "guess reading the log" part suggests that either the tech support has been suboptimal or you are not using Windows 7 or newer - you can just order installed software by date in the uninstall dialog there. VS 2012 is not designed for XP. It is also well known that MS does not design software that works. It designs that which works in the most of cases. Nothing new here. Microsoft can do nothing about that since doing something means huge shifts of power and influebce between execs at best, and possibly MS is already free of competent execs. Their errors started ti pile up with the C: drive...
-
I just upgraded my desktop box (Win7 x64) from 4GB to 8GB and the performance shot up - which leads me to conclude that the machine was being slowed down by excessive paging. A dev machine with 2GB RAM will suffer far, far worse. If you're using an x64 OS for development, you really need to be looking at 8GB or more.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
I just upgraded my desktop box (Win7 x64) from 4GB to 8GB and the performance shot up - which leads me to conclude that the machine was being slowed down by excessive paging. A dev machine with 2GB RAM will suffer far, far worse. If you're using an x64 OS for development, you really need to be looking at 8GB or more.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
Anna-Jayne Metcalfe wrote:
I just upgraded my desktop box (Win7 x64) from 4GB to 8GB and the performance shot up
I just had the same with my laptop a week ago. 4GB to 8GB was a big improvement. I shudder to think what 2GB would have been like.
-
This post is made based on the belief that: "suffering shared is suffering diluted" ... which does seem to me to be one modal use of the Lounge :) You have all been in software "hell," I'd bet; if not with Visual Studio, then with an OS issue, or some other issue with an application, or your own code, that, suddenly, begins to malfunction for no apparent reason; an application that won't install, etc., etc. And, I suspect, that you, like me, have tarried long in software hell, because you wanted, at all cost, to avoid the dreaded re-install of the OS, followed by endless upgrading, and endless re-install of all your tools, and programs. I'll spare you the "Google street-level view," which I am exposing, and getting some help with, kind of, on the MS Visual Studio install forum. Here's a high-altitude fly-by view: It started with installing an upgrade to the MindScape dingus (Add In ? Extension ?) to Visual Studio RC 1. Then, the next day, trying to start Visual Studio: it goes into an endless loop presenting a dialog "Loading Components." Only way out: Task Manager: kill devenv.exe. So, what could be more natural, at this time, when MS has a free 90 day trial of Visual Studio 2012 Pro RTM, than to uninstall the RC 1, and install the RTM ? Un-install of RC1 fails with countless issues. Hand editing the Registry to remove all RC1 and FrameWork 4.5RC references, results in the apparent removal of RC1, but then RTM will not install. Endless fiddling with more registry entries, removing selected .NET components: finally RTM installs, but will show, on first launch, when I try to create a Windows Forms solution, a dialog telling me it can't "create the compiler." If I then ignore this dialog, and create a second solution; I end up with a viable solution that will build and run (!), but which will not allow me to access to the Design view, of any Form or UserControl :) I bet you've seen that window with deep blue on top, and a yellow panel top-side, that usually appears when you have done some kind of messing around with the Designer.cs file in a WinForms project. I'd estimate I have now spent nearly twenty hours of my life, over the last five days, unable to use Visual Studio 2012, trying to get the RTM to work, and now trying to get it un-installed. That's major withdrawal syndrome for me, because: using VS is a favorite past-time, and I like to answer QA questions here, checking my answers by coding in 2012, before posting them, to make sure they are correct. Some of the help files I've be
Funny, but not too remarkable given the the diverse nature of software, but I first used VS11 Beta, then upgraded without any problem at all to VS2012 RC, and then to VS2012 RTM, both times without uninstalling the previous version.
-
It is and has been known for ages that Windows cannot neither install nor uninstall programs reliably. Nothing to wonder here. All "installers" are just tools to fool "common users" and the real pain is that MS treats developers as such. The sad news is that those without a recent backup deserve that treatment. One must have the OS partition backup and all installers run after it was made handy at all times. If it takes you more than 4 hours to reinstall everything you are not doing that right. Paranoid souls may also use Ashampoo uninstaller or equivalent, this is also necessary if you care about what installers do to your system. This is why healthier communities offer ZIP installers and portable programs. The "guess reading the log" part suggests that either the tech support has been suboptimal or you are not using Windows 7 or newer - you can just order installed software by date in the uninstall dialog there. VS 2012 is not designed for XP. It is also well known that MS does not design software that works. It designs that which works in the most of cases. Nothing new here. Microsoft can do nothing about that since doing something means huge shifts of power and influebce between execs at best, and possibly MS is already free of competent execs. Their errors started ti pile up with the C: drive...
I am using Win 7, and I think most of what you say above is a complete crock. I may be in "software hell." But, you, seem to be in a totally different kind of "hell," where your sense of humor has been incinerated, all ablaze in an inner bonfire kindled with grudges against Microsoft: to emit such sulfurous fumes, as your words writ here. Do you believe Apple programmers got better dog-food: have never gone through yogic contortions as tools and technologies shifted around them, requiring they re-boot their brains ? I like MS tools, I think Visual Studio is the best IDE ever developed. I have no complaints against the nice people at the MS VS Studio Install Forum trying their best to assist me with resolving the problem. My screed here was delivered tongue-in-cheek; I am not in the hell ... of having ... no ... sense ... of humor :) In reality, there is no "hell," that cannot be escaped from, because, as Werner Heisenberg said, "atoms are not things." Bill
~ Confused by Windows 8 ? This may help: [^] !
-
I am using Win 7, and I think most of what you say above is a complete crock. I may be in "software hell." But, you, seem to be in a totally different kind of "hell," where your sense of humor has been incinerated, all ablaze in an inner bonfire kindled with grudges against Microsoft: to emit such sulfurous fumes, as your words writ here. Do you believe Apple programmers got better dog-food: have never gone through yogic contortions as tools and technologies shifted around them, requiring they re-boot their brains ? I like MS tools, I think Visual Studio is the best IDE ever developed. I have no complaints against the nice people at the MS VS Studio Install Forum trying their best to assist me with resolving the problem. My screed here was delivered tongue-in-cheek; I am not in the hell ... of having ... no ... sense ... of humor :) In reality, there is no "hell," that cannot be escaped from, because, as Werner Heisenberg said, "atoms are not things." Bill
~ Confused by Windows 8 ? This may help: [^] !
You may be right. I am very much against Microsoft. I watch them and have to deal with their projects from the very beginning. Actually I manage to handle their products, but what makes me so anxious is that they break my hopes. Constantly creating new marginally better technologies and abandoning existing ones. Making Windows 8... I do not want to say it is really bad as is, but it might be so much better I cannot think about them calm.
-
Eddy Vluggen wrote:
monster-machine with 2 Gb of RAM
:(( I didn't even know they sold computers that low-speced nowadays. :rose: Seriously, 16GB of RAM would cost, maybe, $100. My computer from high school, which I graduated from about 10 years ago, had something like 2GB of RAM. There are graphics cards now that come with 3GB of DDR5 RAM. My God, man, you poor soul. :rose: :rose: :rose:
AspDotNetDev wrote:
:(( I didn't even know they sold computers that low-speced nowadays. [Rose]
It was a gift, most PC's for sale will have 4 Gb now.
AspDotNetDev wrote:
My computer from high school, which I graduated from about 10 years ago
512k. Yes, half a megabyte - and it ran a multitasking graphical OS.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
I just upgraded my desktop box (Win7 x64) from 4GB to 8GB and the performance shot up - which leads me to conclude that the machine was being slowed down by excessive paging. A dev machine with 2GB RAM will suffer far, far worse. If you're using an x64 OS for development, you really need to be looking at 8GB or more.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
Anna-Jayne Metcalfe wrote:
I just upgraded my desktop box (Win7 x64) from 4GB to 8GB and the performance shot up - which leads me to conclude that the machine was being slowed down by excessive paging.
I usually conclude that I'm running too much crap, which usually is true. After downloading the MVPS-hosts file, disabling a lot of unneeded services, and cleaning the startup-path, everything seems to fly.
Anna-Jayne Metcalfe wrote:
A dev machine with 2GB RAM will suffer far, far worse.
Did I mention I'm coming from a 1Gb laptop running Ubuntu? My last article was written entirely on that machine, including the software :)
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
