Databases
StackOverflow2013
Postsdbo
POvisual studio C# 2010 conversion issue
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POvisual studio C# 2010 conversion issue
    primarykey
    data
    text
    <p>Running to this issue. I open a project in visual studio 2010. The conversion wizard comes up, I press finish. It opens the project but fails to compile complaining about missing assembly referencs when all references are there. I suspect it is because of conversion. The .csproj file is changed from :</p> <pre><code>&lt;Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="3.5"&gt; </code></pre> <p>TO</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0"&gt; </code></pre> <p>So target framework has changed. How do I disable this? I am not doing anything from my side. Just opening the project and it is failing to compile. Is there some intellifence in Visual Studio 2010 to disable or NOT do this, so I can do some development and compile things. It references a ton of other projects and I don't have the option of converting them.</p> <p>The project was initially developed in 2008 and I am now opening in VS 2010. </p> <p><em><strong>Update</em></strong> It looks like the problem is some of the assemblies referenced from this older application have been upgraded to target framework 3.5. But this application is still targeting 2.0. So I upgraded its target framework. </p> <p>Now there is another problem. Both this application and a referenced assembly have a reference to an assembly A. But application is referencing A 5.0 whereas the referenced assembly is referencing version A 6.0. So Visual studio is complaining about that. Why do these versions have to match? Can't the application and its referenced assembly use different versions of common assembly?</p> <p>The error reporting in visual studio is shady and pathetic.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser236215
    1. USuser236215
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POvisual studio C# 2010 conversion issue
      1. USSecurity Hound
      1. VTFavorite
    2. VO
      singulars
      1. POvisual studio C# 2010 conversion issue
      1. USuser236215
      1. VTFavorite
    1. COWhat you posted is exactly the same. The only difference is the `ToolsVersion` which does not indicate which .NET Framework your trying to target. **What is the exact build error?**
      singulars
      1. POvisual studio C# 2010 conversion issue
      1. USSecurity Hound
    2. COError 2 The type or namespace name '..' does not exist in the namespace '...' (are you missing an assembly reference?). The required references are there as dependencies and they compile fine. the project is used in prod environment and compiles on a daily basis. Something is going on with visual studio 2010.
      singulars
      1. POvisual studio C# 2010 conversion issue
      1. USuser236215
 

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