Should I start using VS2010 Beta 2 for development work now?
What reasons are there for and against?
+2
A:
Only if you're interested in trying it out. Don't use it for real work as it. It's a beta, which means that significant bugs may still be lying around in the code.
Chris
2009-10-29 22:08:08
do you know of any significant bugs?
Paul Rowland
2009-10-30 00:00:24
http://blogs.msdn.com/kirillosenkov/archive/2009/10/19/visual-studio-2010-beta-2-known-issues.aspx plenty
Jason Short
2009-10-30 21:58:27
+2
A:
We started using VS*2008* Beta 2, when it came out, as our main dev environment - but targeted .NET Framework 2.0 only initially. This was mainly because VS2005 was such a dog. As to whether you want to start targeting .NET 4.0 now is your decision - but I can't see the harm in using it for targeting .NET 2.0 - 3.5.
I think we'll stick with VS 2008 for our main dev environment until at least a 2010-compatible version of CodeRush/Refactor Pro comes out.
Duncan Smart
2009-10-29 22:11:43
+4
A:
You can take two angles with this; using Visual Studio to build your solutions in a .NET 3.5 or earlier OR using it to build applications in .NET 4. Firstly, familiarise yourself with what’s new in both the IDE and the framework (I’ve got a quick, illustrated overview here and there's heaps of other info on the web) and see what you’re actually going to be able to take advantage of in your situation. Secondly, be aware of your target environment; If you’re publishing to shared hosting or client machines you need to consider whether the .NET 4 approach is wise while it's in beta.
I’ve previously built solutions on the last couple of generations of Visual Studio and .NET whilst in beta 2. You’ve got a go-live license so you can actually productionise solutions and both previous generations have been very stable without any significantbugs or changes from beta 2 to alpha versions.
If you can address the issues above, I say go for it!
Troy Hunt
2009-10-29 22:12:31
nice link to whats new in VS2010 and .NET 4.are you using beta 2 for general dev work?
Paul Rowland
2009-11-02 02:51:29
I’m still working through ensuring compatibility with our toolset, namely ReSharper (latest build is good for VS2010), StyleCop (yet to test) and Visual SVN (sounds like compatibility issues but with a simple work around). Once this is sorted my team will likely use it as the primary IDE but still target .NET 3.5 until 4 goes gold. Having said that, I’d be happy to start using 4 now on a project I was confident didn’t need to go into production until after the final release.
Troy Hunt
2009-11-02 20:32:30
A:
I say whats wrong with 2008? You could use 2010 to build for 3.5 framework if you really wanted to, but I'd seriously leave it, it might be more trouble than its worth..who knows?
I have it installed and I've had a play with it and I've even installed resharper beta that works with 2010. But this is only to give the new tools a test run.
The company I work for are really good at keeping up with the latest tools, for example we have already rolled out windows 7 to some developer machines, but we wouldn't go as far as using a beta IDE in a production environment.
Michael Baldry
2009-10-30 00:21:09
"who knows?" - well hopefully some kind soul on stackoverflow will tell me they are using it and its brilliant because of these reasons... or its rubbish because of these reasons...
Paul Rowland
2009-10-30 01:01:36
You won't get that, it's a beta, so no matter how brilliant one person may find it, others may have lots of problems, and the person who thought it was brilliant will probably also come along a bug at some point. Don't treat a beta like a released piece of software.
Michael Baldry
2009-10-30 15:32:45
If you go by most of the information being published on blogs, posted to Stack Overflow or discussed on Twitter, this appears to be a very stable release. I’m yet to hear of any significant problems or negative feedback from people actually using it daily. All indications at this stage are that it’s a very polished product and personally I wouldn’t have any hesitations in using it assuming compatibility with all my tools.
Troy Hunt
2009-11-02 20:36:40