Visual TFS Reports setup

Will not work on Windows 7 – See other post in this blog

  1. Pre-requisites
    SQL Server 2008 R2 with Reporting Services and Analysis Services
  2. Use Team Foundation Administration Console > Application Tier > Reporting
    Edit > Use Reporting ticked > Warehouse Tab > Server (enter name) Database (Tfs_Warehouse)
    Analysis Services Tab > Server (enter name) Database (Tfs_Analysis) Account for accessing data sources Username maybe Domain\User
    Reports Tab > Server (enter name) > Populate URLs Web Service in format http://server:port/ReportServer and Report Manager http://server:port/Reports
    Account for accessing data sources Username maybe Domain\User
    Default Path /TfsReports
  3. May need to Use the WarehouseControlWebService.asmx as in Connect link below. Address is
    http://localhost:8080/tfs/TeamFoundation/Administration/v3.0/WarehouseControlService.asmx
    http://connect.microsoft.com/VisualStudio/feedback/details/653006/team-foundation-reports-broken-the-warning-parameter-is-missing-a-value-iterationmdxparam-parameter-is-missing-a-value
  4. For me the standard out of the box reports for MSF for Agile.. were missing
    This seems to be because I created the “Visual Studio > Team Explorer > New Team Project ” before setting up TFS reporting.
    First attempt in brackets below. My second attempt was “Visual Studio > Team Explorer > New Team Project > this creates reports for the process of your choice. > Move the reports to the project folder of your choice > Detach the project > Go to Team Foundation Server Administration Console > Team Project Collections > Delete the Team Project”

    (Initially tried to resolve this by finding the Compressed Zip file with the standard reports in. Then uploading the reports into Report Server one by one.
    From the source I had, this had the affect of wrong datasources. After pointing the datasource to the new name Tfs2010ReportDS instead of TfsReportDS this then went further)

  5. Bug Status report uploaded send the “Warning” parameter was missing a value.
    First attempt > Manage report > Parameters > Click the web button for Use Default or something like this> Report then ran but had no data
    Second attempt > TFS Administration Console > Reporting > Start Rebuild (takes a while)
    See http://msdn.microsoft.com/en-us/library/cc668753.aspx
    and http://social.msdn.microsoft.com/Forums/en-US/tfsadmin/thread/c8a324ea-c329-41bf-901e-82f464fac4bb

    STILL NOT WORKING. Getting Closer I Feel.

VS TFS Build

Connect to VS-TFS remotely

This is another great help. Benefits include working more towards a common code library from home or work.

  • Connect to VPN
  • Visual Studio
    • > Connect to Team Foundation Server
    • Servers
    • Add
    • Use remote network internal i.p address
    • Use default settings
    • May be prompted for Login and password
    • Done > Success
  • Or in intenet explorer
    • http:// < internal ip address : <vs-tfs port number default = 8080> /tfs

Microsoft.Common.targets (1360): Found conflicts between different versions of the same dependent assembly

Problem

Warning : “Found conflicts between different versions of the same dependent assembly”

Not enough information

Solution – Method

The verbosity of builds may be changed in Visual Studio > Tools > Options > Projects and Solutions > Build and Run > MSBuild Project output verbosity. May need to go to at least detailed. Then use the output window to get more information.
The verbosity may also be changed in the VS-TFS build.

Then search in the Output for “conflict”, and underneath it states:

“References which depend on “… new version
“References which depend on “… old version

Make them match.

Solution – Binding Redirect

Optionally check-in the file containing the app.config.

If you double click on the warning then you may get a message:

“One or more dependent assemblies have version conflicts.
Do you want to fix these conflicts by adding binding redirect records in the app.config file?”

If you click OK, then use source code control to compare the app.config you will get a change in the newVersion setting

<runtime>
<assemblyBinding xmlns=”urn:schemas-microsoft-com:asm.v1″>
<dependentAssembly>
<assemblyIdentity name=”EntityFramework” publicKeyToken=”B77A5C561934E089″ culture=”neutral” />
<bindingRedirect oldVersion=”0.0.0.0-4.4.0.0″ newVersion=”6.0.0.0″ />
</dependentAssembly>
</assemblyBinding>
</runtime>

This Post History

VS-TFS Build was reporting this error for a long time, but not indicating precisely which file was causing the problem

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (1360): Found conflicts between different versions of the same dependent assembly

Generally have found the problem to be on a project which references another project, where both projects use the same references. One may get out of sync with the project being built.

Found the problem difficult to find. Not entirely sure what the problem was:
The build server had a copy of version 9 of Microsoft.VisualBasic.PowerPacks.Vs in c:\Program Files\Common Files\Microsoft Shared\…
instead of version 10.0 listed in some projects.
I checked that version 10 was installed on the build server, then removed the version 9 from this pc.
Could have perhaps considered making the PowerPack reference copy local.

Also try working out any references listed in the problem project which are also used by referenced projects and include a reference to the problem project. I have found that where Visual Studio builds projects without the referenced project references, MSBuild seems to need them in the target project as well. This was not in fact the case in my resolution here.

Example solved 15-Mar-2011 was System.Windows.Forms.DataVisualization was version 3.5.0.0 in a user control. Upgraded all to 4.0.0.0.

See http://stackoverflow.com/questions/1871073/resolving-msb3247-found-conflicts-between-different-versions-of-the-same-depend

Build server automated tests fail SQL authentication

If unit tests are testing against the database using Integrated Security then when these automated tests are put onto the build machine authentication may fail.
SOLUTION. Create a SQL login for a machine which is possible.
CREATE LOGIN [MyDomain\MyComputer$] FROM WINDOWS;
http://social.msdn.microsoft.com/Forums/en/sqlsecurity/thread/315b5780-c131-4867-88b9-ebac82e68d77

VS TFS Team Build Process

Install not too bad. Recommendation was to put on a standalone machine or server that would not use too many resources. I picked my spare XP SP3 machine and installed Visual Studio Team Foundation Server 2010. For drop folder I used a server with short directory name \\server-name\Build
Then using Team Explorer in VS from my developer machine I created a Build definition.

First bug was:
user ‘nt authority\network service’ needs write permissions to the path
Solution was go to highest directory add security for Network Service Full Control, but only for that folder
Then for folder Build I also added security for Network Service. This all took sometime.

Now running however next problem was
assemblies not on machine.
Installed on build machine Report Viewer then later VBPowerPacks. Getting better

Next problem was
dll’s below root of build
Solution was to create a “solution folder” called CommonAssemblies and added the required dll’s into this folder. Then Checked these in to Source Code control and pointed projects using these to this folder.

Next problem was
When a program used one assmbly which used another dll build did not work properly. 
Solution was to add dll to last project to build.

———-

Worked great for a day then Build controllers stopped working:
“there was no endpoint listening at http:// … /v3.0/… that would accept the message this is often caused by an incorrect address or soap action”
http://www.ewaldhofman.nl/post/2010/07/14/Build-server-stops-suddenly-and-frequently.aspx
“In my case it turned out that I had a duplicate entry in the DHCP server for the Build Server. Removing the duplicate entry solved the issue.”
DHCP server on PDC server. On inspection I also had duplicate entry in DHCP server. We then a reserved IP address for my XP Build Server machine. This may have helped.
However also in TFS Administration Console changed the “Build Service properties” “Local Build Service Endpoint (incoming):” to use http:// < ip address of machine >

Visual Studio TFS on Windows 7 – no support for Reporting Features

 
Visual Studio TFS on Windows 7 – no support for Reporting Features
True !!  Even if you try.
 
Later on could try having a virtual server with a Server os on it and then add reporting services
In the meantime I have succeeded in most of my other TFS, specifically will now have ability to use Source Code Control to allow me to work on laptop or XP machine. Also Work Item management !!
 
  • Windows 7 (Windows 7 Home Premium, Windows 7 Professional, Windows 7 Enterprise, Windows 7 Ultimate)

  • Note
    Client operating systems do not support integration with SharePoint Products or the reporting feature. If you want to use either of these features, you must install Team Foundation Server on a server operating system.

  • Visual Studio TFS Over a home network ( Team Foundation Server ) ( 2010 )

     
    Objective: Put VS TFS on W7 and then connect to this on my Windows XP desktop so I can work from either
    7 laptop with full TFS including Source Code Control and Work Items
     
    Wow … round the houses but have got there … think it was really important to achieve
    I do not have a lot of network experience so thought I had to set up a virtual server. Then spent hours and hours getting Virtual Server 2005 R2 and Hyper-V RSAT on my W7 machine with the intention of then installing a server system on virtual server, then connecting to this etc etc…
     
    However I have just discovered that I did not need to do this.
     
    Make sure the Windows 7 has a user login and password
    Go to W7 Team Foundation Server Administration Console > Get Web Access URL e.g. http://computername:portno/tfs/web
    Go to XP IE and enter above address. Should be asked for a login – password. Enter this and hey presto you should be in.
    In XP Visual Studio Connect to Team Foundation Server Add server. Just enter server name if using default port numbers and path. Then connect.
     
    Now I am in business and can start coding -> adding value to my product 
    At last !!
     
     
     

    TFS Team Foundation Services Installation

     
    Not easy. Will not proceed if Frontpage Service Extensions are installed in IIS
    In order to remove this go to Tools > Control Panel > Add Remove Programs >Add Remove Window Components > Double-click Application Server > Double-click Internet Information Services IIS > Uncheck Frontpage 2002 Server Extensions