I'm currently considering a big "no no" and jumping over to VS 2010 while it's still in RC... after all, text code is text code, how bad can it "F" things up?
I'm just wondering if anyone is using VS 2010 for their projects? I'm very much interested in the subtle additions as well as the multi-screen support.
I've been using it in a VM and it's been pretty stable and even resharper 5.0 has support for it now so it's as good as fully baked for my liking.
A few things to be careful of are:
the .sln files aren't backwards compatible so it won't be easy to share with other people not using VS2010.
There are a number of plugins that don't yet support VS2010 so if you depend on any third party plugins make sure they work
ASP.NET MVC 2 RC 2 has a bit of funkiness so you should check out this post to make sure you've got all your stars aligned if you're using 2010 and MVC.
As you said first of all it is still in RC. People wouldn't upgrade the current Visual Studio version unless there is a reason for it.
If you are not going to use any of the features in .net 4.0, it is probably not important to switch to Visual Studio 2010.
We are using VS2010RC and TFS2010 for our projects in production.
Works great!!
What I like in VS2010 and use:
Test Manager for recording manual tests in Web, WPF, Windows Forms and soon in Silverlight. AWESOME!
Generating "Coded UI" tests
Hierarchical work items (TFS) finally :-)
What I like in VS2010 but don't use yet:
.NET4 features like: Parallel extensions, dynamic keyword, optional and named parameter
Yes, Multi Monitor support works a bit better, but was fine for me with VS2008 too
Related
I am looking in to using sharpDevelop to develop Windows (.NET) applications over using Visual Studio. I'm just wondering if there are any serious limitations to using SharpDevelop over VS? The price is certainly right and at first glance it seems like a pretty decent IDE. I'm just wondering if it is compatible with VS. I mean if I am collaborating with other developers that are using VS, can we seamlessly pass projects/solutions back and forth and work on them? Just wondering what people's opinions are.
Past year I start using SharpDevelop to develop a large application.
Based on my experience, I can say these are some advantages in using it:
It's faster than Visual Studio; if your project is pretty large, you have to spend less time waiting for the project to compile
It's free
One important disadvantage I've found is the lack of a good refactoring system, in Visual Studio I used Jetbrains Resharper for its great refactoring support.
Now I've returned to use Visual Studio, just for the facilities offered by Resharper.
SharpDevelop 4.0 Beta 4 (as the most current version) is pretty stable as for a Beta. Besides being free it has some pretty features which can be extended via AddIn (a sort of plugin system). A large number of project templates for the most popular languages supporting the .NET Framework. A possible limitation is the support for ASP.NET which still lags behind VS.
Surely you can bet that the top versions of Visual Studio may have some better tools, options, better integration and so on.
Please consider comparing SharpDevelop to the Express Editions of VS. Then it will be obvious that SD is a big win if you don't have to pay. Consider it also as a different product, not only a copy of VS (just not to say 'option X is called here Y, opposed to VS').
This feature by feature comparison list for SharpDevelop vs. VS Express might be helpful.
I'm working on a project that was started using Visual Studio 2010. Although according to a special engine we've created the number of code lines is not very high, the project builds very slowly. I tested sharpdevelop, and it was about an order of magnitude faster!! The only problem we faced was that we could not debug our server and client together, something that VS does like a charm (well, that charm requires some patience), and shows the stack trace of the server, on top of the client, which is very useful.
My suggestion: use sharpdevelop unless you absolutely need a feature it lacks.
SharpDevelop 4.0 Beta does not support the default Visual Studio installer projects. However, since these are going to be deprecated after VS2010 by Microsoft, this is probably not a main issue for you.
For those with experience of VS2008 and VS2010. Are there any areas in which you prefered 2008? Any annoyances with the upgrade?
Any reasons not to upgrade?
I'm coming at this from a Web Dev point of view.
Thanks
I think it depend principally of how you use VS.
If your goal is to continue to use Windows Form without Linq (some people stay with VB6...), VS 2010 don't seems to be a good investment...
But if you use, or plan to use WPF and co., VS 2010 seems to be a good investment for me !
So, i think it's interesting to ask yourself : "Any reason NOT to upgrade to WPF and Linq ?"
About your the fear of change like Office 2003 -> Office 2007
Yes, me too, i feel "dropped to my grandma's level"...
But i feel like that too with the change Windows Form -> WPF.
It's good for me : it's not with the improvement of the candle the the bulb was invented !
Office 2007 is for me a great improvement for the user interface...
But it's just my point of vue.
The main reason to upgrade to Visual Studio 2010 is the .NET Framework's new version 4.0, and all the accompanying tools you can use.
If you don't need this new version now, you can delay the upgrade: that's a reason.
But sooner or later, because we all know that we can't stay behind, we'll have to step forward... This is why all of us are using Visual Studio 2008 instead of Visual Studio 6.0 and build software for Windows 7 instead of Windows 98...
If you're in a team, one person upgrading forces all of your developers to have to upgrade as the Solution files and Project files will be marked as being 2010 format and VS2008 won't read them. One of our developers checked in a project using a 2010 beta and now we can't work on it as we didn't buy 2010 yet :(
I suggest you get VS2010 Express (when it's around) and experiment with it as far as performance goes. It's not quite the same as the full version, but close enough to spot big problems I should think.
With the general public release of Visual Studio 2010 Beta 2 today, this latest version has created a lot of hype and interest.
Indeed, the opinion I've gauged is that VS 2010 has resolved a great deal of the minor flaws left over from previous versions, as well as added some particularly useful new code editor and project development tools (in particular the Premium/Ultimate versions).
My question here is: what are you favourite new features in VS 2010 that have really got you excited? Or similarly, what are the flaws of VS 2008 that you are most glad to have resolved?
There is a wealth of changes in VS 2010, of course, but these are some of the ones that have interested me most (about which I know!).
Integrated support for F# (with multi-targeting for .NET 2.0 - 4.0)/
Much improved WPF designer. The VS 2008 was more than a bit buggy at times.
Great improvements to the code editor, such as call hierarchy viewing.
A decent add-in framework.
A greatly expanded testing framework (now capable of database testing, for example) in Premium/Ultimate.
Project planning and modelling features in Premium/Ultimate.
If I could request one point/feature per post, I think that would be best, so we could vote them individually.
Visual Studio 2010's true Multi-Monitor Support sounds pretty fantastic.
The feature I'm most looking forward to having a decent play with is actually more .net 4 than visual studio. Parallel Extensions looks like it will be very interesting.
The new, clean web.config should make my managers happy.
"Just change the option in the web.config"
"Where is it?"
"Under 'AppSettings.'"
"Ugh ... there's so much junk in that file."
The built in profiler and historical debugger!
The 'Navigate To' window (Ctrl+,) is fantastic. Eclipse has something similar, and I've always thought Visual Studio needed it. Now if they would just add a 'Collapse All' button to the Solution Explorer...
One-click web publishing will be handy.
Favorite feature? Requiring 4 gigs of RAM to run it's bloat.
I liked many features
Deployment
Gated checkin
Parallel Programming
Faster debugging
Separate debugger for x86 and x64
These are just few.... The more you explore VS2010 the more you will get. Try to go through the videos by microsoft.
Thanks,
Sunil Agarwal
I have been using Visual Studio Express versions. I used to use the full Pro VS 2005. I can't figure out what I am missing with the Express version. What benefits will I get if I buy the full version of VS?
Here you go. This link is vs2005 specific rather than the more-recent 2008, but that's the version you asked about.
Some highlights:
No Mobile Device support
No Object Test Bench
No Extensions
No built-in source control support (they should really change this)
No remote debugging
No Office Development support
No 64-bit compiler support
No Visual Studio Package support
No profiler
No SQL Server debugging integration
Limited deployment options
This list is actually quite lengthy, but with the notable exception of source control they are mostly things you might be able to do without as a single developer, if you really have to. Even the source control can be handled by a file-system-only tool like Tortoise.
Obviously if you're building something like a smart phone app or VS extension it's a non-starter, so you'll need to evaluate what you're really doing. Some of the other missing features like object test bench or the profiler can be partially replaced by third-party tools.
Here's a link to a downloadable Visual Studio 2008 Product Comparison Guide from Microsoft.
The full version of Visual studio supports some extra features and tools.
One of the big differences is more debugging options (You can specify break conditions for debugging, unlike the express version). That feature alone is probably worth it.
You can also install 3rd party addons to add extra featues.
No Resharper.
also, you can add addins like VisualSVN and Resharper into pro. You can't into express.
Matze might be right - MS needs the money - 5K people layed off today, and only 4.7b profit! :(
Depends on what you do. Look at the product matrix to see what features you gain with higher SKUs. Testing, Smart Devices, etc may or may not be relevant for you.
This really just requires a bit of Googling.
You can view a comparison of the paid versions here and an overview of the Express versions here
Have a look at this:
http://blogshare.members.winisp.net/docs/VisualStudio2008-ProductComparison-v1.02-Revisions.xps
If you are doign any sort of professional development with Visual Studio you should buy the Standard edition at a bare minimum. Without it you will loose Source Control integration which IMHO is vital absolute must no questions asked must have for professional development.
I used VS2003 for a while, and am currently using VS2008 C# Express.
Personally, I miss the ability to set a conditional breakpoint instead of simply breaking when a line is hit, and the Threads window.
Support for code version systems is a feature that is real essential.
And Microsoft needs your money to go on implementing new, hot stuff.
Could somebody please name a few. I could given time, but this is for somebody else, and I'd also like some community input.
Personally I would say one of the biggest advantages I have found is the product responds quicker i.e. opens faster, compiles and runs projects faster. In my mind why wouldn't you upgrade for this benefit alone.
Because of the environment that I work in I am restricted to .NET 2.0 so have not been able to take advantages of the many other features of multi targeting etc.
However for the ASP.NET work I have done the split view and CSS support is great. Certainly that is the one area I have noticed the biggest functional improvement from VS2005 to VS2008. With CSS you still need to but in the effort to understand it but why not get as much help as possible from the IDE as well.
Overall I have found it to be a very easy transition so I can't think of a reason not to upgrade.
Well, it supports .NET 3.5, which offers a lot of new features - it depends on whether you need them.
Other than that, they improved (also with SP1) the refactoring tool, compile speed, IntelliSense now works great with C# too, and you get the new C# compiler even when writing .NET 2.0 code. Also, ASP.NET designer performance has improved a lot.
In my opinion, even writing mostly .NET 2.0 code, I find it slightly better than 2005.
One big feature is it lets you target different versions of the .NET runtime, depending on the project.
If you're using The Microsoft Unit Testing framework, it's far better in 2008. i.e. it's usable.
Besides the usual support for latest versions of framework and integrated unit testing, i personally find out VS 2008 to be more stable, with better refactoring support and more mature (read stable) product than VS 2005.
I was using VS 2005 since it showed up on the market, until the first release of VS 2008, so i can tell the difference.
Depends on your programming language.
On .net, the built-in support for .net 3.5 is obvious, although this is mainly project templates. However, SP1 adds .net Client Framework support, which is not possible within VS2005 to my knowledge.
This also means support for WPF with a XAML Designer, although most people still prefer Expression Blend for WPF Interfaces.
Apparantly, there is now a JavaScript Debugger, even though it's a bit broken as it seems (not sure if SP1 fixes this)
In short: For .net 3.5, it's almost a must-have if you are a professional developer, but that is just my opinion.
The CSS property builder is much better IMHO.