Flexible Project Setup for Teams and Complicated DNN Applications
•
1 recomendación•13,945 vistas
During my years consulting and then into my time training large companies at DNN Corp, I kept getting a common question, “how do I do this with large/enterprise teams?” It’s way too easy to try and walk them through doing all of the hard work of trying work around the single-developer project architecture that you’re used to seeing in videos and wiki articles – but that’s not the answer they’re looking for. If you have a complicated project and/or a team of 2 or more people working on code that’s all supposed to work together, there has to be a far simpler solution – and there is!
Recomendados
Recomendados
Más contenido relacionado
Destacado
Destacado (11)
Más de Will Strohl
Más de Will Strohl (20)
Último
Último (20)
Flexible Project Setup for Teams and Complicated DNN Applications
- 1. FLEXIBLE PROJECT SET-UP FOR TEAMS AND COMPLICATED APPLICATIONS Will Strohl @WillStrohl Don’t forget to include #DNNCon in your tweets! @WillStrohl
- 2. Don’t forget to include #DNNCon in your tweets! @WillStrohl Will Strohl @WillStrohl Director, Product Development @ Author, founder of DNNCon, former ODUG President, 20+ OSS projects, former DNN Corp employee
- 3. Your website has multiple solutions/projects. The project has 2 or more people. You need to share code across projects. You want to automate processes. Don’t forget to include #DNNCon in your tweets! @WillStrohl Who?
- 4. “How can we develop on DNN as a team?” Don’t forget to include #DNNCon in your tweets! @WillStrohl Why?
- 5. • Multiple extension types • External references • Source control mapping • Multiple projects/project types • Team environments • Builds/packaging • External processes Don’t forget to include #DNNCon in your tweets! @WillStrohl Challenges
- 6. DesktopModules vs. Build Out of Site Don’t forget to include #DNNCon in your tweets! @WillStrohl Methods
- 7. Desktop Modules Pros Cons • Easy to start • Existing videos, wikis, blogs • Visual Studio templates • Great for 1-off’s • WSP-friendly • Difficult to map in source control • Multiple Visual Studio projects • Check-in the website • Difficult to share code Don’t forget to include #DNNCon in your tweets! @WillStrohl
- 8. Desktop Modules Don’t forget to include #DNNCon in your tweets! @WillStrohl
- 9. Build Out of Website Pros Cons • All projects in single solution • Build against multiple dependencies • Process integration • Build all once • Doesn’t follow community examples • Not good for POCs • Not good for single projects Don’t forget to include #DNNCon in your tweets! @WillStrohl
- 10. Build Out of Website Don’t forget to include #DNNCon in your tweets! @WillStrohl
- 11. Demonstration See it in action! Don’t forget to include #DNNCon in your tweets! @WillStrohl
- 12. DesktopModules Build Folders • Quick and easy • Ready-to-use Visual Studio templates • Follows wiki/videos • WSP-friendly Don’t forget to include #DNNCon in your tweets! @WillStrohl Summary • Single solution • Source control • Don’t check-in websites • Dependencies • Build all at once • Shared libraries
- 13. THANKS TO ALL OF OUR GENEROUS SPONSORS! Don’t forget to include #DNNCon in your tweets! @WillStrohl
Notas del editor
- 13+ years consulting & training Talk about my experiences with going onsite for Training Consulting
- Project types = class libraries External processes = continuous integration, etc.