StarTeam Visual Studio Plugin Known Issues and Limitations

In this topic:

Known Issues

• StarTeam VS Plugin fails because of missing MS Visual J# 2.0 library. Visual Studio Source Control configuration with StarTeam fails with following error: “Unable to load DLL vjsnativ: The specified module could not be found.”

  The issue is observed after Window 10 upgrade to v. 1809 or higher. The cause of the issue is the missing vjsnativ.dll after the upgrade. Microsoft Windows 10 does not provide Visual J#, which was available in previous versions of Microsoft Windows in their .NET redistributable.

  Workaround: If the OS was recently upgraded the vjsnativ.dll can be found in this directory: C:\Windows.old\WINDOWS\Microsoft.NET\Framework\v2.0.50727

  The file needs to be copied to the current Windows directory: C:\Windows\Microsoft.NET\Framework\v2.0.50727

  Alternatively, download the vjsnativ.dll from Visual J# redistributable package from Microsoft and copy to the current Windows directory: C:\Windows\Microsoft.NET\Framework\v2.0.50727

• When Internet Explorer is the default System Web browser, and enhanced security configuration has been enabled on a server machine, SSO login page could fail due to security restrictions. To resolve, enable secure connection for SSO on Tomcat web server. Alternatively, OSP web site can be added to the trusted website.

• Occasionally, using StarTeam File Compare/Merge stand alone or running the compare/merge inside Visual Studio throws the following exception: "Could not find any JRE". To work around this issue, ensure that set system environment variable JAVA_HOME is set correctly. For example:

  JAVA_HOME= C:\Program Files (x86)\Micro Focus\File Compare Merge\jre

• Component types for Atlas and StarTeam Agile, as well as custom component types, are now visible tabs in the StarTeam Visual Studio Plugin. While the web interfaces for these tools provide the preferred editing capabilities, if you would like users to be able to edit any of these item types from within Visual Studio, then an appropriate custom editor (either via Layout Designer or Alternate Property Editor) should be created and will be picked up by the StarTeam Visual Studio Plugin.

  Note: Rich text edit boxes on Custom Editors will not display in Visual Studio.

• The StarTeam Visual Studio Plugin Plugin does not support source code operations on Web Site projects that use a local IIS server. This is a known bug. There is no workaround other than using the embedded client and pointing it to the local files in the IIS server.
• When changing the source code provider for a solution from StarTeam SCC (or any SCC provider) to the StarTeam Visual Studio Plugin you must unbind the SCC integration using the File > Source Control > Change Source Control menu, then set StarTeam Visual Studio Plugin (Tools > Options > Source Control) as your source control provider. The system displays the File > Source Control > Change Source Control menu only if you have a solution that is bound to an SCC provider.
• When the connection to MPX has been broken for solutions or projects placed into StarTeam Server with MPX enabled, using the integration commands Update Solution or Refresh does not work. As a workaround for this issue, you can either:
  • Log off and log on to the StarTeam Server.
  • Perform a manual refresh using the StarTeam Refresh command or the Refresh button in the StarTeam Items or StarTeam Folders pane.
• Rich text support appears to be in place when copying and pasting text, images, or hyperlinks into text-based fields for a Change Request, Task, Topic, or Requirement. Once the item is saved to the StarTeam Server, the formatting and images are removed.
• When upgrading projects from the 2005 version of StarTeam Visual Studio Plugin to this integration, one person needs to migrate the project and check in the changes. That user must have the project and solution files current on disk so that they have the StarTeam sync records and no Unknown file statuses. After that, all users must pull the project or solution to their workspace for use in Microsoft Visual Studio 2012. You will get an error message if you try converting your Microsoft Visual Studio 2005 project to a Microsoft Visual Studio 2012 project by using the StarTeam > Pull Solution (or Pull Project) commands in Microsoft Visual Studio 2012. Perform the steps in the following example instead. For example:
  1. Open the StarTeam Cross-Platform Client (or Microsoft Windows client) and open the Microsoft Visual Studio 2005 project. Make sure that none of the files have an Unknown status. If any files have this status, select them, and choose File > Update Status from the main menu. If the files are not in your workspace, you will see a Missing status. In this case, you must check them out.
  2. Open the Microsoft Visual Studio 2005 .sln file in Microsoft Visual Studio 2012. Doing so automatically opens the Conversion wizard which converts the Microsoft Visual Studio 2005 solution and project files so that they can be used in Microsoft Visual Studio 2012.
  3. After completing the steps in the wizard, the solution and project files are marked as Modified by StarTeam. Choose StarTeam > Pending Checkins window to check in the files.
  4. Advise other users to open Microsoft Visual Studio, and choose StarTeam > Pull Solution (or Pull Project) to bring the files to their own respective workspaces for use in Microsoft Visual Studio.
• If you have a locally-modified file open and another user renames that same file and checks in the changes (including the solution file) and then you update the solution, you must manually merge the file from your local workspace with the renamed file to make sure that all of your changes are preserved. Additionally, you will no longer see the file by its original name in the Solution Explorer (your original file with its changes still exists in your local workspace), and you might see an error message if you have the file open in the Designer.
• Unlike Visual SourceSafe, you must save your files so that changes are recognized by the integration before accessing most StarTeam file commands. However, changes are automatically saved when using the StarTeam Place Solution, Place Project, Update Solution, Update Project, or Commit Project commands.
• If you use the options to either exclusively or non-exclusively lock files on check-out (found in the File tab of the StarTeam Personal Options dialog), and you check out but do not modify files or if you modify files and revert your changes, the files will not appear in the StarTeam Pending Checkins dialog. In this case, the files remained locked until you manually unlock them. This behavior differs from Visual SourceSafe where the check in dialog displays locked files and the check in operation unlocks unmodified files.
• Sometimes the Project Load Failure dialog box displays when you pull the project, but it can be ignored. The solution opens anyway.

Back to top

Limitations

• In the embedded client, the following new custom field types are not available: Boolean, Content, Date, Map, Group, Group List, Time span, User, User List, and Multiple Enumerated.
• You cannot view the properties of either a change package or its changes in the Changes tab of the StarTeam Visual Studio Plugin embedded client, but you can view this information in the Change tab of the StarTeam Cross-Platform Client.
• The StarTeam Cross-Platform Client is optional software, but you cannot use the Launch Client menu item from the StarTeam menu if it is not installed. If the menu item is selected, but the StarTeam Cross-Platform Client is not installed, StarTeam generates an error message.
• Changing the working folder in the StarTeam Visual Studio Plugin does not change the alternate working folder in the StarTeam Cross-Platform Client.
• On Windows Vista and Microsoft Windows 7, the default installation folder for the StarTeam File Compare/Merge component is C:\Users\Public\Micro Focus\File Compare Merge. If you change that location during installation, you must select a folder that all users can write to.

Back to top