A guide to moving from Visual Studio to Eclipse - visual-studio

Is there guide out there that will help me, A .Net developer whose been using Visual studio for some time, get to grips with Eclipse?
Even just a quick guide to eclipse.
Has anyone else made the transition, and if so how did you cope. Any Tips?

Not sure if it will help you, but Eric Sink ran a nice four part series some time ago on his move from VS to Eclipse:
From C# to Java - Part 1
From C# to Java - Part 2
From C# to Java - Part 3
From C# to Java - Part 4

Are you using Vista or XP? If Vista, one tip I will give you is run Eclipse in XP compatibility mode. If you are using XP, this tip can be ignored as it doesn't affect you.
If you do use Vista, take a read of item 2 - Automatic scrolling - in this blog post I wrote.

There is a DZone Refcardz Getting Started with Eclipse (free registration required)

Related

Should I start using VS2010 Beta 2 for development work now?

Should I start using VS2010 Beta 2 for development work now?
What reasons are there for and against?
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!
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.
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.
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.

Other Flex IDEs?

I am an Adobe Flex developer and I am sick of Eclipse. Is there an alternative (free) IDE for Flex? I am aware of Tofino, but I can't get that to work on my MSVS Express editions, and I don't want to buy the whole thing. Help is greatly appreciated.
If you aren't concerned with a visual designer, there is also FlashDevelop.
The current version of IntelliJIDEA 8.1.x supports Flex which is pretty nice (along with debugger for Flex). However, there are some limitations with it but with the next version it has better Flex'ing support including AIR, FlexUNIT, etc...
I personally only used IDEA a couple of time for Flex projects, I prefer TextMate for Ruby and Flex and use FlexBuilder for debugging.
Tofino not work on VS Express Edition, but is an alternative to Eclipse Flex. You don't have much more.
There is Amesthst which is a flex development that runs in Visual Studio. I did not have the best luck in using it, or stuck with eclipse as that was the tool used by the rest of my group.
http://www.sapphiresteel.com/Adobe-Flex-Development-in-Visual
Amethyst runs in the free VS Shell Edition. We released a new beta this week with a visual designer:
http://www.sapphiresteel.com/Amethyst-Beta-6-Adobe-Flex-Visual
Download here:
http://www.sapphiresteel.com/Download-Amethyst-Adobe-Flex-IDE
If you need the VS Shell download the All-in-One installer for our Ruby On Rails IDE. This includes VS Shell and you can install Amethyst into that:
http://www.sapphiresteel.com/spip?page=download
best wishes
Huw

Has anyone ran into any issues developing on Windows 7?

I want to trial Windows 7 but wondered if anyone who has done so already ran into any issues specifically related to development?
i.e. problems with VS2008, SQL Management Studio and SQL Server, MySQL, PHP etc. etc.
Examples from XP -> Vista: in Vista there was a sudden loss of an SMTP server. And there were initially (if I remember correctly) issues with VS2005 with I seem to remember a patch coming out later to remedy.
EDIT: or on the contrary any big advantages or benefits to developing on Windows 7!
I been using windows 7 for a while now.
I been using VS2008, netbeans, tomcat, sql manager studio, mysql etc...
And i actually find it more stable and faster then windows vista.
There aren't many advantages to developing on Windows 7 before it's released. Most development features are a function of the IDE, not the OS. So, you might want to consider instead if you should be developing on Visual Studio 2010 instead of VS2008. Instead, you're more likely to have compatibility issues, although for the most part, Windows 7 is much more compatible with existing software than Vista was when it was in beta.
There could be one advantage to developing for Windows 7 before it's released -- you have a head start in taking advantage of features that competitors haven't yet, giving you an advantage in the market. That's the theory at least. That assumes you're going to develop something that uses a feature only available in Windows 7. That assumes you wouldn't be better off with the larger number of sales you'd get by developing something that works on existing platforms.
The only issue I've encountered so far involves compiling older vanilla C programs with Visual C++. You're usually presented with an error like so:
mt.exe : general error c101008d:
Failed to write the updated manifest
to the resource of file
".\Release\SomeProgram.exe". The
binary is not a valid Windows image.
You have to add an empty resource file to the solution.
More on the issue here.
I've never gotten any of the new audio stack examples working; thus this question. API works, documentation is... a bit lacking at the moment; sure to be fixed by RTM.
Other than that, Windows 7 has been faster than and just as stable as Vista (2 crashes from RTM, 0 crashes after SP1) was for me. Truly, you should be developing on Vista and testing on Windows 7 RC as a general practice with respect to pre-release operating systems; but I think we'll get away with it just fine in this particular case.
My advice would be to not develop on Windows 7. Note that I don't mean you shouldn't target it as a platform, just that you should be doing your development on a stable platform.
I personally won't trust a new release of Windows (or Linux for that matter) until it's been in the wild as a proper product (not release candidate) for many months. For Windows, I tend to wait until the first real service pack plus a month for all the nigglies to be fixed.
For Linux, I'm still using Ubuntu 8.04 LTS, not 8.1, and certainly not the 9 alphas.
Test machines are another matter, you should always have one at the "latest and greatest" level for testing, but I consider the development machine of prime importance, needing a stable platform.
No problems from my end yet, been working on a c# app with visual studio 2008 x64, and php web apps with dreamweaver cs3 and netbeans.
Windows7 seems to be just vista with more bells and wistles and a bit more responsive, not to sure if to much really change "under the hood" so to speak. But I have nothing to back that statement up with...
I've been using Win7 for a couple of months now and never had a problem. I went straight from XP to 7 and the only problems I faced were related to configuring SourceGear Vault to work with IIS7...other than that,it's been all good.
I use VS 2005, VS 2008, SQL Server 2005, Infragistics NetAdvantage, and a couple of third party components.
Although I haven't seen any advantages for the development side of the applications, I'd recommend you to upgrade to Win7 only for the better feel of a complete OS. I mean XP was good, but I really dig Win7.

VB6 Program not working in Windows Me

I have written a program in VB6. When I compile it and send it to my friend, he says it is not working. He (like me) has Windows Me.
Why my programs are not working there? Should he install something or what?
Your friend will need the VB6 runtime files to run any VB6 programs. You can find them on Microsoft's site.
You should be able to generate an installer project. There are a number of dependencies for the VB6 runtime (http://www.microsoft.com/downloads/details.aspx?FamilyID=bf9a24f9-b5c5-48f4-8edd-cdf2d29a79d5)
He should install Microsoft Visual Basic run-time files that all applications created with Visual Basic 6.0 need in order to run.
You can get it from Microsoft's Download Center.
He probably needs the VB runtimes.
But you should look into creating a proper msi installer package for you project.
There is a free one from MS to use with VB6 called the Visual Studio Installer 1.1.
Not much information to go on, if you have more, that would be helpful. I'm just guessing, but, your friend's computer may not have the VB6 runtime installed. If he's willing, he should try installing it and see if that fixes the problem.

Does anybody have experience with Visual Studio 2008 on Windows 7?

Has anyone already tried this, anything particulair that I need to be aware of?
Yep, been running it for a while and I haven't hit any problems yet. Can't say I've use it all day every day, but I've built WPF, WinForms, Web and Console apps with it for testing various things and haven't had any hitches.
I have it on my Dell X1, which is effectively my "NetBook", and it's really pretty rapid. The only glitch I have had at all is some problems with graphics acceleration, but that's down to the Intel driver I'm using being an old XP driver, and it was easily worked around.
I've been running it inside a VM in Parallels Desktop 4 on a MacBook Pro. Absolutely no problems to speak of.
(There's no sound in Windows 7 as virtualized through Parallels, which is a known issue — but not very pertinent to the operation of Visual Studio.)
Jeroen,
I've been unable to install the 2008 Team Developer edition - keep getting a permission error. I was, however, able to insall the 2008 Team Database edition. I normally install both editions, so am kind of bummed about not getting the Developer edition to install. Screenshot of the error is here if you're curious.
No Problem with team edition, but only using it for web projects.
I've been using it at work since RC1 and have not run into any issues. Have developed a WinForms app, a WebForms site and now working on a MVC project.
I have had zero problems running Visual Studio 2008 Pro on 32 bit and 64 bit editions of Windows 7 for full-time C++ development.
If the application you are developing doesn't behave correctly under UAC you may will need to run the IDE as admin otherwise it won't run correctly under debug (this is the applications problem, not Windows 7 or Visual Studios).
Others seem to have problems with access rights/permissions, this should also be fixable by running the IDE as admin (via right click) or more permanently via the compatibility tab in the shortcut properties.
I don't know why this happens, is probably related to their particular user account settings.

Resources