Databases
StackOverflow2013
Postsdbo
POWorking with multiple versions of Visual Studio
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWorking with multiple versions of Visual Studio
    primarykey
    data
    text
    <p>I'm trying to find a way of being able to use multiple versions of Visual Studio on the same set of projects. The majority of our team uses 2008, but I am trying out 2010. All projects are C#.</p> <p>As I understand it Visual Studio 2010 insists on upgrading all projects, so it's not possible to leave all the solution/project files as 2008 versions. I really don't want to branch the entire source tree, so I'd like to find a way for multiple versions of the project files coexisting. Currently, I've duplicated all .sln and .csproj files so I have:</p> <pre><code># 2008 versions SolutionName.sln ProjectA.csproj ProjectB.csproj # 2010 versions SolutionName.vs2010.sln ProjectA.vs2010.csproj ProjectB.vs2010.csproj </code></pre> <p>The trouble is, despite the 2010 versioned files all having the same assembly names as their 2008 counterparts, Visual Studio (2010) believes the projects are all <code>ProjectName.vs2010</code>. Renaming the project in VS fails with a message saying a file of the same name already exists.</p> <p>I don't think putting the 2010 version in a sub-folder would be a solution as it would screw up any relative paths in the files.</p> <p>So:</p> <ul> <li>Is there any way to convince VS that the project name should not be suffixed with .vs2010 (i.e. not the same name as the file)? Or</li> <li>Am I approaching this the wrong way? Is there a better way of working with multiple versions of VS on the same projects?</li> </ul> <p><strong>UPDATE</strong></p> <p>My initial claim was wrong that Visual Studio was failing to find the project references because it was using the file name. The specific problem I was having was that in my build files the project references were of the form:</p> <pre><code>&lt;ProjectReference Include="..\..\path\to\ProjectName.vs2010.csproj"&gt; &lt;Project&gt;{48354450-2462-449D-8B32-EFECA39F6CD7}&lt;/Project&gt; &lt;Name&gt;ProjectName&lt;/Name&gt; &lt;/ProjectReference&gt; </code></pre> <p>The project files that I copied apparently have a different ID (or whatever it is in the <code>&lt;Project&gt;</code> element. Simply removing the element from the build file has solved that particular issue:</p> <pre><code>&lt;ProjectReference Include="..\..\path\to\ProjectName.vs2010.csproj"&gt; &lt;Name&gt;ProjectName&lt;/Name&gt; &lt;/ProjectReference&gt; </code></pre> <p>Having said that, the whole process of duplicating the project and solution files has actually been more effort than it's worth, so I'm not recommending this approach.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSimonC
    1. USSimonC
    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. POWorking with multiple versions of Visual Studio
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWorking with multiple versions of Visual Studio
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWorking with multiple versions of Visual Studio
      1. USNiki
      1. VTFavorite
    1. COWhat problem is having the project names end in the ".vs2010" suffix causing you? The project name shouldn't have any impact on you
      singulars
      1. POWorking with multiple versions of Visual Studio
      1. USDamien_The_Unbeliever
    2. COSorry, forgot the actual problem... Some projects have project references to the other projects and VS is failing to find the references (i.e. a reference to `ProjectName.vs2010` works, but just `ProjectName` fails).
      singulars
      1. POWorking with multiple versions of Visual Studio
      1. USSimonC
    3. CObut project references are held in project/solution files - files you're already maintaining separate versions of for the two versions of VS.
      singulars
      1. POWorking with multiple versions of Visual Studio
      1. USDamien_The_Unbeliever
 

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