Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Figured this out, here is the solution:</p> <p>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"</p> <p>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".</p> <p>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:</p> <p>REM This is required for T4 generation from models to work properly copy "$(TargetDir)"CommonServiceContractAssembly.dll" "$(DevEnvDir)PublicAssemblies\" /Y</p> <p>So I copy "CommonServiceContractAssembly.dll" that is referenced "everywhere" into where Visual Studio will load it. After I did this everything worked properly.</p> <p>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.</p>
    singulars
    1. This table or related slice is empty.
    1. POAttempting to add a strongly typed view does not find any classes in the MVC project
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJohn Culviner
    1. USJohn Culviner
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAttempting to add a strongly typed view does not find any classes in the MVC project
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COi'm having the exact same problem that you're describing here. i've checked references and updated everything to use the same version for all dependencies, but the problem persists. how did you figure out your solution btw?
      singulars
      1. PO
      1. USspaceman
    2. COHmm, I'm sorry to hear that solution isn't working for you. Take a look in reflector and verify the above too, you never know. How I managed my solution was thinking about how Visual Studio must be loading my assemblies to reflect on them to determine "ViewModel Candidates". Based on previous experience I know that .NET (and VS since it runs on .NET) can get "upset" if all referenced versions don't match up. I bet VS2010 throws an exception somewhere internally that is handled and just decides to quit on trying to resolve the affected assembly.. Keep us posted!
      singulars
      1. PO
      1. USJohn Culviner
    3. COThis answer pointed me to the right direction. My project was referencing for example `Assembly X 1.0.1` while one of the other references was using `Assembly X 1.0.0`. Updating the reference in that class library to the newer version did the trick.
      singulars
      1. PO
      1. USMarthijn
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload