Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Solved
Go to Solution
Accepted Solutions
Link copied. Please paste this link to share this article on your social media post.
Updates of individual libraries in an existing solution depend on what update is released.
-
Patch Versions: Bug fixes and minor additions are released as patch versions, indicated by an increment in the third part of the version number. If you open a solution with a new patch available, your solution will get these updates automatically without any prompts. These fixes are designed not to affect other parts of your application.
-
Minor Versions: Updates that include configuration changes are released as minor versions, indicated by an increment in the middle part of the version number. When a new minor version is available, you will be notified upon opening your solution that there is a new version of that library. You can then review the changelog to decide whether to apply the update for the specific library to all your applications using that library in your solution, or continue with the existing version.
-
Major Versions: Major structural changes or a total rebuild of a library will result in a new major version. In this case, you cannot update an existing solution to the new major version. The latest major version will only be used when creating a new application from scratch.
Note: You can see what version of individual libraries you are using by hovering over the library name (green text) in each application
Link copied. Please paste this link to share this article on your social media post.
Updates of individual libraries in an existing solution depend on what update is released.
-
Patch Versions: Bug fixes and minor additions are released as patch versions, indicated by an increment in the third part of the version number. If you open a solution with a new patch available, your solution will get these updates automatically without any prompts. These fixes are designed not to affect other parts of your application.
-
Minor Versions: Updates that include configuration changes are released as minor versions, indicated by an increment in the middle part of the version number. When a new minor version is available, you will be notified upon opening your solution that there is a new version of that library. You can then review the changelog to decide whether to apply the update for the specific library to all your applications using that library in your solution, or continue with the existing version.
-
Major Versions: Major structural changes or a total rebuild of a library will result in a new major version. In this case, you cannot update an existing solution to the new major version. The latest major version will only be used when creating a new application from scratch.
Note: You can see what version of individual libraries you are using by hovering over the library name (green text) in each application
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.