VS2013 Preview
-
For obvious reasons, I couldn't try the VS2013 preview at work as I'd not be thanked if I checked anything in that might taco the build. A question though: does it enforce a one-way conversion from VS2012 to VS2013? As for the curly brace completion, we get that if you have Resharper installed plus many other useful things. :)
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
Leslie Nielsen 151576 wrote:
does it enforce a one-way conversion from VS2012 to VS2013?
I can open VS2012 solutions in VS2013 without problems, and I can also open VS2013 solutions in VS2012 without problems. I've no idea whether it makes a conversion, but I think it doesn't, because I don't get a 'Conversion' window or something similar.
The quick red ProgramFOX jumps right over the
Lazy<Dog>. My latest article: Understand how bitwise operators work (C# and VB.NET examples) My group: C# Programmers Group -
Leslie Nielsen 151576 wrote:
does it enforce a one-way conversion from VS2012 to VS2013?
I can open VS2012 solutions in VS2013 without problems, and I can also open VS2013 solutions in VS2012 without problems. I've no idea whether it makes a conversion, but I think it doesn't, because I don't get a 'Conversion' window or something similar.
The quick red ProgramFOX jumps right over the
Lazy<Dog>. My latest article: Understand how bitwise operators work (C# and VB.NET examples) My group: C# Programmers GroupThanks for confirming that. That was my experience being able to use the same projects with VS2010 and VS2012.
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
For obvious reasons, I couldn't try the VS2013 preview at work as I'd not be thanked if I checked anything in that might taco the build. A question though: does it enforce a one-way conversion from VS2012 to VS2013? As for the curly brace completion, we get that if you have Resharper installed plus many other useful things. :)
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
Leslie Nielsen 151576 wrote:
As for the curly brace completion, we get that if you have Resharper installed plus many other useful things.
I have Resharper 8 beta installed. They are doing very good things with the product and they have improved the WPF/Xaml support.
Mike.
-
Leslie Nielsen 151576 wrote:
As for the curly brace completion, we get that if you have Resharper installed plus many other useful things.
I have Resharper 8 beta installed. They are doing very good things with the product and they have improved the WPF/Xaml support.
Mike.
Me too. I'm just waiting for its production release which must be due soon. As soon as it does I'll be shelling out the quids to buy it.
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
Leslie Nielsen 151576 wrote:
does it enforce a one-way conversion from VS2012 to VS2013?
I can open VS2012 solutions in VS2013 without problems, and I can also open VS2013 solutions in VS2012 without problems. I've no idea whether it makes a conversion, but I think it doesn't, because I don't get a 'Conversion' window or something similar.
The quick red ProgramFOX jumps right over the
Lazy<Dog>. My latest article: Understand how bitwise operators work (C# and VB.NET examples) My group: C# Programmers Group -
When I purchased VS2012 Pro I was very disappointed to learn that it was in itself a native 32 bit assembly. Microsoft did confirm to me that there were no plans to bring it out as a 64 bit assembly. I know it can build 64 bit apps, but itself only produces output at the speed of a native 32 bit product. My question: Is VS2013 available as a native 64 bit assy or is it still only a clunky 32 bit platform. It will be *very* disappointing if Microsoft's premier IDE only runs on half the power of modern 64 bit hardware. Does anyone know the answer?:confused:
-
Leslie Nielsen 151576 wrote:
does it enforce a one-way conversion from VS2012 to VS2013?
I can open VS2012 solutions in VS2013 without problems, and I can also open VS2013 solutions in VS2012 without problems. I've no idea whether it makes a conversion, but I think it doesn't, because I don't get a 'Conversion' window or something similar.
The quick red ProgramFOX jumps right over the
Lazy<Dog>. My latest article: Understand how bitwise operators work (C# and VB.NET examples) My group: C# Programmers Group -
Looks good, (we still are on VS2008). Most of our projects re-build nearly flawlessly, and we are missing update to 3rd party libraries to finish up the rest.
Nihil obstat
-
Leslie Nielsen 151576 wrote:
does it enforce a one-way conversion from VS2012 to VS2013?
I can open VS2012 solutions in VS2013 without problems, and I can also open VS2013 solutions in VS2012 without problems. I've no idea whether it makes a conversion, but I think it doesn't, because I don't get a 'Conversion' window or something similar.
The quick red ProgramFOX jumps right over the
Lazy<Dog>. My latest article: Understand how bitwise operators work (C# and VB.NET examples) My group: C# Programmers GroupProgramFOX wrote:
I can open VS2012 solutions in VS2013 without problems, and I can also open VS2013 solutions in VS2012 without problems. I've no idea whether it makes a conversion, but I think it doesn't, because I don't get a 'Conversion' window or something similar.
IIRC reading something last week that you need the most recent 2012 update to be fully bi-directionally compatible between the two because the new one added some new odds and ends to the solution/project files.
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
-
When I purchased VS2012 Pro I was very disappointed to learn that it was in itself a native 32 bit assembly. Microsoft did confirm to me that there were no plans to bring it out as a 64 bit assembly. I know it can build 64 bit apps, but itself only produces output at the speed of a native 32 bit product. My question: Is VS2013 available as a native 64 bit assy or is it still only a clunky 32 bit platform. It will be *very* disappointing if Microsoft's premier IDE only runs on half the power of modern 64 bit hardware. Does anyone know the answer?:confused: