1.0 vs 1.1 framework conflict in VStudio

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Paul Wehland (pwehland_at_eMeSeN.COM)
Date: 03/15/04 

Date: Mon, 15 Mar 2004 13:22:26 -0800

I have both v1.0.3705 and v1.1.4322 of the .NET Framework installed on my
computer.

In my properties of my project in the references path, I have v1.1 listed
first, then v1.0 listed second. When I do this I cannot edit a WinForm
dialog. I get the error:
    "The designer could not be shown for this class because none of
    the classes within it can be designed. The designer inspected the
    following classes in the file Form1 -- The base class 'System.
    Windows.Forms.Form' cannot be designed"

The workaround is to reference v1.0 first, and v1.1 second. However when I
do this I cannot compile because there are some v1.1 features I need,
specifically FolderBrowserDialog.

The workaround works, but it cumbersome switching back and forth for editing
and compiling. Is there a better fix?

Relevant Pages

  • 1.0 vs 1.1 framework conflict in VStudio
    ... In my properties of my project in the references path, ... The designer inspected the ... The workaround is to reference v1.0 first, ... do this I cannot compile because there are some v1.1 features I need, ...
    (microsoft.public.vstudio.general)
  • 1.0 vs 1.1 framework conflict in VStudio
    ... In my properties of my project in the references path, ... The designer inspected the ... The workaround is to reference v1.0 first, ... do this I cannot compile because there are some v1.1 features I need, ...
    (microsoft.public.dotnet.framework)
  • 1.0 vs 1.1 framework conflict in VStudio
    ... In my properties of my project in the references path, ... The designer inspected the ... The workaround is to reference v1.0 first, ... do this I cannot compile because there are some v1.1 features I need, ...
    (microsoft.public.dotnet.languages.csharp)
  • Inherited forms in CF2 VS2005 cant compile
    ... I am using form inheritance in VS2005 professional and all was going well - ... when I added a reference to System.Data.SqlServerCe it now causes ... "DesktopCompatible" workaround (i.e. through the class designer). ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: What is the difference detween SRC and CODEBEHIND Tags?
    ... Code behind will compile quicker on application startup because large parts ... >> CODEBEHIND specifies the name of the compiled file that contains the ... It tells the designer where to find the ... >> work with at design time. ...
    (microsoft.public.dotnet.framework.aspnet)