If you have used Visual Studio 2017 to connect to a Team Services instance, or you follow the Microsoft ALM blog you will have noticed that with Visual Studio 2017: Work items now open in the web from Visual Studio ’15’! While the official post shows why that change was made and what advantages the web form brings, I wanted to quickly point out some small things that were done to make this behavior more usable. You can follow along by downloading Visual Studio 2017 and connecting to your Team Services or Team Foundation Server 2017 instance. Running Queries from Visual Studio There is still the full work item query tree available in Visual Studio, including favorites: You can also still create and run new[…]
If you stumble across the following error message with Visual Studio 2013 Update 2 RC: 1>[…]\Package.appxmanifest(19,64): error APPX3210: App manifest references the image ‘Assets/Icon150.png’ which does not have a candidate in main app package. have a look a at the manifest file. In my case I had been using forward slashes in some of the asset paths. While this used to work before update 2 it now leads to an error. So to fix this I had to replace this: <m2:DefaultTile Square310x310Logo="Assets\Icon310.png" Wide310x150Logo="Assets/Icon150.png"> with this: <m2:DefaultTile Square310x310Logo="Assets\Icon310.png" Wide310x150Logo="Assets\Icon150.png"> and the error went away.
I just had a case where my Visual Studio 2013 solution failed to build even though no errors were displayed in the output pane or the log. The same happened for all the other targets (Clean Solution etc.). Building from the command line using msbuild directly, on the other hand, worked fine. The solution (as in previous VS versions) was to delete the user-specific settings. So a quick: del /s /q *.user fixed the problem for me.