Adrian Hara

Working through the .NET maze

  Home  |   Contact  |   Syndication    |   Login
  46 Posts | 0 Stories | 108 Comments | 10 Trackbacks

News

Twitter












Archives

Post Categories

October 2006 Entries

Today I came across a nice feature of the ConfigurationElement framework class (for those of you who don't know what it's used for, you might want to check out this post). I needed to have a Point represented in the config file, like so: <someElement topLeft="100,100"/>. So in the code for my derived ConfigurationElement class I wrote some quick code to parse the string and return a Point, like so: [ConfigurationProperty("gra... IsRequired = false)] public Point GraphTopLeft { get {...

Here are two assembly signing gotchas I ran into today: 1. I had two assemblies, A and B, and A had an [InternalsVisibleTo(”... attribute (my concrete scenario, A is the “main” assembly and B a unit tests assembly). Everything is peachy! Then I go and sign them and compile: boom! Compilation fails with the following error message: “Friend assembly reference 'B' is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations”...