Home/ Questions/Q 4021890
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T10:24:26+00:00

I have a very odd problem. Whenever I try to use the Add View

  • 0

I have a very odd problem. Whenever I try to use the “Add View” dialog in ASP.NET MVC2 and then try to “Create a strongly-typed view” by selecting a “View data class” from the drop down of available classes none of the classes (“models”) in my MVC project are showing up.

The very odd part is all of the assemblies that my MVC project is referencing, even other projects in the solution, their classes are showing up. I have tried cleaning, rebuilding, cleaning the obj folder but every single time for some reason none of the classes in my actual MVC assembly are showing up. It was working fine before but now it doesn’t anymore and I can’t really think of anything that has changed.

Anyone experienced this issue before?
Thanks for the help!

Image of example:

http://imgur.com/47itE.png

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Figured this out, here is the solution:

    The MVC Project was referencing a bunch of service contract assemblies that where referencing a “CommonServiceContractAssembly.dll”. The MVC Project was also referencing “CommonServiceContractAssembly.dll”. The MVC Project and the service contract assemblies were all built referencing slightly different versions of “CommonServiceContractAssembly.dll”

    When Visual Studio 2010 was reflecting on all referenced assemblies to “Create a strongly-typed view” of I believe it wasn’t sure how to handle the slightly different version of “CommonServiceContractAssembly.dll” being referenced so it didn’t display the reflected “strongly typed model” possibilities for any assemblies dependent on “CommonServiceContractAssembly.dll”.

    The fix is to actually force Visual Studio 2010’s app domain to use the correct version of “CommonServiceContractAssembly.dll” when Visual Studio 2010 starts up. This was accomplished with a Post Build Event like the following:

    REM This is required for T4 generation from models to work properly
    copy “$(TargetDir)”CommonServiceContractAssembly.dll” “$(DevEnvDir)PublicAssemblies\” /Y

    So I copy “CommonServiceContractAssembly.dll” that is referenced “everywhere” into where Visual Studio will load it. After I did this everything worked properly.

    Another option would be to always ensure that all assemblies that share a common dependency are always compiled with the same version of that dependency.

    • 0