Solved

.net framework 4 client profile targeting issues

Posted on 2015-01-08
4
135 Views
Last Modified: 2015-01-16
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
Comment
Question by:antonms
  • 2
  • 2
4 Comments
 
LVL 40
ID: 40543011
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
 

Author Comment

by:antonms
ID: 40543100
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
 
LVL 40

Accepted Solution

by:
Jacques Bourgeois (James Burger) earned 500 total points
ID: 40543179
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
 

Author Comment

by:antonms
ID: 40553818
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

Featured Post

Master Your Team's Linux and Cloud Stack

Come see why top tech companies like Mailchimp and Media Temple use Linux Academy to build their employee training programs.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article surveys and compares options for encoding and decoding base64 data.  It includes source code in C++ as well as examples of how to use standard Windows API functions for these tasks. We'll look at the algorithms — how encoding and decodi…
For most people, the WrapPanel seems like a magic when they switch from WinForms to WPF. Most of us will think that the code that is used to write a control like that would be difficult. However, most of the work is done by the WPF engine, and the W…
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA. http://www.experts-exchange.com/videos/1478/Excel-Error-Handlin…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question