Forge - DevCon 2017, Darmstadt Germany: Moving to Forge and the Cloud with your existing .NET experience
1 like728 views
This document outlines a class for .NET developers on migrating to Autodesk Forge and cloud technologies, focusing on web development and integration. Key objectives include learning necessary .NET technologies, security practices, and steps for using Forge with existing .NET applications. It also provides a roadmap for transitioning from desktop to hybrid and standalone cloud applications, along with deployment options and further resources.
Forge - DevCon 2017, Darmstadt Germany: Moving to Forge and the Cloud with your existing .NET experience
- 1. © Autodesk, Inc. 2017 Moving to Forge and the Cloud with Your Existing .NET Experience Augusto Goncalves Forge Developer Advocate at Autodesk November, 2017
- 2. © Autodesk, Inc. 2017 Class Summary For over a decade Autodesk improved its .NET APIs for desktop apps. And you, as a developer, learned how to master this technology Now that the Cloud exposes lots of new features and technologies, how to migrate your code and your knowledge? This class will review what you need to refresh your .NET expertise and get ready to leverage Autodesk Forge, Cloud connected apps and web-based apps.
- 3. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 Key Learning Objectives At the end of this class you’ll be able to: § Discover .NET technologies available for web development § Learn about integration with other web-services providers § Learn about the steps necessary to use Forge with .NET § Gain tips and tricks for existing desktop .NET developers
- 4. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 Migration roadmap
- 5. © Autodesk, Inc. 2017 Roadmap Your desktop app as a plugin Desktop app Hybrid (could enabled) Cloud Your app (standalone) Your webapp Fusion plugin (hydrid?) Your app here!
- 6. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 Hybrid apps (cloud connected)
- 7. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 Technologies What we need for this migration • Learning • Security • REST • JSON • Packages • Restsharp • Newtonsoft.Json • Autodesk.Forge
- 8. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 Security • Assembly security • DLLs/EXEs are not secure, eventually get broken • .NET assemblies can be decompiled, do not store sensitive information • Check ConfuserEx tool • Application architecture • Design for security, keep sensitive information on the server • Sensitive information must be encrypted during transfer and storage
- 9. © Autodesk, Inc. 2017 Hybrid architecture Request Response Your cloud app Other cloud providers Your desktop app
- 10. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 Hybrid app demonstration
- 11. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 2-legged scenario Your desktop app Your cloud app Transform metadata into a XLS file Source: github.comAutodesk-Forge/model.derivative-csharp-context.menu
- 12. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 3-legged scenario Your desktop app Your cloud app End-use enter credentials Store access & refresh token, generate UID Check UID and read access token Filter/transform information Store UID Source: github.com/Autodesk-Forge/data.management-csharp-desktop.sample
- 13. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 Cloud app demonstration
- 14. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 Sample app demonstration • 2-legged Live: modelderivative.apphb.com Source: github.com/Autodesk-Forge/model.derivative-WebAPI-sample • 3-legged Live: forgedatamanagement.apphb.com Source: github.com/Autodesk-Forge/data.management-csharp-sample
- 15. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 But what customers want?
- 16. © Autodesk, Inc. 2017 Request Response Your cloud app Other cloud providers Your desktop app Request Response Your browser client Request Response App Your mobile client or app Database Data at the center
- 17. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 What’s next?
- 18. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 Deployment • AppHarbor Easy from Github • Microsoft Azure Super integrated with Visual Studio • AWS Elastic Beanstalk Flexible • Many other .NET hosts…
- 19. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 Further reading • Developer Portal – Documentation developer.autodesk.com • Forge Blog forge.autodesk.com/blog • Samples at Github github.com/Autodesk-Forge
- 20. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 The ugly truth….
- 21. © Autodesk, Inc. 2017© Autodesk, Inc. 2017 • Ask for help • Use well tested packages • Design for security • The cloud brings: • Connectivity • Benefits • Better experience!
- 22. © Autodesk, Inc. 2017 Thank you! augusto.goncalves@autodesk.com augustomaia
- 23. Autodesk and the Autodesk logo are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. © 2017 Autodesk. All rights reserved.
- 24. © Autodesk, Inc. 2017 Resource page API icons Viewer Reality Capture Authentication Model Derivative Data Management Design Automation BIM360 API