I am installing the OpsHub Visual Studio Online Migration Utility, and teh email with verification code never arrived. I tried 2 different networks, and tried a corporate and personal email account with no success. I emailed support, but the autoresponser requests that a posting be made on Stack Overflow with the #opshub and #visual-studio-online tags. If OpsHub support read this, can yo please respond with an email verification code please.
I have the same issue as you. I hope OpsHub support can help us resolve it.
Additionally, instead of using the OpsHub Visual Studio Online Migration Utility, would you consider using TFS Integration Platform at the present? You can use it to migrate version control and work-item/bug tracking from on-premise TFS to VSO.
Related
Having already followed the advice in the SAP website documentation and installed the developer edition of SQLAnywhere 17, and also having manually run the installer for VS integration that is provided by this installation I still could not see any providers other than the MSSQL ones while creating an EF6 model in Visual Studio 2017.
I found this https://www.nuget.org/packages/Sap.Data.SQLAnywhere.EF6/17.0.7.3399
Does anyone know where to find documentation on how to use it? Nuget provides no links to documentation and does not list a repo.
I installed the package without incident and it appears in project references but it does not appear in the provider list when I try to create an EF model.
A request to the package author provoked this response:
Hi Peter,
For information and documentation go to:
https://sqlanywhere-forum.sap.com/
or with SyBase
http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc01776.1604/doc/html/san1357754863708.html
Kind Regards, Erwin Bakels
While I appreciate the prompt response, the documentation link leads to information about doing another thing with a different version -- it's for code-first with EF4.3 while the library is for EF6 and I need database-first. To be fair to Erwin, I didn't explicitly tell him I wanted database-first, but it's still not a usable answer.
Further research suggests that changes in VS2017 prevent the installer from registering the provider correctly. This implies that until such time as SAP updates the installer to suit VS2017 there is no possibility of designer support for EF with SQL Anywhere.
I have confirmed with SAP support, that Sql Anywhere ADO.NET integration with Visual Studio is not supported in VS2017. You will have to use VS2015 or earlier.
SAP DocCommentXchange
I suggest you download the SQL Anywhere, developer edition. You will get all the files necessary to use EF.
Using the OpsHub free migration tool to go from TFS to Visual Studio Team Services, is it possible to get an output that says User Story ID 123 is now User Story ID 789? To give us a mapping to update/reference for use with out support system.
Thanks in advance for any help.
No, OpsHub migration tool does not support this feature.
I am using the OpsHub Visual Studio Online Migration Utility and when I go to the User Mapping screen, I receive the following dialog box:
Error
"com.opshub.eai.metadata.MetadataException: OpsHub-014371: Could not instantiate metadata implementation for For User List | TFS Source 1437692124799 ALM TFS 1437692124807, due to (301)Moved Permanently"
Also, I installed the utility on multiple computers, tried connecting to different TFS 2010 instances, but always receive similar error messages.
Does anyone have any experience troubleshooting this issue?
I'm looking at whether we can migrate our old on-premises TFS 2010 server to Visual Studio Team Services. We all have MSDN subscriptions so it looks promising. But we have an app we wrote to keep our SQL scripts in version control. The app uses the old Microsoft.TeamFoundation.Client & Microsoft.TeamFoundation.VersionControl.Client object model approach. I'm lost in the Marketing-focused pages about VS Team Services and all I can find is talk of a REST API. Would we really have to re-write this part of the app or am I just missing something?
(I know we could do the source control bit from Visual Studio but the app has other functionality I haven't seen elsewhere.)
Can anyone advise me, please?
The TFS 2010 API works just fine with Team Services, so your app should just work.
You can currently use the 2010, 2012, 2013, and 2015 TFS client API's for TFS against Team Services. Team Services is just TFS on the internet...
Is it possible to publish bug reports directly to Visual Studio Online without having a Visual Studio Online account?
My idea would be that, when a crash of the application happens, the "fail" screen shows an option to send the bug report. I would like this bug report to be automatically added to Visual Studio Online.
I can't seem to find a good up-to-date information about APIs for Visual Studio Online.
I'm also a bit lost about what a "user" of Visual Studio Online is. Is there a way to create "a work-item only user"? In the "standard" TFS those users usually don't need a CAL to access TFS.
If not, it means that all my app testers will use a license for Visual Studio Online, meaning that after the 5 free users, I'll have to pay ~40 USD for someone who will just input bugs/work items?
Each user who needs to login to a Visual Studio Online account will need to have a user plan associated to them (including the free Basic plan allotments) or an MSDN subscription to access the account. We don't have the ability to have anonymous users login to a Visual Studio Online account (or for Team Foundation Server either).
You are right that there is a difference today between Team Foundation Server and Visual Studio Online which allows a "work item only view" on-premises that isn't matched in Visual Studio Online. That access level is called Limited for TFS on-premises instead of Standard. The Standard access level does require a TFS CAL. It's something we are currently exploring now.
Update
Visual Studio Online (and Team Foundation Server Update 4) now allows an unlimited number of stakeholders to have full access to work item tracking for free. This stakeholder license replaces and expands the original Work Item Only View capabilities.
For your testers, the best option for them would actually be Visual Studio Test Professional with MSDN or the new MSDN Platforms offering. This provides them the ability to access Microsoft Test Manager (in the first case) and the web test case management capabilities (in both cases) and allows you to file rich actionable bugs reports.
Update
Visual Studio Online has also been updated to provide the ability to execute test cases as part of the Basic license now. This will be most useful for user acceptance testers who aren't participating in test planning & test authoring but have been assigned a set of test cases to execute.
For your question about up-to-date API information for Visual Studio Online - it is the same documentation as the the TFS SDK at the moment. You can use the TFS SDK to build extensions for both Team Foundation Server and Visual Studio Online.