Visual Studio DLL name, why won’t you change?

So I decided that my project name sucked, and I wanted to change it into something different. I went ahead and renamed all the references in my KimKardashian project to EngelbertHumperdink. Everything – class references, project and solution names – you name it, I changed. Yet when I build my project, I continued to see the KimKardashian.dll file in the bin directory.

So I had to think outside the normal “Replace All” paradigm, going for a win-win  and synergize with myself. What I came up was is a healthy disgust of office buzzwords. But what I also came up with that the csproj file was what I needed. I went into my EngelbertHumperdink.csproj file and found two elements, RootNamespace and AssemblyName, and they had my nemesis:

<RootNamespace>KimKardashian</RootNamespace>

<AssemblyName>KimKardashian</AssemblyName>

A quick name-change and rebuild and all was well. Long live Engelbert Humperdink!

Advertisements
  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: