+972 52-548-6969
Do you use OSS tools for .Net development?
time to read 4 min | 721 words
Jeremy Millier asks this question here. My answer is obviously YES.
My current project is using:
- Windsor for IoC
- Various Windsor facilities (automatic transaction support)
- Active Record for NHibernate sans XML
- NHibernate for data access
- Castle Validators for validation
- Igloo for MVC support
- log4net for logging, performance tuning, etc.
- NHQG for strongly typed queries
- MbUnit for testing
- Watin to drive IE
- Rhino Mocks for mocking
- Cruise Control.Net
- Tortoise SVN
- Subversion
- NCover
- NCover Explorer
- SQLite
- System.Data.Sqlite
- Boo (for configuration, of all things)
- Rhino Commons set of tools
- MSBuild Community Tasks
- #ZipLib
- Prototype
- +Various other javascript fun stuff
- FireFox
- FireBug
- Notepad2
Proprietary stuff that I am using:
- Windows
- .Net Framework
- ASP.Net Web Froms
- Atlas
- SQL Server
- Internet Explorer
- Web Developer toolbar Beta 3
Update (forgot to metntion these):
- Visual Studio
- ReSharper
- TestDriven.Net
Comments
Jumping on the wagon with Jeremy Miller and Ayende, here. What Open Source Software tools for .NET do...
I use a similar mix of OSS (NHibernate, log4net, SVN, Spring.Net) for productivity, but recently I was talking about the use of OSS libraries with a developer from another team, he raised the problem of finding .Net developers familar with these "non standard" (= non Microsoft) librarys.
Has anybody had a problem hiring developers familar with these technlogies?
@Nicolai
yup, but not only the one familiar with OSS, even the vanilla dev-ers we get on interviews are more applying for an education than a job :(
So.... no using Visual Studio.... are you ?
Interesting is that most people (not you) use OSS as surrounding tools, like NUnit or NAnt, not to create their application core (structuremap, castle).
This shows how people are afraid to commit anything "serious" to OSS. Sad, but likely to change.
Wow you got that to install? Congrats! It hosed two dev boxes here, uninstalled and still got nasty js debug errors in IE. Someone mentioned firebug lite for IE JS debugging which I've been meaning to play with (but only offers a subset of features of something like the toolbar)..
Firebug rocks!. Mayby MS can spend a bit more time on the browser frontend for developer tools for web development.
We're using a subset of the tools you listed, with the hope of investigating more, especially interested in Igloo at the moment, would love to see more of what you do with it Ayende.
To add to the List:
Trac for subversion log tracking and project management.
MooTools for some fancy slideshow javascript
Ajax.Pro - just because we started with that before MS AJAX was born.
GhostDoc - for adding XML comments into code.
@Ernst,
ROTFL.
I know the feeling.
@Asher,
Would you believe that I literally forgot about VS?
Added that, thanks.
@Jason,
I just installed that on all my machines, they are Win2003 + IE7.
When I need to do JS debugging in IE, I am using VS, which has a pretty good debugger for JS.
Personally, I work with FF almost all the time precisely because of FireBug, it is amazing powerful, and so easy to work with.
What do u mean by "Boo (for configuration, of all things)"?
@Reshef,
Take a look at what I am doing with Binsor.
I am going to add it as a template language as well, but that is not happening now.
Comment preview