Disable designer in Visual Studio?

16,641

Solution 1

Just dont add "new form" , add to the project new class and inherit him from the Form class.

Solution 2

Right clicking on a project file and selecting open with allows you to set the defaults for opening file types.

Solution 3

Actually, all you have to do in VS2010 is right click the .cs file that you don't want to open in the designer, select the "Open With.." option, then make CSharp Editor the default. Notice that the form view is the default before you change it.

Solution 4

Frederik, sure you're right, but not in one fact. ( this one I.J wanted to know ) As soon as you inherit from any Component, the studio tries to open it in a designer editor. That is a default behaviour of the visual studio.

If you double click a file in the solution explorer, then a designer opens. So it's really annoying if you always get such strange designer for classes that are just inherited from a Component, but do not contain any visible things.

The only thing that really helped me out, was to set this attribute:[System.ComponentModel.DesignerCategory("")]

I didn't knew this =) so cool hint !

I just get a problem with partial MainForm classes. Then it yells "duplicate attribute"...

Does here anybody knows a solution to avoid in some partial class-files the designer to be opened on double click ( without the duplicate attribute error on compile ? )


I think I found a small bug, in VS2005... By setting the DesignerCategory-Attribute on the partial form class, on save the solution explorer shows up an icon, identifying the file as a c# file (no form).

Then I put a comment (//) before the attribute - and it keeps opening the file in code view. Also after closing and reopening it's stored internally as a non designable form-part. Even on re opening the complete solution.

So I think there is any information in the solution or project file...

... I found this in the .csproj file: ...

<Compile Include="GUI\VFormMain_Test.cs">
</Compile>
<Compile Include="GUI\VFormMain_Theme.cs">
</Compile>
<Compile Include="Core\VTTEnv.cs" />
<Compile Include="GUI\VFormMain.cs">
  <SubType>form</SubType>
</Compile>

...

Studio updates from time to time - then it updated the form files again (doh)... ok.. but there is probably a workaround to avoid this.


snip... last edit... found something:

http://social.msdn.microsoft.com/Forums/en-US/csharpide/thread/64c77755-b0c1-4447-8ac9-b5a63a681b78

( name the file you want to open without designer into .Designer.cs )

( Yes you have to name something to switch it of LOL ) Seems to work.

Share:
16,641
I. J. Kennedy
Author by

I. J. Kennedy

[email protected]

Updated on June 19, 2022

Comments

  • I. J. Kennedy
    I. J. Kennedy about 2 years

    I'm using Visual C# Express to write Windows Form applications, and call me old school, but I don't like the designer. It is a nuisance and pollutes my project with lots of unwanted files, as well as unwanted monkey-generated source code.

    Please tell me there's a way to turn it off completely.

  • I. J. Kennedy
    I. J. Kennedy over 15 years
    OK, thanks, that's a big help. I didn't realize I could set the default opener for a file. It was a small nuisance to right click and pick "view code" every time.
  • Jeremy Pridemore
    Jeremy Pridemore over 11 years
    This just showed me how to get rid of the SQL Design view stuff in Visual Studio 2012 and set it back to just opening it with a T-SQL Editor. Thanks, Richard from the past!
  • Cephron
    Cephron over 10 years
    The problem is when it opens by default every time you open a specific file type.
  • Dmytro
    Dmytro about 8 years
    I think this answer just changed my life. I can now write C++/CLI form applications the same way I would normally write Java, without having to use C#. I never thought of using C++/CLI without designer before, but it's beautifully powerful.
  • SQL Police
    SQL Police almost 8 years
    That's right, but then you could still accidentally open up the designer. I have a form where I strictly must prohibit invocation of the designer, because the designer is messing up the code.
  • SQL Police
    SQL Police almost 8 years
    That's right but be careful. If you open the designer by accident, then it might mess up yourhandwritten code.