![]() ![]() In this context, "latest" means "latest supported version." These installer entries will not automatically detect a subsequent release of Visual Studio. At that point, your VSPackage can offer to upgrade the file to the new format or open the file and maintain compatibility with earlier versions of the VSPackage. If you add newer VSPackages to the list of programs that are associated with an old extension, users can right-click the file and choose to open it in a newer VSPackage. This difference identifies the VSPackage that opens a particular file. mypkg10, and version 2 could use the extension. For example, version 1 of your VSPackage could use the extension. ![]() To avoid this issue, you can change extensions when file formats become incompatible. The downside to this approach is that the upgraded file cannot be opened in the earlier version. If that is not true, you should offer to upgrade the file format to the new version of your VSPackage. Ideally, your VSPackage can both load and save the file formats of earlier versions. Users expect a new version of a product to be compatible with earlier versions, so that existing files can be loaded in a new version without losing data. Incompatible file formats compound the issue. ![]() ![]() If your VSPackage provides file associations, you must decide how to handle side-by-side installations in which a particular version of Visual Studio should be invoked to open a file. Applies to: Visual Studio Visual Studio for Mac Visual Studio Code ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |