Uninstall VS2012
-
My problem with that approach is I can never remember which order to install VS and SQL in - and I know that when I get it wrong, it mucks everything up and I have to start again...:mad:
The only instant messaging I do involves my middle finger. English doesn't borrow from other languages. English follows other languages down dark alleys, knocks them over and goes through their pockets for loose grammar.
OriginalGriff wrote:
order to install VS and SQL
I'd like to have a separate box for the database server and keep them off my development system entirely. Maybe some day.
-
So now that a few of the die hards have probably been running with VS2013 for a while now and have been running the final release since it became available last week, is it in you opinion safe to uninstall VS2012? Or is there something fundamentally broken that says "no hang onto VS2012 that bit longer"? (I'm talking about PRO versions if that makes any difference). Cheers,
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Why uninstall it. I have all 2005-2008-2010-2012-2013 installed on same machine side-by-side. I think you have to ask yourself "should I install 2013?", in first place. 2013 has very few new things (for sure it's not a new version worth a whole number). I found two features useful: 1. Inline editing of referenced type (if it's in your code) - it nice but not a must have 2. 64 bit edit and continue (which is only good if you in win development) After playing around with it an reading about it I can tell you two main differences: 1. If you want the new framework you must have a new VS (it's not new, we saw it at every VS-.NET version) 2. MSBuild no more part of .NET framework (so the only way to build is use VS!) I have 20 years of experience with Microsoft - and the last 3 years I'm concerned about the way...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
-
So now that a few of the die hards have probably been running with VS2013 for a while now and have been running the final release since it became available last week, is it in you opinion safe to uninstall VS2012? Or is there something fundamentally broken that says "no hang onto VS2012 that bit longer"? (I'm talking about PRO versions if that makes any difference). Cheers,
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Stick each in their own VM. Sorted.
speramus in juniperus
-
Why uninstall it. I have all 2005-2008-2010-2012-2013 installed on same machine side-by-side. I think you have to ask yourself "should I install 2013?", in first place. 2013 has very few new things (for sure it's not a new version worth a whole number). I found two features useful: 1. Inline editing of referenced type (if it's in your code) - it nice but not a must have 2. 64 bit edit and continue (which is only good if you in win development) After playing around with it an reading about it I can tell you two main differences: 1. If you want the new framework you must have a new VS (it's not new, we saw it at every VS-.NET version) 2. MSBuild no more part of .NET framework (so the only way to build is use VS!) I have 20 years of experience with Microsoft - and the last 3 years I'm concerned about the way...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
Please correct me if I'm wrong but MSBuild available as a separate download[^] Microsoft .NET Framework 4.5.1 Developer Pack[^] allows developing for .net 4.5.1 in VS2012
-
Please correct me if I'm wrong but MSBuild available as a separate download[^] Microsoft .NET Framework 4.5.1 Developer Pack[^] allows developing for .net 4.5.1 in VS2012
You just right... I'm talking about a bad feeling... It's bothers me how Microsoft handles us (developers)... You see I had lot of chats with Microsoft's support persons according bugs, and that too add to this bad feeling. It's maybe because I had too much Microsoft in 20 years...:~
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
-
Nothing is ever really uninstalled. Don't bother trying.
-
I really like the delegating constructors and default template arguments. The variadic templates may come in useful. Apparently there are some speed improvements; hopefully intellisense is one of them.
Joe Woodbury wrote:
hopefully intellisense is one of them
Microsoft has been promising improvements in Intellisense for C++ developers since Visual C++ 6.0. I haven't seen any yet from the lying fucks.
Software Zen:
delete this; -
So now that a few of the die hards have probably been running with VS2013 for a while now and have been running the final release since it became available last week, is it in you opinion safe to uninstall VS2012? Or is there something fundamentally broken that says "no hang onto VS2012 that bit longer"? (I'm talking about PRO versions if that makes any difference). Cheers,
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
I need to convince the bean counters to buy me a Resharper upgrade first. :sigh:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
I've just been reading about 'what's new in VS2013'. The only thing that caught my imagination is edit-and-continue in 64 bit. Is it worth upgrading?
Regards, Rob Philpott.
The improved lazy loading of solutions looks promising. http://blogs.msdn.com/b/visualstudio/archive/2013/10/14/asynchronous-solution-load-performance-improvements-in-visual-studio-2013.aspx[^]
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
Why uninstall it. I have all 2005-2008-2010-2012-2013 installed on same machine side-by-side. I think you have to ask yourself "should I install 2013?", in first place. 2013 has very few new things (for sure it's not a new version worth a whole number). I found two features useful: 1. Inline editing of referenced type (if it's in your code) - it nice but not a must have 2. 64 bit edit and continue (which is only good if you in win development) After playing around with it an reading about it I can tell you two main differences: 1. If you want the new framework you must have a new VS (it's not new, we saw it at every VS-.NET version) 2. MSBuild no more part of .NET framework (so the only way to build is use VS!) I have 20 years of experience with Microsoft - and the last 3 years I'm concerned about the way...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
Kornfeld Eliyahu Peter wrote:
Why uninstall it. I have all 2005-2008-2010-2012-2013 installed on same machine side-by-side.
I'm diskspace limited, and junk old versions whenever everything I had to support them for is updated to the newest version. Currently got 2003-2008-2010-2012 installed; and I'm hoping to get the last major 2003 project (finally) updated later this year. Hopefully I'll be able to boot 2008 within a year too.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
So now that a few of the die hards have probably been running with VS2013 for a while now and have been running the final release since it became available last week, is it in you opinion safe to uninstall VS2012? Or is there something fundamentally broken that says "no hang onto VS2012 that bit longer"? (I'm talking about PRO versions if that makes any difference). Cheers,
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
I am really looking forward to the AngularJS intellisense built into 2013.
Eric
-
So now that a few of the die hards have probably been running with VS2013 for a while now and have been running the final release since it became available last week, is it in you opinion safe to uninstall VS2012? Or is there something fundamentally broken that says "no hang onto VS2012 that bit longer"? (I'm talking about PRO versions if that makes any difference). Cheers,
Dave Find Me On: Web|Facebook|Twitter|LinkedIn
Folding Stats: Team CodeProject
Installed it this morning absolute disaster! Even trying to create the most basic MFC program (just the Wizard project output) ends up with a stack of errors. Looks as though testing must be virtually non-existent for native code. 2012 was fine Seems to be pulling out 2010 include - fixable but a real mess! Microsoft the company that likes to disappoint.....
-
Kornfeld Eliyahu Peter wrote:
Why uninstall it. I have all 2005-2008-2010-2012-2013 installed on same machine side-by-side.
I'm diskspace limited, and junk old versions whenever everything I had to support them for is updated to the newest version. Currently got 2003-2008-2010-2012 installed; and I'm hoping to get the last major 2003 project (finally) updated later this year. Hopefully I'll be able to boot 2008 within a year too.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
IMO VS2013 is not less stable than 2012...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
-
IMO VS2013 is not less stable than 2012...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
Was this intended as a reply to me? I don't see how anything I wrote could be read as a comment on stability.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
Was this intended as a reply to me? I don't see how anything I wrote could be read as a comment on stability.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
It's late afternoon here...:~
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
-
It's late afternoon here...:~
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
:beer: o'clock? Enjoy, it's only 10 in the morning here. :sigh:
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
Yes, uninstall VS2012 and go back to VS2010, you'll be a lot happier.
- I would love to change the world, but they won’t give me the source code.
-
I am really looking forward to the AngularJS intellisense built into 2013.
Eric
-
Stick each in their own VM. Sorted.
speramus in juniperus
-
Why uninstall it. I have all 2005-2008-2010-2012-2013 installed on same machine side-by-side. I think you have to ask yourself "should I install 2013?", in first place. 2013 has very few new things (for sure it's not a new version worth a whole number). I found two features useful: 1. Inline editing of referenced type (if it's in your code) - it nice but not a must have 2. 64 bit edit and continue (which is only good if you in win development) After playing around with it an reading about it I can tell you two main differences: 1. If you want the new framework you must have a new VS (it's not new, we saw it at every VS-.NET version) 2. MSBuild no more part of .NET framework (so the only way to build is use VS!) I have 20 years of experience with Microsoft - and the last 3 years I'm concerned about the way...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is (V).
