From: grasp06110 on 12 May 2010 20:24 Hi Everybody, I am in an unfortunate situation where I need to work on a C# project for a while. We are using Visual Studio 2005. The code I need to work on is a C# desktop application with no unit testing what so ever. Is there anyone out there that has made this transition? What are the best bits of advice you can offer someone who is going through it? Specifically, what tools would you recommend for Unit Testing? For an IDE? Am I hopelessly tied to what every my company is willing to pay for wrt what IDE I use? I miss Eclipse more than words can tell. Just goes to show you don't appreciate water until your well runs dry (at least that's what I learned from Etta James). Thanks, John
From: Arved Sandstrom on 12 May 2010 20:53 grasp06110 wrote: > Hi Everybody, > > I am in an unfortunate situation where I need to work on a C# project > for a while. We are using Visual Studio 2005. The code I need to > work on is a C# desktop application with no unit testing what so > ever. > > Is there anyone out there that has made this transition? What are the > best bits of advice you can offer someone who is going through it? > > Specifically, what tools would you recommend for Unit Testing? For an > IDE? Am I hopelessly tied to what every my company is willing to pay > for wrt what IDE I use? I miss Eclipse more than words can tell. > Just goes to show you don't appreciate water until your well runs dry > (at least that's what I learned from Etta James). > > Thanks, > John I don't call it an unfortunate situation when I "have to" work on C#. It's at least as good as Java, certainly not worse, and anyway all of us are professional developers, not dilettantes who get to pick what language we use. I've used Visual Studio Web Developer or Visual C# as IDEs. These are excellent IDEs, and you won't be suffering through the same kind of glitches as you get with Eclipse. As for testing, I've used NUnit, works just fine. If you don't like Visual Studio 2005, exactly how tough is it to Google just a bit and find all the Visual X 2008 Express IDEs? AHS
From: Arne Vajhøj on 12 May 2010 21:17 On 12-05-2010 20:24, grasp06110 wrote: > I am in an unfortunate situation where I need to work on a C# project > for a while. We are using Visual Studio 2005. The code I need to > work on is a C# desktop application with no unit testing what so > ever. > > Is there anyone out there that has made this transition? What are the > best bits of advice you can offer someone who is going through it? > > Specifically, what tools would you recommend for Unit Testing? For an > IDE? Am I hopelessly tied to what every my company is willing to pay > for wrt what IDE I use? I miss Eclipse more than words can tell. Possible IDE's: - Visual Studio (Express Edition is free, the rest cost money) - SharpDevelop (open source, I like it !) - Eclipse with Emonic C# plugin Unit testing: - the one that comes with the expensive versions of VS - NUunit which is a relative direct port of JUnit Other tools that may make you feel at home: - log4net - nant Arne
From: Arne Vajhøj on 12 May 2010 21:17 On 12-05-2010 20:53, Arved Sandstrom wrote: > If you don't like Visual Studio 2005, exactly how tough is it to Google > just a bit and find all the Visual X 2008 Express IDEs? 2010 has been out for approx. a month now. Arne
From: Mike Schilling on 13 May 2010 02:42 Arved Sandstrom wrote: > grasp06110 wrote: >> Hi Everybody, >> >> I am in an unfortunate situation where I need to work on a C# project >> for a while. We are using Visual Studio 2005. The code I need to >> work on is a C# desktop application with no unit testing what so >> ever. >> >> Is there anyone out there that has made this transition? What are >> the best bits of advice you can offer someone who is going through >> it? Specifically, what tools would you recommend for Unit Testing? For >> an IDE? Am I hopelessly tied to what every my company is willing to >> pay for wrt what IDE I use? I miss Eclipse more than words can tell. >> Just goes to show you don't appreciate water until your well runs dry >> (at least that's what I learned from Etta James). >> >> Thanks, >> John > > I don't call it an unfortunate situation when I "have to" work on C#. > It's at least as good as Java, certainly not worse, and anyway all of > us are professional developers, not dilettantes who get to pick what > language we use. > > I've used Visual Studio Web Developer or Visual C# as IDEs. These are > excellent IDEs, and you won't be suffering through the same kind of > glitches as you get with Eclipse. As for testing, I've used NUnit, > works just fine. Is there only one NUnit now? At the time I needed one (back in 2002 or so), there were about four at SourceForge. I picked the one that looked like it had had the most work done on it, and it was fine.
|
Next
|
Last
Pages: 1 2 3 4 5 6 7 Prev: ObjectInputStream over socket problems Next: Hibernate Validator Date |