I am attempting to migrate to VSO from TFS and receiving the following errors:
I have administrative rights in both VSO and TFS.
Please help me figure out what the problem is.
Thank you!
Here you find answers to your all queries.
Administrative Right(s):
The OpsHub Visual Studio Online Migration Utility requires that the user that is used to create the Visual Studio Online End Point is a member of the Project Collection Administrator Group.
To grant the user that particular right, follow the following link.
http://www.opshub.com/ohrel/Resources/TFS/permissions.php?page=admin
Template Customization:
You are facing template customization error due to you have configured custom field(s) at your source end.
& such field(s) are not exist on your target VSO.
Solution for this is to delete the custom field(s) at your source end & revalidate again to processed further using migration utility. Migration on customized process templates are not supported through free utility.
You can revert customization incase you want to continue your migration with free utility with the help of following article.
http://msdn.microsoft.com/en-us/library/dd236909.aspx
You can use power tools for quick configuration of custom fields
http://visualstudiogallery.msdn.microsoft.com/f017b10c-02b4-4d6d-9845-58a06545627f
Missing Link Type(s) Warning:
You are seeing link type warning because your target VSO instance is not having Affects and Affected by link types. Still you can continue the migration with warning, in this case your Affects & Affected by link type(s) will migrated as “Related” link type.
Alternative solution is to create new project with CMMI template in your target end. This will automatically add the missing Affects & Affected By link type(s) in target VSO. After doing this revalidate again and proceed further without warning. You can remove newly created CMMI project once you are able to see Affects, Affected by link types in you project.
Related
Noticed that Azure DevOps is no longer showing the menu options in Project Settings for the Extensions.
Does anyone else see this or know why?
I am unable to update settings for the installed extensions.
You can manage the installed extensions in the Organization settings.
Go organization settings--> Extensions under General. See document here for more information.
I have seen the same thing, and it only occurred recently. Yes, the org level extension management is still there, and that only allows for managing which extensions are available to use.
The configuration for the extension usage within each project was a separate section in the project settings - this is missing entirely. We have need to modify one of our extension configs and can no longer access it to do so.
I believe this must be an Error of type PEBKAC coming from a recent MS update to DevOps.
I use Team Foundation Server for Source Control and in my Visual Studio I unckeckd the Option: "Multiple Check Out".
But when I check out a file and modify it another user can still check out the same file and also modify it.
What went wrong??
If you have to look at this issue then you are probably not checking in enough. Its a workflow and not tool change that is required.
TFS only supports the single checkout model if all users are using Server Workspaces. The default changed in 2012 to Local Workspaces which does not support this.
https://msdn.microsoft.com/en-us/library/ms181383.aspx
Check out the MSDN documentation for how to change workspace modes.
Locally the project works perfectly.
It is executing and there are proper entries in database.
But when I am deploying it to cloud at staging it is giving me this error as object reference not set to an instance.
My project requires 2 instances of each web and worker role but since I have a limited edition to free instances I am using only 2. one each. Can that be a problem ?
I am using SDK 1.8
It is ASP.Net project.
Can anyone suggest me how to resolve this issue ?
I had a similar issue where I was getting the following when publishing from Visual Studio 2013 to my Azure Cloud Service with a web role and a worker role. This occurred after upgrading the project from Azure SDK v2.4 to v2.5:
2:41:59 PM - Applying Diagnostics extension.
2:42:01 PM - Object reference not set to an instance of an object.
Even after working with a Microsoft Developer I could not get it to show me any kind of stack trace to indicate where the null was coming from. He just happened to notice something funny in my cloud configuration under the "Roles" folder that looked strange.
The problem was that the diagnostics.wadcfgx is needed for an SDK 2.5 project, whereas before that version the diagnostics.wadcfg is needed. (Note the "x" in the file extension.) Apparently the worker role did not have this file automatically created when the project was upgraded.
In order to fix this particular issue, just right click on the role (in the roles folder under cloud configuration) and select "Add Diagnostic Configuration", then Build the solution and attempt to publish. These diagnostics files are ONLY needed when publishing directly from Visual Studio.
I haved same error today, after upgrading Azure SDK to version 2.5
I'm add configuration diagnostics to each role in service and the error disappeared
Had this with MS Azure Tool 2.9. Turned out that it needed the following in diagnostics.wadcfgx :
<PrivateConfig xmlns="http://schemas.microsoft.com/ServiceHosting/2010/10/DiagnosticsConfiguration">
<StorageAccount endpoint="" />
</PrivateConfig>
Hope it helps someone!
I ran into the same issue when upgrading to 2.5. It created the .wadcfgx files and they looked sensible but deployment via Visual Studio would still fail with the same error.
Applying Diagnostics extension.
Object reference not set to an instance of an object.
Package deployment would still work. I was able to get past it via the following steps.
Delete the generated .wadcfgx files
Have Visual Studio regenerate them via the context menu option on the role.
Doing a clean build and redeploying.
I'd love to know what the actual error was and how to get more details. The messaging is pretty terrible.
My issue is that I cannot select a build process template after migrating to TFS/VS2012.
I managed to google and find one article which suggest the same problem here,
Possible Bug
Any ideas how I can get the dropdown to load the Build Process Templates or why they may not be getting loaded?
Also, I am able to click New->Copy Template, and copy successfully, but it never populates the dropdown list after accepting.
Possibly the same issue
I recently ran into the same problem but not related to upgrading the server. We were not able to see build process templates when trying to add a new build definition. We are in TFS 2012. This team project also appeared not to have any build definitions. That was expected though because we had not yet used the TFS builds on this team project.
The problem was caused by someone with admin rights setting the "View build definition" and the "View Builds" access rights to Deny for everyone.
By just setting that back to allow on the TFS group, we suddenly could see the build definitions and also were able to select build process templates.
It was really strange that it let us add new build process templates, but we couldn't select them.
Sooo...
I was finally able to get the templates loading by doing the following.
Unmapped the entire TFS project which had been mapped in a sub folder and not at the root.
Deleted files from disk completely
Remapped the TFS project, this time from the root TFS project level
Accepted the "get"
After doing this my build definitions loaded and worked. (Seems to be a mapping issue...bug...)
This may be an extream solution and I am still not sure what happened but it now works.
I have VisualStudio 2012 and I'm trying to follow the following tutorial http://msdn.microsoft.com/en-us/library/hh674270.aspx
But I couldn't find the option Schema Definition from the WCF pane of the Templates dialog.
Do I have to install something? What would that be? An extension, perhaps?
Thanks in advance.
You don't need to install it - it's already there. What might be catching you out is that it's only available in the "WCF Service Library" template.
Once you then add a schema file as shown:
You then get an additional option on the project properties:
I want to add my findings.
I too wanted the Contract-First tool and didn't find the setting mentioned in the msdn link.
However I found out how to add it to any project type as I wanted my iis-hosted services to use contract first aswell.
What you do is to create a "WCF Service Library" as mentioned above.
Then open the csproj-file for the project in a text editor.
Then copy paste the entries that looks something like this into the other project-file
<FlavorProperties GUID="{3D9AD99F-2412-4246-B90B-4EAA41C64699}">
<WcfProjectProperties>
<AutoStart>True</AutoStart>
</WcfProjectProperties>
</FlavorProperties>
Also you need to change the guid:s in the target project to something like this:
<ProjectTypeGuids>{3D9AD99F-2412-4246-B90B-4EAA41C64699};{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>
The FlavorProperties tag with its guids are from vs2012 update 3 so it may change in the future.
So with this hack you're able to deploy contract first services directly to the iis.
The question however is why it wasn't working like this out of the box in visual studio 2012
You don't need to add the XSD from the WCF pane, just take the XML Schema item from the Data pane.
If VS 2012 has the option "Enable XSD as type definition language" on, it will generate the types under the namespace of your solution + ".ContractTypes".
Check the output windows to see what the build process is doing with the XSDs.