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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…