Visual studio feeds

All Visual Studio blogs in one place

Subscribe

Enter your email address:

Delivered by FeedBurner

Increase your website traffic with Attracta.com

Google+

Contact

Email:
Subject:
Message:
Anti-spam: How many eyes has a typical person?

Follow us on FB

Search

Announcing DAX Studio 2.2.0

AddThis Social Bookmark Button
Originally posted on: http://darren.gosbell.com/archive/2015/06/24/announcing-dax-studio-2.2.0.aspxToday we released DAX Studio 2.2 which includes a number of big enhancements. You can download the new release from http://daxstudio.codeplex.com/releases Below is an outline of the new functionality you will find in this release. Intellisense DAX Studio now has intellisense support, it's a fairly basic implementation, but I think I've got it working fairly smoothly. Note that it’s based on the best practice of always prefixing columns with the tablename and never prefixing a measure with a table name. So if you type ‘table name’[  you will get intellisense for
all the columns in the ‘table name’ table. But if you just type [ you will be presented with a list of all the measures in the model. The intellisense brings up table, column and measure metadata information from the current model: As well as functions and keywords, including the descriptions for functions. The function metadata is coming from the DICOVER_FUNCTIONS dmv so it should accurately reflect the capabilities of the current data source (So you will see some additional functions when connected to newer data sources such as Power BI Designer): ...(Read whole news on source site)

Announcing PostSharp 4.2 Preview 3

AddThis Social Bookmark Button
It has been a few weeks since the release of PostSharp 4.2 Preview 1. Today, I’m happy to announce new features and improvements to PostSharp. If you want to discover them, you can download PostSharp from our website or from NuGet (make sure to enable pre-releases). What was new in PostSharp 4.2 In the previous blog post, I already announced the following improvements included in PostSharp 4.2 Preview 1: Support for Visual Basic Amazing performance improvements in ready-made patterns Other improvements in threading models Today, I’m announcing the following new features: Thread-safety policy Ready-made patterns: support for System.Collections.Immutable Ready-made patterns: support for rules Module initializers Support for INotifyPropertyChanging OnAspectsInitialized
advice How we dogfooded our own threading models Most of the improvements we are publishing in this release stem from dogfooding our threading models into PostSharp Tools for Visual Studio. I’m proud to say that we now have a multithreaded VS extension without a single lock or event. Now that all threading assumptions have been made explicit and declarative, the code is much cleaner and easier to understand. Frankly, the experience was both exciting and awkward. Exciting because the result is amazing. Awkward because we filed more than 50 bugs, enhancements and user stories in the process – principally usability issues or improvements....(Read whole news on source site)

Generating CSV-files on .NET

AddThis Social Bookmark Button
I have project where I need to output some reports as CSV-files. I found a good library called CsvHelper from NuGet and it works perfect for me. After some playing with it I was able to generate CSV-files that were shown correctly in Excel. Here is some sample code and also extensions that make it easier to work with DataTables. The post Generating CSV-files on .NET appeared first on Gunnar Peipman - Programming Blog.

Deploying custom services as Azure Webjobs

AddThis Social Bookmark Button
Azure has this thing called webjobs. It is a curious way of deploying continous or scheduled services as sub-processes of an Azure website. This may be a desirable option because: it’s a PaaS thing. You don’t have to manage a server. you get configurable scale - including autoscaling you can run many logical services within a single management unit (Azure Website) I did not enjoy my time with the MSDN documentation for Azure Webjobs. They document the manual process for working with Webjobs, either the Visual Studio Azure tooling or through the Azure portal. Manual deployment processes, involving clicking lots of buttons with
a mouse, a not going to be workable on my team, so I need a way to automate deployment. Also, the documentation only shows how to write services that are coupled to Azure. I want to be able to run my service locally. Step 1: Use a console app for your service The holy grail of .net services has been wrapping console apps for a long time, often using something like Topshelf. The goal is to get the reliability of a service for deployment but the ease of development and testing of a console app. To create a console app for...(Read whole news on source site)

PowerShell : Trigger a release in Release Management from TFS builds

AddThis Social Bookmark Button
With TFS 2013, the default template provides the ability to extend the out of box capabilities by providing post build process scripts, that can be used to execute custom PowerShell scripts as part of the build process. With the combination of the post build scripts and the TF_BUILd environment variables its very easy to provide PowerShell customization and execute them during the build. In this post, we'll see how we can combine these together to trigger a release from Release management using the Orchestration service API from release management. If you want to see the details of the REST API,
use Fiddler to tract the calls through the Release Management Client application.
I'm using the InitializeReleaseFromBuild API to trigger a release in Release Management. The formatted uri should look like http://RMSERVER:PortNumber/account/releaseManagementService/_apis/releaseManagement/OrchestratorService/InitiateReleaseFromBuild?teamFoundationServerUrl=”tfsserverurl"&teamProject="project"&buildDefinition="definition"&buildNumber="build”&targetStageName="targetStage”

Later using the ReleaseStatus API, we can query the status of the release.
http://RMSERVER:PortNumber/account/releaseManagementService/_apis/releaseManagement/OrchestratorService/ReleaseStatus?releaseId=releaseId&api-version=2.0

param
(
    [string]$rmserver,
    [string]$port, 
    [string]$teamProject,  
    [string]$targetStageName,
    [string]$tfsUrl
)
$buildDefinition = $env:TF_BUILD_BUILDDEFINITIONNAME
$buildNumber = $env:TF_BUILD_BUILDNUMBER

$location = $MyInvocation.MyCommand.Name
 | Split-Path-Parent (Get-VariableMyInvocation -ScopeScript).Value.MyCommand.Path

Push-Location $location

$server = [System.Uri]::EscapeDataString($tfsUrl)
$project = [System.Uri]::EscapeDataString($teamProject)
$definition = [System.Uri]::EscapeDataString($buildDefinition)
$build = [System.Uri]::EscapeDataString($buildNumber)
$targetStage = [System.Uri]::EscapeDataString($targetStageName)

$serverName = $rmserver + ":"+ $port
$orchestratorService = "http://$serverName/account/releaseManagementService/_apis/releaseManagement/OrchestratorService"

$status =@{
    "2"= "InProgress";
    "3"= "Released";
    "4"= "Stopped";
    "5"= "Rejected";
    "6"= "Abandoned";
}

$uri = "$orchestratorService/InitiateReleaseFromBuild?teamFoundationServerUrl=$server&teamProject=$project&buildDefinition=$definition&buildNumber=$build&targetStageName=$targetStage"

$webClient = New-Object...(Read whole news on source site)

Home