• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 174
  • Last Modified:

.net framework 4 client profile targeting issues

Hi
When attempting to retarget our vb.net application from .net 2.0 to .net 4.0 we tried two available target framework options...
1.      .net framework 4
2.      .net framework 4 client profile
If we select option 1 then our application retargets without issue. However option 2 results in VS2010 crashing immediately when switching from Debug to Release (using the VS toolbar combo).
Please note we have already considered...
http://msdn.microsoft.com/en-us/library/vstudio/cc668079%28v=vs.100%29.aspx
How can we identify what’s causing VS2010 to crash when option 2 is selected?
Thanks
0
antonms
Asked:
antonms
  • 2
  • 2
1 Solution
 
Jacques Bourgeois (James Burger)PresidentCommented:
Your application probably references assemblies that are not in the Client Profile. In such a case, Microsoft advise to target the full Framework (http://msdn.microsoft.com/en-us/library/vstudio/cc656912(v=vs.100).aspx).

Note also from the same page, that starting with Framework 4.5, the client profile is no longer available. Unless you have very good reasons to use the client profile, I would thus suggest that you drop it now.
0
 
antonmsAuthor Commented:
Thank you for your reply,  we also believe the problem relates to referencing an assembly that's not available in the Client Profile, however we are trying to establish what reference is causing VS2010 to crash.
0
 
Jacques Bourgeois (James Burger)PresidentCommented:
I do not know of a way to do it automatically, but you can try the following.

Load the project for the full version of the Framework. Compare the list of referenced libraries with the list provided at http://msdn.microsoft.com/en-us/library/ff462634(v=vs.100).aspx. Those in the project that do not make it in the list on the web page are the ones.
0
 
antonmsAuthor Commented:
Hi
Apologies for my late reply, the only .net related reference, not available in the Client Profile list, I could find was Microsoft.VisualBasic.PowerPacks.Vs

C:\Program Files (x86)\Reference Assemblies\Microsoft\VBPowerPacks\v10.0\Microsoft.VisualBasic.PowerPacks.Vs.dll

However when I remove the reference VS still crashes - I think we will stick with the full framework option. Thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now