INTELLIGENT.TECHNICAL.ARCHITECTURE.TRAINING

 
 
Blogs:
 
 

Posts Tagged ‘WinRT’

October 20, 2013 / No Comment
AUTHOR:
CATEGORY: .Net, ALM, Blog, C#, Visual Studio

To make generic tests robust enough to run for all developers on your team and on the build server, you are likely going to want to avoid hard coding the path to the executable.  To do this successfully, you need to have a list of all the environment variables that are available when the test executes.  These can be obtained by creating a generic test with the existing program as %COMSPEC% (the fully pathed location for cmd.exe) and setting “/C set” as the Commnd-line arguments.  The result, with all standard environment variables pulled out, is as follows:

AgentId=1
AgentLoadDistributor=Microsoft.VisualStudio.TestTools.Execution.AgentLoadDistributor
AgentName=<ComputerName>
AgentWeighting=100
ControllerName=localhost:6901
COR_ENABLE_PROFILING=1
COR_PROFILER={<UUID1>}
DataCollectionEnvironmentContext=Microsoft.VisualStudio.TestTools.Execution.DataCollectionEnvironmentContext
DeploymentDirectory=<SolutionDirectory>\TestResults\<TestRunDirectory>\Out
MSBuildLoadMicrosoftTargetsReadOnly=true
MSBuildTreatAllToolsVersionsAsCurrent=true
PkgDefApplicationConfigFile=<LOCALAPPDATA>\Microsoft\VisualStudio\12.0\devenv.exe.config
ResultsDirectory=<SolutionDirectory>\TestResults\<TestRunDirectory>\In
TestDeploymentDir=<SolutionDirectory>\TestResults\<TestRunDirectory>\Out
TestDir=<SolutionDirectory>\TestResults\<TestRunDirectory>\
TestLocation=<ProjectDirectory>
TestLogsDir=<SolutionDirectory>\TestResults\<TestRunDirectory>\In\<ComputerName>
TestOutputDirectory=<SolutionDirectory>\TestResults\<TestRunDirectory>\In\<UUID2>\<ComputerName>
TestResultsDirectory=<SolutionDirectory>\TestResults\<TestRunDirectory>\In\<UUID2>\<ComputerName>
TestRunDirectory=<SolutionDirectory>\TestResults\<TestRunDirectory>\
TESTRUNNER_DATACOLLECTOR_INSTANCE=<UUID3>
TestRunResultsDirectory=<SolutionDirectory>\TestResults\<TestRunDirectory>\In\<ComputerName>
TotalAgents=1
VisualStudioDir=<UserProfile>\Documents\Visual Studio 2013
VisualStudioEdition=Microsoft Visual Studio Ultimate 2013
VisualStudioVersion=12.0
VSLANG=1033
VSLOGGER_CPLAN=<LOCALAPPDATA>\Microsoft\VisualStudio\12.0\TraceDebugger\Settings\qorgnywy.n4l
VSTS_PROFILER_NOT_CLEAR_ENVVARS=1
__UNITTESTEXPLORER_VSINSTALLPATH__=C:\Program [...]

Read more

Visual Studio 2012 Presenter Mode

November 9, 2012 / 1 Comment
AUTHOR:
CATEGORY: Blog, Visual Studio

For those of us frequently presenting, we are faced with having to switch to presenter fonts by changing the font size for multiple different display items on the Environment->Fonts and Colors Options dialog or (if we are looking for an adequate but not optimal solution) simple changing the zoom level.  Of course, when we get back to our desks, we have to switch back the settings to fit with our 3 monitor 2560 × 1600 WQXGA resolution (purely hypothetical in my case).

To streamline the change the November release of the Visual Studio Productivity Power Tools 2012 (see [...]

Read more

Deleting Moldy Shelvesets

October 20, 2012 / 1 Comment
AUTHOR:
CATEGORY: Blog, PowerShell, TFS

If you have had a Team Foundation Server (TFS) instance running for any significant length of time you undoubtedly have old shelvesets lying around from other developers (surely you wouldn’t have done this) that have long ago expired and although moldy, they have not disintegrated. Consider cleaning them up using the following short PowerShell script from Kelly Adams:

Get-TfsShelveset -Owner * |
?{ $_.CreationDate -lt “7/1/2012″ } |
%{ Remove-TfsShelveset -ShelveSet (“{0};{1}” -f $_.Name, $_.OwnerName) }

Note:

  • The “-Owner *” on the Get-TfsShelveset command is what finds shelvesets from other developers rather than just yourself.
  • You need to have the Team [...]
    Read more

  • Removing Duplicate Entries from %PATH%

    June 30, 2012 / 2 Comments
    AUTHOR:
    CATEGORY: PowerShell, Windows

    As developers, we frequently end up with duplicate entries in our path. From the command line you can clean up your path using pathman.exe. Here’s a PowerShell Script to find the duplicates and remove them using Pathman.exe:

    $extraPath=(($path.Split(“`;”) | group | ?{$_.Count -gt 1}).Values | %{$_[0]}
    pathman.exe /ru $extrapath

    Disclaimer: Works for us.

    IntelliTect Presents at the Seattle Code Camp 2012

    June 15, 2012 / No Comment
    AUTHOR:

    Asynchronous Programming with C# 5.0Mark Michaelis
    In C# 5.0 there is really only one significant syntax addition – support for asynchronous programming that is embedded into the language. In this session we go over the is and is-nots of what C# 5.0 enables in the way of parallel processing – both for the UI and for the server tier. Don’t miss this session to learn not only the fundamental syntax but also the best practices and scenarios of what the async keyword enables.

    PowerShell for DevelopersMark Michaelis & Read more

    GIST: Windows Server “8” Administrative Experience

    April 3, 2012 / No Comment
    AUTHOR:

    There are several items that deserve highlighting from Erin Chapple’s post (via Jeffry Snover) titled, “Rocking the Windows Server “8” Administrative Experience”.  Here’s my gist:

  • Administration designed for one a single-role centric view to a multi-server view of the environment.  The result is that rather than administer a role on a particular server you will now be able to administer a role that may span multiple servers.
  • The PowerShell based Command-line Interface (CLI) for Windows administration is a both/and experience – both CLI and GUI.
  • CLI automation increases reliability, auditability, and predictability – across multiple servers none-the-less.
  • Server Core is the preferred [...]
    Read more

  • Turning on Continuous Testing in Visual Studio 11

    March 2, 2012 / No Comment
    AUTHOR:
    CATEGORY: .Net, Blog, C#, Visual Studio

    The new unit testing explorer support has a new unit test explorer has a Run dropdown for selecting which text to execute (see Figure 1).

    In addition, Visual Studio 11 supports continuous testing – automatically running your tests every time you compile your code.  However, as shown in Figure 1, the option to enable continuous testing doesn’t appear from the Run dropdown (and probably shouldn’t because you are not likely to be changing the option back and forth that often).  To enable continuous testing, select the Unit Test->Unit Test Settings->Run Tests After Build menu as shown in Figure 2.

    New Attributes for Trace/Logging Information in .NET 4.5

    March 2, 2012 / No Comment
    AUTHOR:
    CATEGORY: .Net, C#

    There is a new set of .NET attributes in .NET 4.5 to help with gathering trace information.  Before .NET 4.5, tracing the line number, member name, and source file name required using the stack trace in combination with the PDB files.  In .NET 4.5, however, there is a new mechanism for doing this using attributes on optional parameters.  Consider the code below:

    Note the static public void Write(string message, [CallerLineNumber] int lineNumber = 0, [CallerMemberName] string memberName = null, [CallerFilePath] string fileName = null) method signature and how it uses the parameter attributes CallerLineNumber,CallerMemberName, and CallerFilePath from the System.Runtime.CompilerServices namespace.  By [...]

    Read more

    Installing Windows 8 Consumer Preview on the Windows Build Samsung Galaxy Slate

    March 1, 2012 / No Comment
    AUTHOR:
    CATEGORY: Blog, Windows

    If you copy the Windows 8 Consumer Preview directly to a USB key and run Setup.exe you are likely to see a dialog indicating you need 20 GB of disk space and, obviously, there is no such availability on the tablet given the previous Windows 8 Developer Preview install.

     

    Windows 8 20 GB Required
    Windows 8 20 GB Required

    The work around it to use a command prompt boot from USB as follows:

  • Create a bootable USB key using the  Read more

  • Storyboarding in Visual Studio 11 with Lorem Ipsum Auto-expand

    February 29, 2012 / 1 Comment
    AUTHOR:
    CATEGORY: Blog, Visual Studio

    One of the “easter egg” (meaning not intuitively discoverable) features in the Storyboarding for Visual Studio is the fact that text boxes (of any kind – Text Areas, Text Input, Text…) you can type “=Lorem()” followed by ENTER to fill the text box with Lorem Ipsum text as shown here:

     

    IntelliTect Corporation
    3024 S. Bannen Ct.
    Spokane Valley, WA  99037

    Phone: (509) 315-3400
    Email: info@intelliTect.com

      COPYRIGHT © 2006-2012 INTELLITECT. ALL RIGHTS RESERVED.