Today I came across a problem with dynamically loading assemblies using MEF, when the assembly being loaded has a dependency on yet another assembly. In my case this was SignalR.
I was typically seeing the error:
Could not load file or assembly 'AssemblyNameHere, PublicKeyToken=xxxxxxxxxxxxxxxxx' or one of its dependencies. The system cannot find the file specified.
The reason for this is because the CLR is looking for the dependency in the directory in which the assembly host is running, and not the location of the assembly MEF loaded in.
The way around this is in this MSDN article. By using the probing tag in the app.config, you can specify the directory to look for dependencies. The caveat with using probing is you can only specify sub-directories of the assembly host, so if you want to use an absolute path to another place on the disk then probing isn't the solution, but I'd argue whether you needed it in another place anyway.
The config change required should look something like this:
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="Modules\"/>
</assemblyBinding>
</runtime>
</configuration>
Assembly Host (.exe) -> Assembly (.dll) -> SignalR (.dll)
Could not load file or assembly 'AssemblyNameHere, PublicKeyToken=xxxxxxxxxxxxxxxxx' or one of its dependencies. The system cannot find the file specified.
The reason for this is because the CLR is looking for the dependency in the directory in which the assembly host is running, and not the location of the assembly MEF loaded in.
The way around this is in this MSDN article. By using the probing tag in the app.config, you can specify the directory to look for dependencies. The caveat with using probing is you can only specify sub-directories of the assembly host, so if you want to use an absolute path to another place on the disk then probing isn't the solution, but I'd argue whether you needed it in another place anyway.
The config change required should look something like this:
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="Modules\"/>
</assemblyBinding>
</runtime>
</configuration>
If you bought a Windows Phone 8 device recently and want to play an action game to kill time, the freeware Epic Battle Dude can help. Epic Battle Dude turns you into a king, putting you on a mission where you battle monsters who encroach upon your kingdom, and even kidnap the queen. You need to battle these creatures using weapons such as the sword, axe and mace. Epic Dude is also available to Android and iOS users.
Facebook is not just a replica of reality, but also a mythical land where some true stories are so bizarre, that you often wonder if it is some poorly scripted piece of fiction. Of late though, the recent confessions pages have been creating most of the stir on FB, but there is enough fodder for those looking for some reality-TV style tales out in the open. Here are some of the classic cases of virtual insanity that India has seen via the social networking service.
A few years back, a quality sub-10k smartphone was a distant dream. But thanks to the Android platform, the situation has completely changed. We now have a problem of plenty in the budget smartphone segment. In March, we published a list of phones worth buying for Rs 15,000. However, if you're not willing to cross the Rs 10,000 barrier, these are the options you should be looking at. Note that this list is not in any specific order:
If the Note II wasn't big enough for you, you'd rejoice to see the
