How is a Java Project Structured (Compared to a Visual Studio C# Project)? -
i'm trying learn project automation , i'm using book pragmatic project automation guide. it's examples in java find easier follow along in java. don't have experience using java or of ides. however, i've learned c# using visual studio (although i'm still beginner).
i'm having trouble understanding parts of setting java project. i'm using netbeans ide 7.0 on windows 7. visual studio, have solution projects underneath. netbeans, appear have project directories determining rest of structure (and ide degree)? equivalent add reference
appears adding source classpath
. there seems degree of separation between compiler , ide. i'm in situation can compile project fine while ide tells me still have errors (and assume because have project set incorrectly).
i'm looking analogies me better understand java project structure.
lots of similarities between 2 languages , ides. spent many years in both. starters equivalent 'add reference' in vs adding library or jar in netbeans. in respect reference - jar pretty same thing module or .dll in vs. jar compiled reference. add reference go project menu , properties libraries menu there can add either pre-assembled netbeans libraries, collections of .jar's, or single .jar, or project. once add reference can import them class in c#.
netbeans doesn't have 'solution' vs does. deal individual projects. have capability add project reference don't have continually re-build references when change between multiple projects. has project groups group similar projects.
lastly apache ant responsible tying in background. netbeans creates build.xml , build-impl.xml file in background tell ant how assemble project .jar.
there other things cover thing answers of questions. help?
Comments
Post a Comment