Adding an app.debug.config app.release.config transformations in .NET applications

Most applications need to run on multiple environments and with multiple configurations. At a minimum we usually have at least a local and production environment, but more often we have a local environment, a system test, UAT as well as our production and pre-production environments. Transformations allow you can have different settings for different configurations (debug or release). 

For example, the most common transformation is our connection string. For different databases , we will always have different connection strings That means a lot of different configurations are needed for each environment. Currently for ASP.NET, MVC and Web API projects, we have this functionality supported with our Web.config transformations. However for our app.config, i.e. for console or class libraries this is still not supported, out of the box. So we have to manually create our own transformations.

Previously, I have achieved these transformations manually, as you can see from this previous article I wrote: Adding an app.debug.config app.release.config transformations in .NET applications   , but now there are many different extension and Nuget packages for Visual studio, like Slow Cheetah and Configuration Transform which help you to achieve this much easily. 

Slow Cheetah 

Lately I have been using Slow Cheetah a lot and I really like it, this package allows you to automatically transform your app.config in Visual studio. You can either download it as a Visual Studio extension from the website or just add it to your project from Nuget.

Once installed ,you get a right click option to Add Transform, when you right click on your app.config in your project solution . 

Clicking this option will automatically create your new debug and release configs for you. 
And as you can see they are correctly nested underneath the app.config. This is because Slow Cheetah has automatically updated our project file to contain the necessary settings to tell the release and debug config that they are dependent upon the app.config. Before we had to manually make these adjustments to the project file ourselves.

If we open our project file and check the settings added, we can now see something like this, this is how we would normally have to edit our project file to look like, this basically defines the dependency between the app.config and the release and debug config.

Also notice the IsTransformFile element, this is the important setting for Slow cheetah. Instructing it to automatically transform the App.config file depending on the chosen configuration.

And that's it, a lot of manual work saved already. Now you can can add whatever customization's you like inside the transform files, for example if you want to tweak app settings and connection string.

E.G here I have just added an app setting to the app.config and the app.release.config , setting the value to true in the release config and false in the app.config. 

Note, the use of the replace transform key to prompt the replacement of this value and the locator key. 

So if we walk-through the example above, the replace transform key, sends the instruction to replace the true value from the isProd key located beneath the appSetting element. This is done using the xdt:Transform attribute. 

Also note , that all XDT documents, i.e. your app.config, and each environment config, need a namespace declaration in the root element, otherwise your transformations will not happen.

When you build your application the files are transformed and dropped into the output directory. If you are transforming the app.config then when the file is transformed it will be renamed in the output directory as usual to ensure that your application picks it up at runtime.

Preview Transform 

You can also quickly preview your transform using the Preview Transform context menu on the transform file. By selecting the release config and right clicking in the solution explorer, we are presented with the differences, which in our case, is the app setting differences we added between the app and release configs. However as you know, environment configs can become very long and detailed, so this Preview Transform tool can be a god send when you are trying to check settings or connection strings to debug an issue. 

How to fix: HTTP could not register URL error

Often when running a service , you might get the following annoying error :

HTTP could not register URL http://+:8000/MyWCF/. Your process does not have access rights to this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details).

To get around this you need to run up a command window and run the following for your service and domain :

netsh http add urlacl url=http://+:80/MyUri user=DOMAIN\user


Thanks to Brian via stackoverflow for this command and the explanation of the invalid exception text and how to find what's really going wrong.

Using FOR XML PATH(”) for String Concatenation

FOR XML PATH

Every now and then  I need to concatenate a column of strings returned from a SQL query, often I use the COALESCE function,

COALESCE





....but lately I've been using FOR XML PATH(”) a lot and am finding it easier to use. FOR XML PATH function can also be used for string concatenation when generating XML:

STUFF FOR XML PATH
Another handy function for string manipulation is STUFF. The STUFF function inserts a string

into another string. It deletes a specified length of characters in the first string at the start position and then inserts the second string into the first string at the start position.


STUFF (character_expression , start , length ,character_expression)

So applying that to the code above , we get something like this :

Calling a action/controller with params and showing a partial view in modal dialog in MVC3/4/5

Pretty much every MVC user application you write need a modal popup or even modal form dialog containing a partial view.
Therefore we need a mechnism for calling an action and controller , passing in an Id and returning a view model with results to a partial view inside a modal dialog.

There are many different options now but i always go back to this method when i need to achieve this as it gives me so much control not only over the params i can pass in ,but dialog size and style too.

This is the jquery code , i copy this to a separate js file in the project script directory.

$(document).ready(function () {
      $(".openDialog").on("click", function (e) {
          e.preventDefault();
          $("<div></div>")
              .addClass("dialog")
              .attr("id", $(this)
              .attr("data-dialog-id"))
              .appendTo("body")
              .dialog({
                  title: $(this).attr("data-dialog-title"),
                  close: function (ev, ui) { window.location.reload() }, //function () { $(this).remove() },
                  width: 600,
                  modal: true,
                  height: 'auto',
                  show: 'fade',
                  hide: 'fade',
                  resizable: 'false',
 
                  //buttons: {
                  //    "Close": function ()
                  //    { $(this).dialog("close"); }
                  //}
              })
 
 
          .load(this.href);
       
 
      });
 
   
 
      $(".close").on("@Html.ActionLink("Edit", "EditDocumentDetails", "Document",

             new { id = item.DocumentId }, 
             new 
             {     @class = "openDialog", 
                   data_dialog_id = "interestDialog", 
                   data_dialog_title = "Edit Document Details" 

             })click", function (e) {
          e.preventDefault();
          $(this).closest(".dialog").dialog("close");
      });
   
  });

An example of where this is called from a view is :

@Html.ActionLink("Edit", "EditDocumentDetails", "Document",
             new { id = item.DocumentId }, 
             new 
             {     @class = "openDialog", 
                   data_dialog_id = "interestDialog", 
                   data_dialog_title = "Edit Document Details" 
             })

And an example of your controller code :

public ActionResult EditDocumentDetails(int id)
      {
          var doc = this.context.ApplicantDocuments.Find(id);
          if (doc == null)
          {
              return HttpNotFound();
          }
 
          IEnumerable<SelectListItem> docTypes = this.GetReferenceList(Constants.ReferenceDocumentTypeList);
          ViewBag.DocumentTypes = new SelectList(docTypes, "Value", "Text", doc.DocumentTypeRef);
          
          return PartialView("_EditDocumentDetails", doc);
      }

CTE , ROW_NUMBER() PARTITION BY , useful tools when face with duplicate data

I recently came across an issue where I was retrieving data for a UI and dealing with potential dupes. for my purposes I used CTEs and row_number function to solve my particular issue.

 A CTE is essentially a kind of temporary table or a named result set off of a physical table (sort of like an in-line view).

With this function, you can number rows in your result set.  Even better, you can PARTITION BY to split your result set up into groups.  I might not want to see 1-10 as my row numbers, I might want to see 1-5 and 1-5 based on some column that I decide to partition the data by.  Note, this is a horizontal partition of rows.




 

 

A closer look -Enumerable.Range (System.Linq)

Enumerable.Range is a small static method in the  Enumerable class from System.Linq. 

The Enumerable.Range() method performs a very simple function, but it’s results can be used to drive much more complex LINQ expressions.  In it's simplest form it can be used to generate a sequence of consecutive integers. 

It accepts two int parameters, start and count, and constructs a sequence of count consecutive integers, starting at start:

• Range(int start, int count)

• Returns a sequence of int from start to (start + count – 1).

So, for example, the code snippet below will create an List<int> of the numbers from 1 to 10:

   1: var numbers = Enumerable.Range(1, 10).ToList();

   2: string nums= string.Join(",", numbers); 

   3: // result will be : "1,2,3,4,5,6,7,8,9,10"

Not just for numbers !

Or it can be used to  to generate a string containing the English alphabet

   1: IEnumerable<char> letters = Enumerable
   2:  .Range(0, 26)
   3:  .Select(x => (char)(x + 'a'));

   4: string alphabet = string.Join("", letters); 

   5: // result will be : "abcdefghijklmnopqrstuvwxyz"

Handy eh ?

Getting a bit more complicated now, if we wanted a list of the first 5 even numbers, we could start with the number of expected items and use the .Select() clause in conjunction with the mod operator to bring back only the even numbers :

   1: var evens = Enumerable.Range(0, 5).Select(n => n*2).ToList();

   2: string ans = string.Join(",", evens ); 

   3: // result will be : "0,2,4,6,8"

Alternatively , you can achieve the same result using the .Where() clause against the total results to filter it down:

   1: var another= Enumerable.Range(0, 10).Where(n => (n % 2) == 0).ToList();

   2: string ans = string.Join(",", another); 
   3: // result again will be : "0,2,4,6,8"

Or if you want to provide a min value, max value, and a number of steps, as demonstrated in this question on StackOverflow and answered by by John Skeet:

i.e. basically what was needed here was to return something like this :

0, 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000

Were the min was 0 , the max 1000 , and he wanted to get there in 11 steps.

   1: int numberOfSteps = 11, max = 1000, min = 0;
   2: var example = Enumerable.Range(0, numberOfSteps)
                 .Select(i => min + (max - min) * ((double)i / (numberOfSteps - 1)));
   3: string ans = string.Join(",", example); 
   4: // result will be : "0,100,200,300,400,500,600,700,800,900,1000"








Conclusion

The Enumerable.Range() method performs a very simple function, but it’s results can be used to drive much more complex LINQ expressions.

Displaying SSRS Report in MVC using MvcReportViewer -Part II

Embedding a Local Report

In my previous post we discussed how to install the MVCReportViewer package via Nuget into your application to avail of the helpers to embed SSRS reports into your MVC views.

In this article we will discuss using the MVCReportViewer  package and helpers to embed local reports.

Most often people want to embed SSRS reports from the server into thier views, but sometimes we just want to create a simple local report in Visual Studio and display that in our view. This is the scenario we will discuss below.

Creating reports in Visual Studio 2012/2013

Visual Studio 2012/2013 comes with reporting capibilites out of the box. Simply right click in your solution explorer in Visual Studio and Add Item/ Reporting and you can see you have the option to add a Report or use the Report Wizard.

This provides you with good basic reports, it's like a pared down version of the tools and controls you get with real SSRS. If this suits your needs you need go no further. However if you need more capilibilites than whats on offer here you will need to install the SQL Server Data Tools – Business Intelligence tools  for Visual Studio 2012/2013.

SQL Server Data Tools – Business Intelligence for Visual Studio 

Currently the URL to download Microsoft Visual Studio Tools for Applications component for Visual Studio 2012 can be found here:

http://www.microsoft.com/en-ca/download/details.aspx?id=38807

Once you have install it, you will be able to create and work with SSRS reports within Visual Studio. Here are the basic steps for setting up a new SSRS report project:

Open up Visual Studio

• Select File –> New –> Project
• You will now see a new project template option called Business Intelligence
• Expand this project template and select the Reporting Services option.
• You can now either choose to use the setup wizard or just a plain project template.

Regardless of whether your requirements necessitate the use of the Business Intelligence tools or the standard out of the box reporting tools in Visual Studio, lets now disucss adding a basic report to your project so you can embed it in your MVC view.

DataSets

Before creating your report, you need to define your dataset. Lets create a Report folder in our project. It is a good idea to organise your folder structure within your application in a logical manner , so we will use this folder for all our Datasets and reports.

Using the standard out of the box reporting functionality in Visual Studio 2012/2013, right-click in your Report folder and Add New item.

Go to Data-> and select Dataset. Call it