17008 VCS Subversion Version Control System

Size: px

Start display at page:

Download "17008 VCS Subversion Version Control System"

Ashley Carter
5 years ago
Views:

17008 VCS Subversion Version Control System 2013 Microchip

2 Class Objectives At the end of this class you will be able to: Understand why a Version Control System is used Know basic features of Subversion Use Subversion using TortoiseSVN Use Subversion within MPLAB X IDE 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 2

3 Class Agenda What is Subversion? Fundamental Concepts Managing a Repository using TortoiseSVN Subversion Client Terminology and Basic Usage Subversion inside MPLAB X IDE 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 3

5 What is a VCS? (Version Control System) A system that manages and tracks changes to a collection of data over time. Also called a: Revision Control System Source Control System 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 5

6 Why do you need a VCS? How many times have you wanted to: Go back in time in your development? Track changes made in time? Collaborate with your team on a project? Restore deleted or previous versions of a file? Separate releases from the workflow? Work on a feature separately and reintegrate when finished? 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 6

8 Using a VCS allows you to: Backup and Restore Need a file saved on Feb 15, 2012 Track changes Log what was changed and why Determine who made a change Prevent blamestorming Collaborate on a Project Be up to date with team progress 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 8

9 Using a VCS helps you fix: Bug introduced in the past Investigate what changes were made at a specific point in time Break your project Discard your changes and get back to the last working version New feature or concept Work on new features or concept in an isolated workspace without disrupting team work flow 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 9

11 Why Subversion? Cross platform support Windows Linux Mac OSx Widely used and supported Most GUIs are free Managed by Apache Software Foundation Free to use 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 11

12 Subversion Components Subversion server & client Command line interface (cli) Subversion GUIs TortoiseSVN - Windows RapidSVN - Windows, Linux, MacOS Native Application Support Built in support for SVN interface 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 12

13 Summary Why do you need a VCS? Source Control Management Version Management Team Collaboration Why use Subversion? Tools and Application Integration Free to use 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 13

15 The Repository The database where the files, folders, history are stored is called Repository Looks like a file server that keeps track of contents history Tracks changes 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 15

16 Revision The snapshot of the file system tree after changes have been published is called Revision. NOTE: SVN revision numbers apply to entire tree 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 16

18 Addressing the Repository svn svn://myserver.com/repos svn+ssh same as svn, but through an ssh tunnel svn+ssh://myserver.com/repos 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 18

content or changes to the repository 2013 Microchip

19 Update and Commit Update Process of getting content or changes from the repository Commit - Process of sending content or changes to the repository 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 19

20 Working Copy a local copy of a particular version of a user's VCS-managed data upon which that user is free to work. [svn book] Working copies appear to other software just as any other local directory full of files and folders Microchip Technology Incorporated. All Rights Reserved VCS Slide 20

21 How the Working Copy works? For each file Subversion records working revision timestamp Change indication Unchanged, and current Locally changed, and current Unchanged, and out of date Locally changed, and out of date 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 21

22 How the Working Copy works?.svn folder special administrative directory used to manage the working copy v1.7 - only in the topmost folder prior to v1.7 - subfolders also It is not recommended to delete or change anything in the.svn folders Microchip Technology Incorporated. All Rights Reserved VCS Slide 22

TortoiseSVN Server admin GUI Client GUI Windows Application Integrated into Windows Explorer

27 Creating a Repository Create a new folder to be used for your repository Right click on it Use Create repository here option in TortoiseSVN 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 27

28 Creating a Repository - result - Recommended Folder Structure can be created (trunk, branches, tags) Repository can be browsed 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 28

29 View the Repository Right click on your repository folder Click on Repo-browser option from the TortoiseSVN menu A special file browser will open (next slide) 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 29

View the Repository - result - Revision Number (HEAD = current revision number) Repository URL

View Change Notes Right click on the item you want to see the log for Then choose the Show

32 View Change Notes Search Filters Results of search (revision number) The message set when changes have been applied Modified content Option to see statistics 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 32

33 View Statistics Statistics can be drawn from the repository browser How many changes per user How many changes per day How many changed files Percents per author Graphs 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 33

34 Repository Folder Structure trunk development line branches a copy of development line tags stable snapshot of a development line (releases) 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 34

35 Branches One or many copies of the development line Changes can be made to all copies Exists independently of another line Shares a common history 1 st Branch 3 rd Branch M Original Line of Development M time 2 nd Branch 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 35

38 Command Line Interface Easy to integrate into any application Programs: svn the command-line client program svnadmin the command-line admin program svnversion status reporting tool other tools svnlook, mod_dav_svn, svnserve etc 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 38

39 Getting Data into Repository - import - $ svn import [PATH] URL doesn't require a working copy files are immediately sent to the repository used to begin tracking with Subversion After the import is finished, the original local directory is not converted into a working copy. To work on that data in a versioned way, you still need to create a fresh working copy of that tree Microchip Technology Incorporated. All Rights Reserved VCS Slide 39

TortoiseSVN Import URL of Repository Log message for import 2013

41 Creating a Working Copy - checkout (co) - $ svn checkout URL[@REV]... [PATH] creates a working copy of the URL directory on your local machine from last revision (HEAD) optional: you can specify what revision you want to checkout (-r <rev_number>) Any file manipulation of versioned files inside the working copy (copy, move, rename, delete) has to be done using the Subversion client Microchip Technology Incorporated. All Rights Reserved VCS Slide 41

TortoiseSVN Checkout Repo Address Working Copy Location Revision to Checkout

Command-Line Checkout Command Repo Address Working Copy Location Revision

44 Updating the Working Copy - update (up) - $ svn update [@REV] [PATH...] updates the working copy to the last revision, unless specified - for out-of-date files, Subversion will not allow any changes to repository, you will have to update first - update your working copy before any attempt to send the changes you made to the repository 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 44

Command-Line Update Command Desired Revision Number Updated Added 2013

47 Reviewing Changes - status (st) - $ svn status [FOO...] gets an overview of changes to the Working Copy or to the files of your choice 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 47

TortoiseSVN Status 2013 Microchip Technology

Command-Line Status Unversioned item Modified item Deleted item Added item

scheduled to be added to the repo; some GUIs handle folder contents to be added/skipped

50 Working Copy Content Change - add - $ svn add FOO schedules a file, folder or symbolic link to be added to repo on next submit If FOO is a folder, all its contents will be scheduled to be added to the repo; some GUIs handle folder contents to be added/skipped when add is called Microchip Technology Incorporated. All Rights Reserved VCS Slide 50

TortoiseSVN Add Folder Folder to be added Files inside the folder File that will not

Command-Line Add Folder Command Item to be added Added folder Added folder

53 Working Copy Content Change - delete (del) / remove (rm) - $ svn delete FOO... schedules a file, folder or symbolic link to be removed from the Repository on next commit - files and symbolic links (for some GUIs, folders also) will be deleted from the Working Copy before submit to Repository - after submitting the changes, FOO will be entirely removed from your Working Copy and the Repository 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 53

54 Working Copy Content Change - copy (cp) - $ svn copy SRC[@REV]... DST Copy one or more files in a Working Copy or in the Repository: WC WC; WC URL URL WC; URL URL TortoiseSVN - right click on the item and drag to open copy/move dialog 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 54

55 Working Copy Content Change - move (mv) - $ svn move SRC DST moves files or directories in your working copy or in the repository: WC WC URL URL Used to rename items TortoiseSVN - right click on the item and drag to open copy/move dialog 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 55

56 Reviewing Changes - diff - $ svn diff [FOO...] [-r<revision_start>:<revision_end>] displays differences in file content against the working copy revision if needed, the diff tool can display the differences between 2 desired revisions 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 56

TortoiseSVN diff Unchanged lines Modified lines Inserted line 2013

Command-Line diff Unified diff format output 2013 Microchip

59 Undoing Changes - revert - $ svn revert PATH... undo all local edits reverts the file(s) to its pre-modified state from local svn cache area can be used to restore unsubmitted deleted files Revert is inherently dangerous, since its entire purpose is to throw away data - namely, your uncommitted changes. Once you've reverted, Subversion provides no way to get back those uncommitted changes Microchip Technology Incorporated. All Rights Reserved VCS Slide 59

60 Conflicts Happen when updating the Working Copy, inside the Working Copy Occurs when same line of same file has been changed in both sides (Working Copy & Repo) Needs human decision on what to keep Three unversioned files produced: FOO.mine, FOO.rX, FOO.rY Gets solved using svn resolve command Conflict cannot be committed before resolve 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 60

61 Conflicts - merging by hand - Because cannot be automated - needs human decision Intimidating the first time you attempt it Practice => makes it easy An effort for you and the team member that modified the same line(s) you did An example will follow next slides 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 61

62 Conflicts - example - Working Copy checkout sandwich.txt (rev. 3) Top piece of bread Mayonnaise Lettuce Tomato Provolone Creole Mustard Bottom piece of bread Working Copy changed sandwich.txt Top piece of bread Mayonnaise Lettuce Tomato Provolone Salami Mozzarella Prosciutto Creole Mustard Bottom piece of bread Repository changed sandwich.txt (rev. 4) Top piece of bread Mayonnaise Lettuce Tomato Provolone Sauerkraut Grilled Chicken Creole Mustard Bottom piece of bread 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 62

63 Working Copy updated sandwich.txt Conflicts - example - Top piece of bread Mayonnaise Lettuce Tomato Provolone <<<<<<<.mine Salami Mozzarella Prosciutto ======= Sauerkraut Grilled Chicken >>>>>>>.r31 Creole Mustard Bottom piece of bread Unchanged lines Conflicting lines mine Conflicting lines revision Microchip Technology Incorporated. All Rights Reserved VCS Slide 63

Conflicts - example - TortoiseSVN has conflict

65 Conflicts - example - Command line conflict resolution Accept the changes you made $ svn resolve --accept mine-full sandwich.txt Accept the changes from repository $ svn resolve --accept theirs-full sandwich.txt Do not accept any changes - go back to revision before the two edits $ svn resolve --accept base sandwich.txt Conflict has been resolved manually $ svn resolve sandwich.txt 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 65

66 Submit Changes to repo - commit - $ svn commit [PATH...] [-m <message> ] Your edits are finished You've merged all changes from the server So you're ready to commit your changes to the repository Add a meaningful message to your commit 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 66

TortoiseSVN Commit 2013 Microchip Technology

69 Subversion and MPLAB X IDE Subversion is plug-in available inside MPLAB X IDE Allows you to interact directly with the repository from within the IDE Uses the same cli as TorotoiseSVN and other GUI tools MPLAB X IDE currently only supports SVN client <v Microchip Technology Incorporated. All Rights Reserved VCS Slide 69

70 Subversion Interface Menus MPLAB X IDE Team Menu Complete list of options Subversion Pane Commonly used options Shows versioning information Project Pane Right Click Menu Commonly used options 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 70

71 MPLAB X IDE Team Menu Contains complete list of commands used to interface with the SVN repository Contains higher level commands such as checkout as well as commands for tagging, branching and switching 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 71

72 Subversion Pane Shows a quick status of files under version control Filter and sort options dependent on version status Allows you to perform most commonly used actions 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 72

73 Project Pane Right Click Menu Right click on a single file in the Project pane Actions operate on a single file Used for quick access to most commonly used actions 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 73

74 Check Out a Project Checks out contents of a project from a repository to your local working copy Specify the Repository URL Option for checking out a specific revision of the project Only on Team Menu 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 74

75 Check Out a Project Specify folders and revision of the project you want to checkout Specify local folder to checkout project into 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 75

76 Adding Files By default, any file/folder created and added to a project will be automatically added and committed at the next Commit All action You can override this using the Exclude from Commit command 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 76

77 Updating and Committing Update and/or Commit via the Team menu or Subversion pane Right click on a file in the Project pane for actions for a single file 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 77

78 Update Updating occurs in the background Update status can be seen in the Versioning Pane as well as the Output Pane Progress bar in the lower status bar indicates update completion 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 78

79 Commit Commits local changes to the repository Type in a Commit Message describing the change Select files that you want to commit 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 79

80 Output Panes Versioning Output Pane Displays files that have been updated and their status General Output Pane Displays a detailed report of the last update or commit action Displays the cli used in the last action 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 80

81 Change Indicators Project pane shows colored text for files depending on revision status Hovering over the file will popup a message that indicates the revision status of the file Not Modified (black) Locally Modified (blue) Locally New (green) 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 81

Change Indicators The editor window indicates the revision status of lines of code with colored bars Hovering over the colored bar will indicate the nature of the change Right clicking on the

82 Change Indicators The editor window indicates the revision status of lines of code with colored bars Hovering over the colored bar will indicate the nature of the change Right clicking on the colored bar will give you options to view next change as well as open the diff window Line Added Line Changed Line Deleted 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 82

Show Annotation Shows revision level annotations in your source file Shows author that modified file, author is the PC user name Right click for options to diff

83 Show Annotation Shows revision level annotations in your source file Shows author that modified file, author is the PC user name Right click for options to diff with the revision or to revert to the revision Revision Level Author (User Name) 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 83

85 Class Summary Today we covered: Why we need a VCS VCS Terminology Subversion Client basic usage Using Subversion from MPLAB X IDE 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 85

87 Appendix A Subversion Terminology Subversion Client Software run by a user to access a Subversion repository locally or on a Subversion server. Subversion Repository Location where project files are stored. Contains the most recent version as well as past versions of the project. Project Tree Trunk Branch Tag Revision Head A single project tree contains folders for project management and version control. Typical folders are: trunk, branches, tags. These folders are used to keep the working copy, development copy, and code releases or snapshots. Contains of the main project source for team development. Consist of code that can compile, even if it contains stubs for undeveloped code. Split from the main trunk to allow for development. Branches allow development without disrupting the trunk. Branches can remain a separate development path or can be merged back to the trunk later in time. Snapshot of project at an important point of time. Typically a software release version. Stored change in a file's state. Revisions are incremented during the commit process where changes are saved. Latest revision of all project files in the project trunk, branch, or tag. Working Copy Local copy of a projects source code checked out from the repository Microchip Technology Incorporated. All Rights Reserved VCS Slide 87

88 Appendix A Subversion Terminology Check-out Export Update Commit Revert Merge Conflict Creates a local working copy for development, testing, or release. Can be the project head, a specific revision, or a tag of the project. Export a clean directory tree Merges any changes that have been made in the repository into the local working copy. Checking in or writing any project changes from the local copy to the repository. Process of changing a file back to a previous version of itself. Can be used to resolve conflicts. Process of combining the changes made in a working copy of a file in a project to the repository that contains a more recent revision of the same file than what was checked out before modifying it. Typically used in when multiple developers are working on the same file to avoid loosing other developers changes. Occurs when changes are made by different developers to the same file and the repository system is unable to reconcile the changes. Typically requires the files to be merged manually to resolve the conflict Microchip Technology Incorporated. All Rights Reserved VCS Slide 88

89 Appendix B Additional Resources Apache Subversion Page CollabNet Subversion Edge (SVN Server) SVN Server installation w/ frontend TortoiseSVN MPLAB X IDE & Subversion - wikidot Microchip Technology Incorporated. All Rights Reserved VCS Slide 89

90 Appendix B Additional Resources Subversion Manual TortoiseSVN Manual html NetBeans Subversion Manual A Visual Guide to Version Control Revision Control Wikipedia Microchip Technology Incorporated. All Rights Reserved VCS Slide 90

93 Branches One or many copies of the development line Changes can be made to all copies Exists independently of another line Shares a common history 1 st Branch 3 rd Branch M Original Line of Development M time 2 nd Branch 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 93

95 Handling Releases Releasing version 1.00 Make a branch for version 1.00 For this branch, do a tag, e.g Bugs found, correct them in branch 1.00 (do not forget trunk also) Release version by making a copy of debugged branch Microchip Technology Incorporated. All Rights Reserved VCS Slide 95

96 Handling Releases Release Tag v Release Tag v Release Tag v Release Tag v Release v1.00 Branch Release v1.10 Branch Release Tag v Release Tag v Release Tag v Original Line of Development time 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 96

Exporting Files From Repo or Working Copy $ svn export [-r <rev_num>] URL [PATH] $ svn export [-r <rev_num>] PATH [PATH] Export a clean directory tree Mainly used to distribute the project files

97 Exporting Files From Repo or Working Copy $ svn export [-r <rev_num>] URL [PATH] $ svn export [-r <rev_num>] PATH [PATH] Export a clean directory tree Mainly used to distribute the project files without versioning information When exporting files from an Working Copy, all local changes will be preserved; files not under version control will not be copied; useful when a support bug report needs the project files Microchip Technology Incorporated. All Rights Reserved VCS Slide 97

Switching Projects - switch - $ svn switch [-r <rev_num>] URL [PATH] Switches Working Copy contents to a specific revision number in the trunk, branch, or tag Updates the

98 Switching Projects - switch - $ svn switch [-r <rev_num>] URL [PATH] Switches Working Copy contents to a specific revision number in the trunk, branch, or tag Updates the Working Copies URL Prior to svn version 1.7, also used to relocate project (option --relocate) 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 98

Repository URL Changed - relocate - updates the Working Copy to point to a different repository root URL Confusion between svn switch and svn relocate?

99 Repository URL Changed - relocate - updates the Working Copy to point to a different repository root URL Confusion between svn switch and svn relocate? If the working copy needs to reflect a new directory within the repository, use svn switch. If the working copy still reflects the same repository directory, but the location of the repository itself has changed, use svn relocate Microchip Technology Incorporated. All Rights Reserved VCS Slide 99

Appendix E MPLAB X IDE currently does not support SVN v1.7 or v1.8 Support is expected near end of 2013 Running multiple versions of SVN Install SVN v1.

100 Appendix E MPLAB X IDE currently does not support SVN v1.7 or v1.8 Support is expected near end of 2013 Running multiple versions of SVN Install SVN v1.6 or earlier to sub directory Create your repository with v1.6 or earlier server utility Direct MPLAB X IDE to use client <v1.6 Tools/Options Misc/Versioning/Subversion 2013 Microchip Technology Incorporated. All Rights Reserved VCS Slide 100

101 LEGAL NOTICE SOFTWARE: You may use Microchip software exclusively with Microchip products. Further, use of Microchip software is subject to the copyright notices, disclaimers, and any license terms accompanying such software, whether set forth at the install of each program or posted in a header or text file. Notwithstanding the above, certain components of software offered by Microchip and 3 rd parties may be covered by open source software licenses which include licenses that require that the distributor make the software available in source code format. To the extent required by such open source software licenses, the terms of such license will govern. NOTICE & DISCLAIMER: These materials and accompanying information (including, for example, any software, and references to 3 rd party companies and 3 rd party websites) are for informational purposes only and provided AS IS. Microchip assumes no responsibility for statements made by 3 rd party companies, or materials or information that such 3 rd parties may provide. MICROCHIP DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING ANY IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY DIRECT OR INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL, OR CONSEQUENTIAL LOSS, DAMAGE, COST, OR EXPENSE OF ANY KIND RELATED TO THESE MATERIALS OR ACCOMPANYING INFORMATION PROVIDED TO YOU BY MICROCHIP OR OTHER THIRD PARTIES, EVEN IF MICROCHIP HAS BEEN ADVISED OF THE POSSIBLITY OF SUCH DAMAGES OR THE DAMAGES ARE FORESEEABLE. TRADEMARKS: The Microchip name and logo, the Microchip logo, dspic, FlashFlex, KEELOQ, KEELOQ logo, MPLAB, PIC, PICmicro, PICSTART, PIC 32 logo, rfpic, SST, SST Logo, SuperFlash and UNI/O are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries. FilterLab, Hampshire, HI-TECH C, Linear Active Thermistor, MTP, SEEVAL and The Embedded Control Solutions Company are registered trademarks of Microchip Technology Incorporated in the U.S.A. Silicon Storage Technology is a registered trademark of Microchip Technology Inc. in other countries. Analog-for-the-Digital Age, Application Maestro, BodyCom, chipkit, chipkit logo, CodeGuard, dspicdem, dspicdem.net, dspicworks, dsspeak, ECAN, ECONOMONITOR, FanSense, HI-TIDE, In-Circuit Serial Programming, ICSP, Mindi, MiWi, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, mtouch, Omniscient Code Generation, PICC, PICC-18, PICDEM, PICDEM.net, PICkit, PICtail, REAL ICE, rflab, Select Mode, SQI, Serial Quad I/O, Total Endurance, TSHARC, UniWinDriver, WiperLock, ZENA and Z-Scale are trademarks of Microchip Technology Incorporated in the U.S.A. and other countries. SQTP is a service mark of Microchip Technology Incorporated in the U.S.A. GestIC and ULPP are registered trademarks of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of Microchip Technology Inc., in other countries. All other trademarks mentioned herein are property of their respective companies Microchip Technology Incorporated. All Rights Reserved VCS Slide 101

17066 CBA. Developing Android and iphone Applications to Control Bluetooth Accessories

17066 CBA. Developing Android and iphone Applications to Control Bluetooth Accessories 17066 CBA Developing Android and iphone Applications to Control Bluetooth Accessories 2013 Microchip Technology Incorporated. All Rights Reserved. 17066 CBA Slide 1 Objectives By the end of the class you