Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6142505
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T18:23:45+00:00 2026-05-23T18:23:45+00:00

We have an application that supports both .NET 2.0 and .NET 4.0 and we

  • 0

We have an application that supports both .NET 2.0 and .NET 4.0 and we switch the few framework dependent assemblies with <bindingRedirect />. We’ve used the <supportedRuntime /> element to allow the application to run using the latest framework if available. However, we do still require the full profile, not just the client profile.

The documentation for .NET 3.5 indicates that you must explicitly opt-in to client only support by adding a sku="client" attribute to the <supportedRuntime /> element.

The sku attribute name is case-sensitive. If the sku attribute is
missing, or if its value is set to anything other than “client”, the
runtime assumes the application is not a .NET Framework Client Profile
application.

However, with .NET 4.0 detailed documentation on the sku attribute is missing. In our tests the .NET runtime will use the .NET 4.0 client profile even if the sku attribute is missing. This is a problem since it doesn’t allow dynamic redirection with the .config file. I’ve tried to use sku="full" to try and force it to only use the full profile but that just results in no .NET 4.0 runtime being supported.

The question

Does anyone know of a way to force the use of the full .NET profile when using <supportedRuntime /> (or other comparable solution) to support multiple .NET framework versions?

Snippet from our .config file

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <startup>
        <supportedRuntime version="v4.0.30319" />
        <supportedRuntime version="v2.0.50727" />
    </startup>

    <runtime>
        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1" 
                         appliesTo="v4.0.30319">

            <dependentAssembly>
                <assemblyIdentity name="Application"
                                  publicKeyToken="798276055709c98a"
                                  />

                <bindingRedirect oldVersion="4.1.2000.0"
                                 newVersion="4.1.4000.0" />

                <codeBase version="4.1.4000.0"
                          href="Redistributable\.NET 4.0\Application.dll" />

            </dependentAssembly>
         </assemblyBinding>
    </runtime>
</configuration>
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T18:23:46+00:00Added an answer on May 23, 2026 at 6:23 pm

    My understanding is this would work:

    <supportedRuntime version="v4.0.30319" sku=".NETFramework,Version=v4.0.1" />
    <supportedRuntime version="v4.0.30319" sku=".NETFramework,Version=v4.0" />
    

    There is no Profile=Full, but the Profile is meant to restrict to a smaller SKU per my understanding.

    The list of installed SKUs can be found at

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\SKUs
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a web application that supports a variety of clients on various platforms
I have an application for Mac OS X that supports plugins that are intended
We have an application (a custom network management tool for building automation) that supports
I have a .NET WinForms application that I've converted into a COM dll using
I have a .NET 2.0 application that won't run on a 64-bit OS (the
I have a published application which supports both amrv6 and armv7. Now I have
I have an iPad application that only supports landscape mode (just for a demo
I have an ASP.NET MVC web application that makes REST style web service calls
I have an ASP.NET MVC 3 application running on both my local dev box
I have this application that I want to support multi languages. I thought the

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.