Home/ Questions/Q 4330650
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T09:59:29+00:00

I have some general questions about web.config and how it works regarding assembly reference.

  • 0

I have some general questions about web.config and how it works regarding assembly reference. I’ve been playing around with the new Razor view engine and had some trouble getting it up and running.

My problem started with a general

The type or namespace name ‘XXXXX’
does not exist in the namespace
‘XXXXX’ (are you missing an assembly
reference?)

Now I figured this was just a simple Add Reference to the project and I’d be on my way. But even after I added a reference to the missing assembly, my project kept breaking.

I found the solution, and I had to add an assembly reference within the web.config. Once I did this everything worked fine.

First, I want to understand why it took adding a reference to web.config to fix this problem. Why wasn’t a project reference just good enough?

Second, when it comes to adding references in web.config, I would like to understand the syntax. When I see markup like this

<add assembly="System.Web.WebPages" />

it seems very clear to me that I’m adding an assembly named System.Web.WebPages. But the full syntax in my web.config is

<add assembly="System.Web.WebPages, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />

Version seems self explanatory, but what is culture and PublicKeyToken used for? Are they required? What happens if I don’t know either of them, can I just put anything in?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Answering your first question:

    There’s another SO question here with a useful answer:

    What is difference between web.config assemblies element and project file Reference element

    Essentially it is to do with differences between Web Projects and non-web projects in Visual Studio (as I understand it).

    Answering your second question:

    This took quite a bit of digging around but here you go:

    Culture – most assemblies should be culture neutral (assuming this is set in the application). However if you do have culture sensitive assemblies then this is where you specify the culture of the assembly.

    PublicKeyToken – this is the public key from the public/private key pair that was used to sign the assembly. Having this enables .NET to verify that the assembly it is loading is the correct one.

    More useful information here:

    http://en.wikipedia.org/wiki/.NET_assembly

    • 0