> >2. Integrated environments like VS work better for typical projects.
> >   They may be hard to adapt to unusual requirements. Consider the
> >   basic issue of language choice. What one needs to do to use VS with
> >   a language unknown to VS? How to tell VS about dependencies which
> >   need to be generated by a custom tool?
> 
> not sure, haven't tried this. actually not sure about the rest of ur
> questions, I just wanted to point out that proj files for VC are pretty easy
> to customize.
> 
> Jason.

That's handled easily enough. External Build Tools. Moreover, if you
set the dependencies correctly (they can be hard set too), VS will
rebuild when necessary, even with the unknown code type.

-- 
Christopher A. Watford
christopher.watford@gmail.com
http://dorm.tunkeymicket.com

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners