Re: How to tell VS not to treat a class as a form

Tech-Archive recommends: Fix windows errors by optimizing your registry

Robbe Morris [C# MVP] wrote:
Forms are classes. You are also inheriting the class Form.
How would visual studio which developers want
the form to render in the designer and which developers don't.

Well, for example if there is no associated *.resx file it's logically to treat that class as just class - anyway VS will fail to load designer if there is no *.resx for *.cs


Just right click the class and click View Code. It
can't be that "inconvenient".

.

Relevant Pages

  • Re: What I saw at MS Launch
    ... > developers this frightened away. ... That's a potential weakness that Borland could ... Binding a grid to a collection is now REALLY easy. ... WinForms designer, and have it just display an error message. ...
    (borland.public.delphi.non-technical)
  • Re: Future of MFC?
    ... MFC could have high-level designer tools ... Don't imagine that we MFC developers like getting our hands dirty when we ...
    (microsoft.public.vc.mfc)
  • Re: Thinking Clearly
    ... known as "Data Dude" which integrates into Visual Studio 2005 Professional ... new compiler but there are new compiler for WinFX. ... The Expression Interactive Designer aka Sparkle will be a commercial product ... but for some developers this adoption may also have a positive ...
    (borland.public.delphi.non-technical)
  • Re: How to tell VS not to treat a class as a form
    ... the form to render in the designer and which developers don't. ... I made change directly to the project file specifying that this file ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: .NET 3.0
    ... IIRC it was actually about the need to expose form design and customization. ... IME in the business application world, the end-user isn't so "end", it'll often be a project manager/team of some sort, which will seek UI changes and data specifics, adjusting your executable to be then consumed by employees. ... The WF designer is AFAICT targeted at a similar "end-user": a user "above" other users, ... There is often more than one level between the developer and the end-user, where you find people that are neither developers nor final users, and want a bit of developer-level design and UI control, while staying rather firmly on the user side. ...
    (borland.public.delphi.non-technical)