Search

Unable to change target framework version to 3.5 because Visual Studio "thinks" it is a test project by gthimmes

Closed
as By Design Help for as By Design

4
1
Sign in
to vote
Type: Bug
ID: 553106
Opened: 4/21/2010 2:50:50 PM
Access Restriction: Public
0
Workaround(s)
3
User(s) can reproduce this bug
I am getting the "Attempted re-targeting of the project has been canceled. You cannot change the specified .NET framework version or profile for a test project." when I try to change one of my class library projects to to target 3.5 framework. This library cannot compile as 4.0.

I do not see any reason why my project is seen as a test project. Any suggestions? This is preventing us in upgrading to the new and wonderful 2010 Visual Studio.

Thanks,

Glenn
Details (expand)

Product Language

English

Visual Studio Version

Visual Studio 2010

Operating System

Windows 7

Operating System Language

English

Steps to Reproduce

I open the properties for the project and try to change the target framework. I can supply the project if necessary.

Actual Results

---------------------------
Microsoft Visual Studio
---------------------------
Attempted re-targeting of the project has been canceled. You cannot change the specified .NET framework version or profile for a test project.
---------------------------
OK
---------------------------

Expected Results

I expect it to change.
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey.

 

File Attachments
File Name Submitted By Submitted On File Size  
JustWareServiceBroker.VS2010.zip 4/22/2010 13 KB
Sign in to post a comment.
Posted by HellSpawnDev on 8/28/2011 at 5:59 PM
I do not consider this a viable solution as removing this GUID renders the project useless because after doing so you can no longer run the tests.

Attempting to put the ProjectTypeGuid back in the .csproj file after changing the Target Framework from 4.0 to 3.5 results in the Conversion wizard being invoked which in turn attempts to change the Target Framework back to 4.0!!!

Please advise if there will be a fix for this or not.
Posted by gthimmes on 4/26/2010 at 10:24 AM
Izzy, thanks for the solution. That is exactly what I needed to know. We are going to upgrade our projects this week and this will certainly simplify the process for us.

-Glenn
Posted by Microsoft on 4/26/2010 at 9:37 AM
Hi -

Thanks for reporting this. The way that Visual Studio determines the type of a project is by examining the <ProjectTypeGuids> XML element in the .csproj or .vbproj file. In your case, you have the following:

<ProjectTypeGuids>
{3AC096D0-A1C2-E12C-1390-A8335801FDAB};
{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}
</ProjectTypeGuids>

(line breaks added for clarity). The {3AC096D0-...} GUID represents the Test Project type. If you remove that GUID (and the separator semicolon), you should be left with a plain-vanilla C# project that you'll be able to re-target.

Thanks,
-- Izzy

Izzy Gryko
Lead Software Design Engineer
Microsoft Visual Studio Platform Development
izzyg@microsoft.com
Posted by Microsoft on 4/25/2010 at 8:36 PM
Thanks for your feedback. We were able to reproduce the issue you are seeing. We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by gthimmes on 4/22/2010 at 7:26 AM
I have stripped all code files out the the project and uploaded the project.
Posted by Microsoft on 4/21/2010 at 11:34 PM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

Could you please attach a zipped project file to this feedback through our site to help us reproduce the issue?

Thanks again for your efforts and we look forward to hearing from you.
Visual Studio Product Team
Sign in to post a workaround.