Showing posts with label Visual Studio. Show all posts
Showing posts with label Visual Studio. Show all posts

Saturday, November 10, 2012

TF31003 Error: TFS + Visual Studio 2012 + Windows 8

I think anyone who's worked with Team Foundation Server for significant amount of time has run into this or a similar variant of the (TF31003: Either you have not entered the necessary credentials or your user account does not have permission to connect to the Team Foundation Server at https://***.visualstudio.com/. Ask your server administrator to add the appropriate permissions to your account) error message at least once. I ran into it earlier today while trying to connect to the online Team Foundation Service (http://tfs.visualstudio.com) using Visual Studio 2012 running on Windows 8.

As the error code to be a generic one and covers a wide variety of issues, it took a bit of trial and error before was finally able to narrow down the issue that was ailing me:
http://stackoverflow.com/questions/11034882/tfs-in-visual-studio-2012-under-windows-8

As suggested, clearing all the cookies in IE resolved the issue for me.

Here is another link to the exact problem/solution that I found after the fact:
http://caioproiete.net/en/error-tf31003-connecting-to-tfspreview-from-visual-studio-2012/

Monday, August 30, 2010

Debugging Tips with Visual Studio 2010

Some useful debugging techniques for Visual Studio:

http://weblogs.asp.net/scottgu/archive/2010/08/18/debugging-tips-with-visual-studio-2010.aspx

Webservice Testing Tool - WcfTestClient

Windows Communication Foundation (WCF) Test Client (WcfTestClient.exe) is a GUI tool that enables users to input test parameters, submit that input to the service, and view the response that the service sends back. It provides a seamless service testing experience when combined with WCF Service Host.
I didn't know this tool existed until a few weeks ago. Apparently its a part of Visual Studio. I've started digging deep into WCF the last few days and its been an indispensable tool to say the least.

More Info on the tool here:
http://msdn.microsoft.com/en-us/library/bb552364.aspx

Also on a side note, I used to be a big fan of storm and they seem to have a paid version here which adds support to WCF. I don't know how it compares to WcfTestClient though.

Sunday, August 03, 2008

Debugging XSLT using Visual Studio 2005 / 2008

Visual Studio has the ability to debug XSL stylesheets. This a extremely useful feature that a few seem to know exist and use regularly.

Most of the projects I'm involved with use XSLT in one way or another. And the VS debugger along with other tools have saved me countless hours of frustration.

Here's a quick guide to get you started:

  1. Create / Open up the XSL file using Visual Studio
  2. Setup break points as necessary
    breakpoints
  3. Make sure that the XML Editor toolbar is visible
    XML Toolbar
  4. Click on the Debug XSLT button to start debugging
    debug_xsl
  5. A warning message would appear asking you to setup an input file. This would be the XML file that needs to be transformed. Click YES and select the input file.
    filename
  6. Step through the code.
    stepthrough

The only disadvantage or limitation rather is that you can't specify values for xsl:param variables. The workaround I use is to re-define the parameter as an xsl:variable , set the expected input value.

xsl_variable

On a related note, XslCompiledTransform class supports stepping into the stylesheet while debugging. The only pre-requisite is that the class should be instantiated with the debug parameter value set to true . Detailed instructions provided here.

Sunday, October 08, 2006

Development and Vista

Visual Studio vs. Vista: What's going on here?

What's going on here indeed?

I understand that applications/operating systems cannot always have full backward compatibility. But the inability to run their flagship development environment on their (near) future flag ship OS is just insane.

I'm sure that Microsoft will eventually issue some patches/fixes. But until then this is only hurt the adoption rate of Vista by developers and more importantly businesses.