RE: http://www.jfrog.com/confluence/display/RTF/Repository+Layouts
The default Artifact Path for a Maven II repo is [orgPath]/[module]/[baseRev](-[folderItegRev])/[module]-[baseRev](-[fileItegRev])(-[classifier]).[ext] What are people using for .NET stuff? Are you creating two repos as you would for Maven, one SNAPSHOT one RELEASE? How you automatically resolving dependencies at build time? Where in your project are you specifying Artifactory links (NuGet or otherwise)? Any other .NET tips? -- View this message in context: http://forums.jfrog.org/How-to-NET-in-Artifactory-tp7579689.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
