Skip to main content

PowerShell and assembly (DLL) - How to debug and load configuration file

This week we had to make a PowerShell script that call a .NET assembly class and trigger an action on a worker role. We wrote the logic in C# because was more simple for us, even if we could write the logic in PowerShell.
The .NET assembly had to read some configurations from configuration file. When we wrote the C# code, it was tested using Unit Tests and it was very simple in that case – we used app.config for this.
But when you want to the call of the logic from PowerShell thing are changing a little.
[Reflection.Assembly]::LoadFile(' [assemblyFilePath].dll')
Even if we had the configuration file (app.config) in the same folder as our assembly, the PowerShell script would throw an expectation that the configuration was not found.

How to attach VS to PowerShell
First thing that you should do in this moment is to attached to PowerShell process before running the script. You can do this from menu: Debug\Attach To Process. You need to select from the processes list the ‘powershell’ and attach to it.
Once this step is done, you will be able to find put any breaks points in the code or catch from Visual Studio all the exception that are thrown by you assembly. Don’t forget to run the script one more time for this.

Specify the configuration file of assembly
When you load an assembly from PowerShell, the configuration file is not loaded automatically. To load a configuration file for a given assembly you need to add in your script the following command
[System.AppDomain]::CurrentDomain.SetData(
    "APP_CONFIG_FILE", 
    ‘[configurationFilePath].config’)
Don’t forget that this call needs to be before assembly loading:
[Reflection.Assembly]::LoadFile(' [assemblyFilePath].dll')
[System.AppDomain]::CurrentDomain.SetData("APP_CONFIG_FILE", ‘[configurationFilePath].config’)


Conclusion
Don’t forget that running C# code from PowerShell is not like running console applications from a bat. Because of this you should be aware of these things.

Comments

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…